9.8. Using RMAN to Perform Database Migration to ASM

Because ASM files cannot be accessed via the operating system, you must use the Recovery Manager (RMAN) to move database objects from a non-ASM disk location to an ASM disk group. Follow these steps to move these database objects:

  1. Note the filenames of the control files and the online redo log files.

  2. Shut down the database using the NORMAL, IMMEDIATE, or TRANSACTIONAL keywords.

  3. Back up the database.

  4. Edit the SPFILE to use OMF for all file destinations.

  5. Edit the SPFILE to remove the CONTROL_FILES parameter.

  6. Run the following RMAN script, substituting your specific filenames as needed:

    STARTUP NOMOUNT;
RESTORE CONTROLFILE FROM '<controlfile location>';
ALTER DATABASE MOUNT;
BACKUP AS COPY DATABASE FORMAT
   '+<disk group destination>';
SWITCH DATABASE TO COPY;
SQL "ALTER DATABASE RENAME <logfile1>
         TO '+<disk group destination>' ";
# repeat for all log file members
ALTER DATABASE OPEN RESETLOGS;

  7. Delete or archive the old database files.

Even though all files in this example are now ASM files, you can still create a non-ASM tablespace if, for example, you want to transport a tablespace to a database that does not use ASM.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset