Expert Oracle Exadata - Parent Directory

CHAPTER 13 MIGRATING TO EXADATA2. Restrict user and application access to the database.3. Take a full database backup (optionally convert to little-endian platform).4. Copy the files to Exadata (not required if backup resides on a shared filesystem or tape).5. On Exadata, startup the database in nomount mode.6. Restore the control file (optionally convert to Linux x86 64-bit platform).7. Mount the database.8. Restore the database (optionally convert to Linux x86 64-bit platform).9. Recover the database. (Note that you cannot recover a database with archiveandredo logs from the source database, if the source database is on a differentplatform than the target database. This means that you can’t reduce themigration downtime by restoring and rolling forward an old productionbackup if the source database is running on a different platform than thetarget. In such a case the writable source database files should berestored/copied only when they are in their final state (that is, the sourcedatabase is already shut down). Read-only tablespace files can still becopied/restored in advance.10. Perform post-migration tasks:a. Convert the database to RAC and create service names.b. Reconfigure client tnsnames.ora files, configuration files for connecting tothe Exadata database.11. Make the database available to users and applications.As you can see, this is a fairly straightforward process. After following these steps you have an exactcopy of your production database running on Exadata. There are a few things to keep in mind, though. Ifyour source database uses file systems for database storage, or if you are using ASM but the disk groupnames are different on Exadata, you may redirect the restored files to the new disk group names bychanging the db_create_file_dest and db_recovery_file_dest parameters in the init.ora file beforestarting the restore process. Table 13-5 shows how these parameters can be used to remap disk groupnames from the source database to Exadata.Table 13-5. Remap Disk GroupsInit.ora Parameters Source Database Exadata Databasedb_create_file_dest '+DATA_FILES'db_recovery_file_dest '+RECOVERY_FILES'+DATA''+RECO'If your database uses multiple ASM disk groups to store your database files, use the RMANdb_file_name_convert command to remap the file names to ASM disk groups. For example:453