The next step is to migrate the control file from the old flash recovery area to the new flash recovery area. RMAN> RESTORE CONTROLFILE FROM ' filename_of_old_control_file' If the old flash recovery area has copy of the current control file, then restore control file from the old DB_RECOVERY_FILE_DEST and mount the database again. If you shut down the database in step 2, then bring the database to a NOMOUNT state. Modify DB_RECOVERY_FILE_DEST_SIZE if you need to change the size of the flash recovery area. Set DB_RECOVERY_FILE_DEST to the desired ASM disk group. Modify the initialization parameter file of the target database as follows: Alter system db recovery file dest size archive#If this database is a standby database and your standby online logs, control file, or archive logs are in recovery area, then stop managed recovery mode and shut down the database. If this database is a primary database and your online logs, control file or archived redo logs are in the flash recovery area, then perform a consistent shutdown of your database. The first step is to change the initialization parameters for the database to store the flash recovery area in ASM, as described in Setting Initialization Parameters for Flash Recovery Area in ASM. The following procedure changes the database configuration so that the flash recovery area is used for all future backups. For example: SQL> ALTER DATABASE FLASHBACK ON If you were using flashback logging before to support flashback database, you can re-enable it now. RMAN> restore controlfile from '+DISK/ct1.f' Then, use RMAN to actually create the new control files in ASM. Shut down and startup in NOMOUNT again, so that the changed CONTROL_FILES parameter takes effect. If using a PFILE, edit the PFILE with the new for the CONTROL_FILES initialization parameter. If you are using an SPFILE, use the following command: SQL> alter system set control_files='+DISK/ct1.f','+FRA/ct2.f' scope=spfile sid='*' In SQL*Plus, bring the database to NOMOUNT: SQL> SHUTDOWN IMMEDIATE Ĭhange the CONTROL_FILES initialization parameter to refer to the new location. The goal is to move the non-ASM control file to the flash recovery area and store it as +FRA/ct2.f. It is also assumed that one control file is already stored in +DISK/ct1.f, the other in non-ASM storage. In this example, it is assumed that you have already set the initialization parameters for a flash recovery area in ASM storage, using the process in "Setting Initialization Parameters for Flash Recovery Area in ASM". u01/app/oracle/fra 1.0737E+10 0 0 0 0 3) Configure archive log destination to use flash recovery area.If you have already migrated all of these files to ASM storage using the procedure in "Disk-Based Migration of a Database to ASM" you do not need to perform this step. NAME SPACE_LIMIT SPACE_USED SPACE_RECLAIMABLE NUMBER_OF_FILES CON_ID SQL>alter system set db_recovery_file_dest='/u01/app/oracle/fra' scope=both ĭb_recovery_file_dest string /u01/app/oracle/fraĭb_recovery_file_dest_size big integer 10G SQL> alter system set db_recovery_file_dest_size=10g scope=both 1)Check and confirm Flash Recovery Area is not enabled.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |