1. Introduction
In enterprise database environments, Automatic Storage Management (ASM) provides a scalable, high-performance, and simplified storage management solution compared to traditional filesystem-based storage.
Migrating a database from Non-ASM (Filesystem) to ASM improves:
• Storage management automation
• I/O performance optimization
• High availability integration with Grid Infrastructure
• Simplified file naming using OMF (Oracle Managed Files)
• Better integration with RAC and Data Guard
This document provides a complete end-to-end implementation of migrating an existing Oracle 19c single-instance database from filesystem storage (/u02/oradata/…) to ASM disk group (+DATADG) using RMAN online copy methodology.
2. Architecture Overview
Before Migration (Filesystem Based)
Component Value
Database Name PROD
Version Oracle Database 19c
Storage Type Filesystem
Datafile Location /u02/oradata/prod
Redo Logs /u02/oradata/prod
Control Files Filesystem
Tempfiles Filesystem
ASM Installed but Not Used
After Migration (ASM Based)
Component Value
Database Name PROD
Version Oracle Database 19c
Storage Type ASM
Disk Group +DATADG
Datafile Location +DATADG/PROD/DATAFILE
Redo Logs +DATADG/PROD/ONLINELOG
Control Files +DATADG
Tempfiles +DATADG
ASM Fully Utilized
Key Transformation Summary
Area Before After
File Management Manual OMF (Automatic)
Performance OS Filesystem Dependent ASM Striping
Scalability Limited High
RAC Ready No Yes
Storage Administration Manual Centralized via ASM
3. Objective
The objectives of this migration are:
• Move database storage from filesystem to ASM
• Ensure zero data loss
• Minimize downtime
• Maintain database integrity
• Configure OMF for future file management
• Relocate password file and SPFILE to ASM
• Take full RMAN backup post migration
4. Scope
This document covers:
• Pre-checks and validation
• RMAN image copy migration method
• Control file & Redo log relocation
• Temp tablespace recreation
• SPFILE migration to ASM
• Post-migration validation
This document does not cover:
• RAC migration
• Cross-platform migration
• Database version upgrade
5. Prerequisites
Before starting migration, ensure:
• ASM instance is running
• Target disk group (+DATADG) exists
• Sufficient free space available (DB size + 30%)
• Database in ARCHIVELOG mode (recommended)
• Full RMAN backup taken
• SYSDBA privileges available
• Grid Infrastructure operational
6. Implementation Methodology
The migration follows this structured approach:
1. Configure OMF to point to ASM
2. Copy password file to ASM
3. Create RMAN image copies into ASM
4. Switch database to ASM copies
5. Recover and open database
6. Move control files to ASM
7. Move redo logs to ASM
8. Recreate TEMP tablespace in ASM
9. Move SPFILE to ASM
10.Validation and full backup
7. Pre-Migration Checks
7.1 Verify ASM Instance
7.2 Verify Disk Group Space
Ensure free space is sufficient.
7.3 Verify Current Database Storage
8. Implementation Steps
8.1 Configure OMF for ASM
This ensures future files are created in ASM.
8.2 Move Password File to ASM
Create password file if not exists:
Copy to ASM:
8.3 Copy Datafiles to ASM (Online Method)
Connect to RMAN & Enable controlfile autobackup:
Create image copies in ASM:
8.4 Switch Database to ASM Copies
Shutdown and mount:
Catalog ASM files:
Switch to copies:
Open database:
Verify:
8.5 Move Control Files to ASM
Create controlfile copies:
Update parameter:
Verify:
8.6 Move Online Redo Logs to ASM
Create new groups in ASM:
REDO LOG FILE GROUP STATUS
➢ unused - lgwr never used the redo file group
➢ current - lgwr currently writing in redo log file group
➢ active - waiting for arch process to take backup
➢ inactive - ready for next write
Status Drop Allowed? Why
CURRENT No LGWR writing
ACTIVE No Needed for recovery
INACTIVE Yes Safe to remove
UNUSED Yes Never used
Switch logs until old groups become INACTIVE:
Drop old groups:
Verify:
8.7 Recreate TEMP Tablespace in ASM
Create new temp: Set default: Drop old temp:
8.8 Move SPFILE to ASM
9. Post-Migration Backup
Take full backup in ASM:
This ensures full recoverability after migration.
10. Validation Checklist
10.1 Datafiles
10.2 Control Files
10.3 Redo Logs
10.4 Tablespace Health
11. Risks and Mitigation
Risk Mitigation
Insufficient ASM space Validate free space before migration
Redo group stuck CURRENT Force log switches
Password file mismatch Copy to ASM and update srvctl
Startup failure Verify control_files parameter
Accidental data loss Take full RMAN backup before and after
12. Benefits After Migration
➢ Centralized storage management
➢ OMF automated file naming
➢ Simplified file addition
➢ Better performance with ASM striping
➢ Seamless integration with RAC
➢ Improved disaster recovery readiness
13. Conclusion
This implementation successfully migrated the Oracle 19c single-instance database from traditional filesystem storage to ASM disk group +DATADG using RMAN online copy methodology.
The migration ensured:
• Zero data loss
• Controlled downtime
• Full integrity validation
• Improved storage performance
• Future-ready architecture for RAC and Data Guard
The database is now fully operating on ASM with optimized storage management, automated file handling through OMF, and enhanced enterprise-grade reliability.
14. Future Enhancements
While the current migration consolidates all database storage onto ASM, several enhancements can further optimize performance, security, and manageability:
1. ASM-Based Transparent Data Encryption (TDE)
o Implement TDE on ASM diskgroups to secure data at rest, ensuring compliance with regulatory standards and enterprise security policies.
o Leverage multi-tenant key management for databases in RAC or CDB/PDB environments.
2. Automatic Storage Rebalancing
o Enable ASM rebalance operations to dynamically distribute data across disks as storage usage grows, improving I/O performance and preventing hotspots.
3. Integration with Oracle RAC and Multi-Instance Environments
o Extend ASM deployment to RAC clusters to provide high availability and load balancing for mission-critical databases.
4. ASM-Based Flash Recovery Area (FRA) Expansion
o Move archival logs, RMAN backups, and temporary recovery storage entirely into ASM for centralized, high-performance backup management.
5. Storage Tiering and IO Optimization
o Leverage ASM storage tiering (SSD/HDD or Exadata storage tiers) to optimize performance for high-transactional workloads.
6. Monitoring and Automation
o Integrate ASM monitoring via Oracle Enterprise Manager or custom scripts to proactively track diskgroup usage, performance metrics, and alerting for threshold breaches.
7. Cloud and Hybrid Deployment Readiness
o Prepare ASM storage layouts for hybrid cloud or Oracle Cloud Infrastructure (OCI) deployments, enabling seamless migration or DR setups in cloud environments.
By implementing these enhancements, the ASM-based environment evolves from a storage migration initiative to a highly resilient, secure, and scalable enterprise storage architecture, ready for future growth and advanced database features.
No comments:
Post a Comment