Performing post restore operation

The steps in this procedure are applicable only for LVM and File System setups. However, steps 7 to 9 are applicable for all setups.

  1. Add the volumes exported as physical Raw Device Mapping to Oracle server for databases with volumes exported as physical RDM.
  2. Perform a rescan of the devices on the database server.
    You may use from sg3_utils package or use appropriate iscsiadm commands, for iSCSI connections.
  3. Post rescan operation, execute oracleasm scandisks if you use ASMLib. You may validate the ASM disks with the command oracleasm querydisk <diskname>.
  4. From the database server, activate logical volumes and import volume groups:
    # vgscan
    # vgimport rh6lvm-datavg
    # lvchange -ay /dev/rh6lvm-datavg/lvol0
    # lvchange -ay /dev/rh6lvm-datavg/lvol1
  5. From the database server, perform file system check, and then mount the database file systems if database files are on file systems.
    # fsck -y /dev/maper/mpathc
    # mount /dev/mapper/mpathc /oradata
  6. From the database server, mount database ASM disk groups if ASM is in use. For example, SQL>alter diskgroup <diskgroup> mount;
  7. Extract the CONTROLFILE from metadata file path specified in RMC-O Restore user interface dialog using the following commands:
    # cd <meta data file path> 
    # tar -xvf <sid>.gz 
    # gunzip controlfile.gz
    Change the ownership of the extracted CONTROLFILE to oracle user and oinstall group.
  8. Connect to RMAN (rman target /) to restore the binary CONTROLFILE and run the recover database command as follows:
    RMAN> startup nomount; 
    RMAN> restore controlfile from '<metadata file path>/controlfile'; 
    RMAN> exit

    Restoring CONTROLFILE is not mandatory if the new form of your database has not changed.

  9. Connect to the SQL prompt to run the following set of commands:
    SQL> alter database mount; 
    SQL> recover database using backup controlfile until cancel; 
    SQL> alter database open resetlogs; 
    SQL> exit
    UNTIL TIME or UNTIL SCN or UNTIL SEQUENCE clauses in the commands described in this procedure for point-in-time recovery. When prompted for archive logs, AUTO or CANCEL option can be used, based on your recovery needs. If there is any mismatch in the path of prompted archive logs, specify the paths to the actual archive logs explicitly in the prompt so that recovery succeeds. Once the recovery completes, a new form of your database is started.