Restore Data - Oracle or Oracle RAC - How To

From the CommCell Browser, right-click the Oracle agent or instance that contains the datafiles you want to rename/redirect on restore, click All Tasks and then click the available Browse command (command names vary by agent).
Run a browse operation. See Browsing Data for a list of customized browse operations and their step-by-step instructions. If you accept all defaults, you will be browsing the latest backups for the selected data.
From the Browse window, Select Objects From the Browse Window for Restore.
From the General tab of the Oracle Restore Options dialog box, and the Job Initiation tab of the Restore Options dialog box, select the options that you want to use.
Click Advanced.
From the Redirect tab of the Advanced Restore Options dialog box, redirect tablespaces and/or rename datafiles for the restore operation. Specifically, do one of the following:
- If you want to redirect all the tablespaces selected for restore to a new location, then select the Redirect All Table Spaces to: checkbox and either type in a new location in the corresponding entry field or click Browse to display the Browse for Restore Redirect Path window and navigate to the new location.
- If you want to redirect only certain tablespace(s) or datafile(s) to a new location, then select the Redirect checkbox, click the desired object(s) in the Object column to highlight them, and either type in a new location in the New Path entry field or click the Browse button to the right of the New Path field to display the Browse for Restore Redirect Path window and navigate to the new location. After specifying the New Path, click Apply. The specified location will now display in the New Path column next to the selected object(s).
- If you want to redirect all datafiles for a tablespace, select the Redirect checkbox, select the desired tablespace from the Object column, and type in a new path in the New Path entry field. After specifying the new path, click Apply. The new path for the datafiles will now display in the New Path column next to the selected tablespace.
- If you want to rename one datafile for a tablespace, select the Redirect checkbox, expand the desired tablespace then select the desired datafile, and type in the full path with a new name in the New Path entry field. After specifying the new name, click Apply. The new name for the datafile will now display in the New Path column next to the selected datafile.
Click OK to save your entries. This closes the Redirect tab.
Select any additional restore options from the tabs for the Advanced Restore Options dialog box and then click OK.

If you want to schedule the job, select the Job Initiation tab from the Restore Options dialog box, click Schedule, schedule the job, and then click OK. If you want to run the job now, accept or click Run Immediately in the same tab and then click OK.

Before the restore job is run, the system will check whether the database is in the correct mode for this type of restore. If it is not, a message dialog will inform you of this and offer to automatically switch the database into the valid mode. When this happens, either click Yes on the message dialog to have the system automatically switch the database to the valid mode and continue the restore, or click No to manually switch the database to the valid mode before proceeding.

The progress of the restore job can be monitored using the Job Controller.
After the data has been restored, you will see a job completion message in the Job Controller and Event Viewer.

Restore and Recover One or More Tablespace(s) in ARCHIVELOG Mode to the Current Time

The following procedure describes the steps involved in restoring one or more lost tablespaces, without the control file for a database running in ARCHIVELOG mode. This procedure restores and recovers the tablespace(s) as follows:

From an online backup
Without the control file(s) (since it exists)
To the current time and to the original host
Using the Recovery Catalog

Before You Begin:

Review the general and agent-specific restore requirements accessed from Restore Backup Data prior to performing any restore.

Required Capability: See Capabilities and Permitted Actions

To restore and recover one or more tablespace(s) in ARCHIVELOG mode to the current time:

From the CommCell Browser, right-click the instance that contains the tablespace(s) you want to restore and recover, click All Tasks and then click Restore.
From the Oracle Restore Options (General) dialog box, select the following options:
- Click the name of the client computer with the tablespace(s) you want to restore in the Destination Client box (if it is not already selected).
- Select the Restore Data and Recover options.
- Select the tablespace(s) you want to restore in The Latest Database View pane.
Click on the Advanced button and verify the following options are selected:
- Restore Data - From the Latest Backup Advanced Restore Options (Restore)
- Recover - Current Time Advanced Restore Options (Recover)
Click OK in the Oracle Advanced Restore Options window.
When restoring encrypted data, refer to Data Encryption.
Optionally for Oracle RAC, from the Oracle Restore Options (Stream) dialog box, set the instance restore order per stream allotment.

Begin or schedule the restore.

During the partial restore job, the system checks whether the selected tablespaces are in the OFFLINE state. If they are not, the system will automatically switch the tablespaces to the OFFLINE state.

While the job is running you can right-click the job in the Job Controller and select Details to view information on the job. After the data has been restored, you will see a job completion message in the Job Controller and Event Viewer.

Restore and Recover One or More Datafile(s) in ARCHIVELOG Mode to the Current Time

The following procedure describes the steps involved in restoring one or more lost datafile(s), from an existing control file. The database containing these datafile(s) is running in ARCHIVELOG mode. This procedure restores and recovers the datafile(s) as follows:

From an online backup
Without the control file(s) (since it exists)
To the current time and to the original host
Using the Recovery Catalog

Before You Begin:

Review the general and agent-specific restore requirements accessed from Restore Backup Data prior to performing any restore.

Required Capability: See Capabilities and Permitted Actions

To restore and recover one or more datafile(s) in ARCHIVELOG mode to the current time:

From the CommCell Browser, right-click the instance that contains the datafile(s) you want to restore and recover, click All Tasks and then click Restore.
From the Oracle Restore Options (General) dialog box, select the following options:
- Click the name of the client computer with the datafile(s) you want to restore in the Destination Client box (if it is not already selected).
- Select the Restore Data and Recover options.
- Open the database tree and select the datafile(s) you want to restore in The Latest Database View pane.
Click the Advanced button and verify the following options are selected in the identified tab for the Oracle Advanced Restore Options dialog box:
- Restore Data - From the Latest Backup in Restore
- Recover - Current Time in Recover
Click OK in the Oracle Advanced Restore Options window.
When restoring encrypted data, refer to Data Encryption.
Optionally for Oracle RAC, from the Oracle Restore Options (Stream) dialog box, set the instance restore order per stream allotment.
Begin or schedule the restore.
While the job is running you can right-click the job in the Job Controller and select Details to view information on the job. After the data has been restored, you will see a job completion message in the Job Controller and Event Viewer.

Restore Archive Log Files

Before You Begin:

Review the general and agent-specific restore requirements accessed from Restore Backup Data prior to performing any restore.
Make sure that the DBID value for the particular database is displayed in the Instance properties dialog box. If you have not yet created an instance for the database, refer to Create/Modify an Instance for more information.

Required Capability: See Capabilities and Permitted Actions

To restore archive log files using the CommCell Console:

From the CommCell Browser, right-click the instance, select All Tasks then click Restore.
From the Oracle Restore Options (General) tab, select Restore Archive Log. You can also select Restore Data and Recover options if required.
Click Advanced.
From the Advanced Restore Options (Restore) tab, select Restore Archive Logs.
Select any of the following criteria to restore the archive log files:
- Select By Log Time to restore archive log with start time (mm/dd/yy:hh/mm/ss) and End time (mm/dd/yy:hh/mm/ss).
- Select By Log Serial Number (LSN) to restore archive logs based on the specified Log Sequence Numbers (LSNs) that you specify. Specify the Start number (enter log sequence number) and End number (enter log sequence number) to restore archive logs.
If you want to save the archive logs in a different location, enter the path in Target Directory field or click Browse to select a new location.
Click OK to save the settings.

Restore and Recover One or More Database Table(s)

The following procedure describes the steps involved in restoring one or more database tables. This procedure restores and recovers the tables as follows:

From an online backup with the Enable Table Browse option set on the Subclient Properties (Backup Arguments: Options) tab
Without the control file(s) (since it exists)
From the current time (by default) backup data or either the point-in-time (PIT) or System Change Numbers (SCN) backup data
To the original host (by default) or to a cross-host client that is installed on the same CommServe and to the Oracle instance that is configured in the CommCell
Using the Recovery Catalog (optional)

Before You Begin:

Review the general and agent-specific restore requirements accessed from Restore Backup Data prior to performing any restore.
Ensure that the destination host has the same version of the operating system and Oracle version as the source host.
Make sure that the backup was performed after enabling the table browse for the subclient. For step-by-step instructions, see Enable Table Browse for the Subclient.
Perform the Prerequisite Setup Steps for Creating a Duplicate Database to create an auxiliary database on the destination host.
Ensure that all dependent tables are selected for restore by running the following Oracle command:
select constraint_name, constraint_type, table_name, R_constraint_name from dba_constraints;

Required Capability: See Capabilities and Permitted Actions

To restore and recover one or more database tables:

From the CommCell Browser, right-click the instance that contains the tables you want to restore and recover, click All Tasks and then click Browse Backup Data.
From the Browse Options dialog box, select Table View.
Click OK.
In the Browse window, select the tables to be restored and click Recover All Selected.
From the Oracle Restore Options (General) tab, select, enter, or consider the following:
- The Destination Client field will display the name of the client computer to which you want to restore the Auxiliary Instance if you select the Auxiliary Instance option on the Oracle Restore Options (Table Restore) tab (discussed in a later step) and enter a client name in the Database Client list on this tab. The source client is the default computer.
- Use the Catalog Connect fields to enter the connect string for the catalog database of the source machine, or select the NO CATALOG option to disable the Catalog Connect fields.
Click Advanced and then the Recover tab, and choose a time for the restore. Current Time is the default option. The point in time value will be displayed automatically in the Point In Time fields if the PIT time has already been entered in the Specify Browse Time field in the Browse Options dialog box.
From the Oracle Restore Options (Table Restore), select the required parameters.
- The Paths Selected For Restore box will show the selected users and selected tables
- If the Auxiliary Instance option is selected, this instance must be in NOMOUNT mode, the pfile should be provided, and you will need to select a client name from the Database Client list. The Auxiliary Instance should be configured on the CommCell. The source client is the default client. The existing Auxiliary Instance will be overwritten by restoring tables.
- Ensure that the staging path that you specify has enough space. To determine space requirements, preview the RMAN script before you run the restore by clicking Script Preview from the Oracle Restore Options (General) tab. This script will show the system tablespaces and the user tablespaces (containing tables) to be restored; however, it will not show the temporary tablespaces used for the restore. Therefore, be sure to check the size of all these tablespaces from your computer before you run the restore.
- The Import Options option allows you to select any options that you want to restore tables.
  - Do Not Import option will export the tables and leave them in the staging area. You can import the tables to the destination database later or at any time by using the appropriate import utility.
  - Import to Source Database option will import tables to the source database.
  - Import to a Different Database option allows you to import selected tables to a different database whose name must be entered in the Select Import Database field. This database must be configured on CommCell of the same CommServe. The cross-machine can be selected from the Select a Client list also.
- Drop Table option will drop all selected tables if they have not been dropped manually from the destination database.
For Oracle RAC only, from the Streams tab, select only one node with only one stream to submit the job.
Click OK.

Restore and Recover a Database to a New Host with the Same Directory Structure (Oracle and Oracle RAC)

The following procedure describes the steps involved in restoring and recovering a database (either in ARCHIVELOG or NOARCHIVELOG) mode to a new host, with the same directory structure.

When you are restoring data from a database in NOARCHIVELOG mode, you must always restore and recover the entire database.

Before You Begin:

Review the general and agent-specific restore requirements accessed from Restore Backup Data prior to performing any restore.
When you perform a database restore to a new host the source and destination machines must have the following features:
- The same operating systems
- The same Oracle version
- The same database datafile directory structures
- The same ORACLE_SID
- Must be either a 32-bit or 64-bit system
In the destination machine
- Install the Oracle iDataAgent or create the Oracle RAC client and configure as client in the same CommServe in which the source machine resides
- Create and configure a new Oracle instance, similar to the one existing in the source machine
In addition the destination machine must have sufficient disk space to accommodate the restored database.

Required Capability: See Capabilities and Permitted Actions

To restore and recover a database to a new host with the same directory structure:

Verify that the destination machine's init <SID>.ora file is the same as the source machine's file.
Configure the destination machine's $TNS_ADMIN/tnsnames.ora file to include the Recovery Catalog database's service entry. The easiest way to configure this file is to copy the Recovery Catalog database's service entry from the source machine's tnsnames.ora file and append it to the destination machine's tnsnames.ora file. The Recovery Catalog database's service entry should look similar to the following:
<service_name> =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = <protocol>)(HOST = <host>) (PORT = <##>))
(CONNECT_DATA = (SID = <Recovery Catalog database>)))
Make sure that ORACLE_SID is set to the database that you are restoring and that ORACLE_HOME is set appropriately. Note the following example for Solaris:
#export ORACLE_SID= <target database SID>
#export ORACLE_HOME= <Oracle home directory>

Note the following example for Windows 2000 machines:
C:\set ORACLE_SID= <target database SID>
C:\set ORACLE_HOME= <Oracle home directory>

From Server Manager or SQL Plus on the source machine, create a new user account within the Recovery Catalog for the destination machine by executing the commands in the following display:
SVRMGR>create user <username> identified by <password>
2>temporary tablespace <temp_tablespace_name>
3>default tablespace <default_tablespace_name>
4>quota unlimited on <default_tablespace_name>;
Statement processed.
SVRMGR>grant connect, resource, recovery_catalog_owner to <username>;
Statement processed.

Make sure that the <username>you supply for the destination machine is different than the username for the source machine.

When you are granting the user database permissions, make sure to include the recovery_catalog_owner option shown above.

Transfer the Oracle password file "orapw<Oracle SID name>" from the source machine to the destination machine. Usually this file resides in ORACLE_HOME/dbs.
From the source machine, use the Oracle exp command to export the Recovery Catalog data. You are exporting the data by user. For example, if the user ID for the Recovery Catalog owner is rman, you would export the database backup information for the user rman.
From the source machine, use the Oracle imp command to import the contents of the file you created in the previous step into the new user account for the destination machine. Depending on the version of Oracle that you are running, you may receive the following error when you run the imp command:
IMP-00044: unable to allocate enough memory for statement
Perform these steps if you receive an error while running the imp command:
- Drop the user.
- Recreate the user.
- Rerun the imp command.
- When you rerun the imp command, enter 1000000 when prompted for the insert buffer file.
- If you receive the error message again, repeat the preceding steps and increase the buffer by a million each time you run imp until the error message is no longer displayed.
Ensure that the database in NOMOUNT mode in the destination machine.
If you want to perform the cross-machine restore from the CommCell Console then continue on with this procedure. Otherwise, if you want to perform the cross-machine restore from the RMAN command line using your own custom script, then exit this help and run the script now (refer to Oracle's Recovery Manager documentation for more information).
From the CommCell Browser, right-click the instance that contains the database you want to restore and recover to a new host, click All Tasks and then click Restore.
From the Oracle Restore Options (General) dialog box, select or enter the following:
- Click the name of the client computer to which you want to restore in the Destination Client box.
  
  If your destination client is not listed, check and ensure that all the requirements stated in the Before you Begin section is satisfied.
- Use the Catalog Connect fields to enter the connect string for the catalog database of the destination machine.
- Select the Restore Control File option.
- Select the Restore Data and Recover options.
  
  It is critical that the Recover option is selected, as Recover applies any incremental backups that are needed to bring the database back to a consistent state.
- Select the entire database in The Latest Database View pane (if it is not already selected).
Click the Advanced button and verify the following options are selected in the identified tab for the Oracle Advanced Restore Options dialog box:
- Restore Control File - To Point in Time in Ctrl & SP Files
  
  The Control file must be restored to a point in time that is later than or equal to time set for the Restore Data option in the Restore tab.
- Restore Data in Restore
  
  The Restore Data option must be earlier than or equal to the point in time that you specified for the Restore Control File option in the Ctrl & SP Files tab.
- Recover - Point In Time in Recover
  
  The point in time for the recover option must be later than or equal to the point in time specified for the Control file in the Ctrl & SP Files tab.
Click OK in the Oracle Advanced Restore Options dialog box.
When restoring encrypted data, refer to Data Encryption.
Optionally for Oracle RAC, from the Oracle Restore Options (Stream) dialog box, set the instance restore order per stream allotment.

Begin or schedule the restore.

View the progress of the restore in the Job Controller window.
- In ARCHIVELOG mode - When the data is restored, click OK on the confirmation window. If desired, click Detail to review information on the restore operation.
- In NOARCHIVELOG mode - The job will report the restore as failed. This is because no archive redo log files exist. RMAN will report the following message, in reference to this error:
  
  RMAN-03022: compiling command: recover(4)
  RMAN-03026: error recovery releasing channel resources
  RMAN-08031: released channel: ch1
  RMAN-00571:
  ======================================================
  RMAN-00569:====== ERROR MESSAGE STACK FOLLOWS=========
  RMAN-00571:
  ======================================================
  RMAN-03002: failure during compilation of command
  RMAN-03013: command type: recover
  RMAN-06054: media recovery requesting unknown log: thread 1 scn 72077
  RMAN>
  Recovery Manager Complete.
Perform the following steps if your database is in the NOARCHIVELOG mode.
Manually recover and open the database using the following steps.
From the Server Manager window, execute the command displayed in the following example:
SVRMGR>recover database using backup control file until cancel;

Server Manager displays several messages, including the following:
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
Type cancel

The following message is displayed:
Media recovery cancelled.
Execute the commands displayed in the following example:
SVRMGR>alter database open resetlogs;
SVRMGR>exit
Reset the Recovery Catalog by executing the commands displayed in the following example:
#rman rcvcat <catalog connect string>
Recovery Manager: Release 8.1.5.00 - Production
RMAN-06008: connected to recovery catalog database
RMAN>connect target;
RMAN-06005: connected to target database: <database_name> DBID=<##>)
RMAN> reset database;
RMAN-03022: compiling command: reset
RMAN-03023: executing command: reset
RMAN-08006: database registered in recovery catalog
RMAN-03023: executing command: full resync
RMAN-08002: starting full resync of recovery catalog
RMAN-08004: full resync complete
RMAN>exit

Resetting the Recovery Catalog creates a new incarnation of the database. Before you can restore and recover the database to the current time, you must perform another full backup and wait for it to complete successfully.
Perform an immediate offline full backup.

Restore and Recover a Database to a New Host with a Different Directory Structure (Oracle and Oracle RAC)

The following procedure describes the steps involved in restoring and recovering a database (either in ARCHIVELOG or NOARCHIVELOG) mode to a new host, with a different directory structure.

When you are restoring data from a database in NOARCHIVELOG mode, you must always restore and recover the entire database.

Before You Begin:

Review the general and agent-specific restore requirements accessed from Restore Backup Data prior to performing any restore.
When you perform a database restore to a new host the source and destination machines must have the following features:
- The same operating systems
- The same Oracle version
- Different database datafile directory structures
- The same ORACLE_SID
- Must be either a 32-bit or 64-bit system
In the destination machine
- Install the Oracle iDataAgent or create the Oracle RAC client and configure as client in the same CommServe in which the source machine resides
- Create and configure a new Oracle instance, similar to the one existing in the source machine
In addition the destination machine must have sufficient disk space to accommodate the restored database.

Required Capability: See Capabilities and Permitted Actions

To restore and recover a database to a new host with a different directory structure:

Copy the init<SID>.ora from the old host to the new host.
Edit the init<SID>.ora file on the new host to reflect all the directory structure changes (i.e., change the path for control files, archivelog destination and *dump destinations).
Create the directory structures as defined in init<SID>.ora file for all paths.
Configure the destination machine's $TNS_ADMIN/tnsnames.ora file to include the Recovery Catalog database's service entry. The easiest way to configure this file is to copy the Recovery Catalog database's service entry from the source machine's tnsnames.ora file and append it to the destination machine's tnsnames.ora file. The Recovery Catalog database's service entry should look similar to the following:
<service_name> =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = <protocol>)(HOST = <host>) (PORT = <##>))
(CONNECT_DATA = (SID = <Recovery Catalog database>)))
Make sure that ORACLE_SID is set to the database that you are restoring and that ORACLE_HOME is set appropriately. Note the following example for Solaris:
#export ORACLE_SID= <target database SID>
#export ORACLE_HOME= <Oracle home directory>

Note the following example for Windows 2000 machines:
C:\set ORACLE_SID= <target database SID>
C:\set ORACLE_HOME= <Oracle home directory>

Make sure that the <username>you supply for the destination machine is different than the username for the source machine.

When you are granting the user database permissions, make sure to include the recovery_catalog_owner option shown above.

Transfer the Oracle password file "orapw<Oracle SID name>" from the source machine to the destination machine. Usually this file resides in ORACLE_HOME/dbs.
From the source machine, use the Oracle exp command to export the Recovery Catalog data. You are exporting the data by user. For example, if the user ID for the Recovery Catalog owner is rman, you would export the database backup information for the user rman.
From the source machine, use the Oracle imp command to import the contents of the file you created in the previous step into the new user account for the destination machine. Depending on the version of Oracle that you are running, you may receive the following error when you run the imp command:
IMP-00044: unable to allocate enough memory for statement
Perform these steps if you receive an error while running the imp command:
- Drop the user.
- Recreate the user.
- Rerun the imp command.
- When you rerun the imp command, enter 1000000 when prompted for the insert buffer file.
- If you receive the error message again, repeat the preceding steps and increase the buffer by a million each time you run imp until the error message is no longer displayed.
Ensure that the database in NOMOUNT mode in the destination machine.
If you want to perform the cross-machine restore from the CommCell Console then continue on with this procedure. Otherwise, if you want to perform the cross-machine restore from the RMAN command line using your own custom script, then exit this help and run the script now (refer to Oracle's Recovery Manager documentation for more information).
When performing cross-machine restore, do the following:
- Restore the control file and put the database in MOUNT mode.
- Login to SQL database in the destination computer and provide the following syntax:
  SQL> alter database rename file '/oracle/oradata/rman10g1/redo01.log' to '/space/oracle/oracle10g2/oradata/redo01.log';
  
  SQL> alter database rename file '/oracle/oradata/rman10g1/redo02.log' to '/space/oracle/oracle10g2/oradata/redo02.log';
  
  SQL> alter database rename file '/oracle/oradata/rman10g1/redo03.log' to '/space/oracle/oracle10g2/oradata/redo03.log';
  
  Here, '/oracle/oradata/rman10g1/ is the source redo log location and '/space/oracle/oracle10g2/oradata/ is the destination redo log location.
From the CommCell Browser, right-click the instance that contains the database you want to restore and recover to a new host, click All Tasks and then click Restore.
From the Oracle Restore Options (General) dialog box, select or enter the following:
- Click the name of the client computer to which you want to restore in the Destination Client box.
  
  If your destination client is not listed, check and ensure that all the requirements stated in the Before you Begin section is satisfied.
- Use the Catalog Connect fields to enter the connect string for the catalog database of the destination machine.
- Select the Restore Control File option.
- Select the Restore Data and Recover options.
  
  It is critical that the Recover option is selected, as Recover applies any incremental backups that are needed to bring the database back to a consistent state.
- Select the entire database in The Latest Database View pane (if it is not already selected).
Click the Advanced button and verify the following options are selected in the identified tab for the Oracle Advanced Restore Options dialog box:
- Restore Control File - To Point in Time in Ctrl & SP Files
  
  The Control file must be restored to a point in time that is later than or equal to time set for the Restore Data option in the Restore tab.
- Restore Data in Restore
  
  The Restore Data option must be earlier than or equal to the point in time that you specified for the Restore Control File option in the Ctrl & SP Files tab.
- Recover - Point In Time in Recover
  
  The point in time for the recover option must be later than or equal to the point in time specified for the Control file in the Ctrl & SP Files tab.
- Redirect All Table Spaces to, along with the path, in Redirect
  
  The path for datafiles should be created manually because Oracle or Oracle iDataAgent will not create that path.
Click OK on the Oracle Advanced Restore Options dialog box.
When restoring encrypted data, refer to Data Encryption.
Optionally for Oracle RAC, from the Oracle Restore Options (Stream) dialog box, set the instance restore order per stream allotment.

Begin or schedule the restore.

View the progress of the restore in the Job Controller window.
- In ARCHIVELOG mode - When the data is restored, click OK on the confirmation window. If desired, click Detail to review information on the restore operation.
- In NOARCHIVELOG mode - The job will report the restore as failed. This is because no archive redo log files exist. RMAN will report the following message, in reference to this error:
  
  RMAN-03022: compiling command: recover(4)
  RMAN-03026: error recovery releasing channel resources
  RMAN-08031: released channel: ch1
  RMAN-00571:
  ======================================================
  RMAN-00569:====== ERROR MESSAGE STACK FOLLOWS=========
  RMAN-00571:
  ======================================================
  RMAN-03002: failure during compilation of command
  RMAN-03013: command type: recover
  RMAN-06054: media recovery requesting unknown log: thread 1 scn 72077
  RMAN>
  Recovery Manager Complete.
Perform the following steps if your database is in the NOARCHIVELOG mode.
Manually recover and open the database using the following steps.
From the Server Manager window, execute the command displayed in the following example:
SVRMGR>recover database using backup control file until cancel;

Server Manager displays several messages, including the following:
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
Type cancel

The following message is displayed:
Media recovery cancelled.
Execute the commands displayed in the following example:
SVRMGR>alter database open resetlogs;
SVRMGR>exit
Reset the Recovery Catalog by executing the commands displayed in the following example:
#rman rcvcat <catalog connect string>
Recovery Manager: Release 8.1.5.00 - Production
RMAN-06008: connected to recovery catalog database
RMAN>connect target;
RMAN-06005: connected to target database: <database_name> DBID=<##>)
RMAN> reset database;
RMAN-03022: compiling command: reset
RMAN-03023: executing command: reset
RMAN-08006: database registered in recovery catalog
RMAN-03023: executing command: full resync
RMAN-08002: starting full resync of recovery catalog
RMAN-08004: full resync complete
RMAN>exit

Resetting the Recovery Catalog creates a new incarnation of the database. Before you can restore and recover the database to the current time, you must perform another full backup and wait for it to complete successfully.
Perform an immediate offline full backup.

Restore and Recover an Entire Database in ARCHIVELOG Mode to a Previous Point-In-Time

The following procedure describes the steps involved in restoring and recovering a database to a previous point-in-time. This procedure restores and recovers the database as follows:

From an online backup
With or without the control file(s) (since it must have a timestamp that is later than or equal to the datafiles)
To a point-in-time and to the original host
Using the Recovery Catalog

Before You Begin:

Review the general and agent-specific restore requirements accessed from Restore Backup Data prior to performing any restore.

Required Capability: See Capabilities and Permitted Actions

To restore and recover an entire database in ARCHIVELOG mode to a previous point-in-time:

From the CommCell Browser, right-click the instance that contains the database you want to restore and recover, click All Tasks and then click Restore.
From the Oracle Restore Options (General) dialog box, select the following options:
- Click the name of the client computer with the database you want to restore in the Destination Client box (if it is not already selected).
- Select the Restore Control File option, if you want to restore the control files.
- Select the Restore Data and Recover options.
- Select the entire database in The Latest Database View pane (if it is not already selected).
- Verify that the Status of the database is displayed as STARTED; if necessary click on the Refresh button to refresh the status.
Click on the Advanced button.
From the Ctrl & SP Files tab in the Oracle Advanced Restore Options dialog box, select the To Point in Time in the Restore Control File pane and enter the date and time to which you want the Control File(s) restored.

The control file(s) must be restored to a point-in-time that is later than or equal to the point-in-time set for the Restore Data option in the Restore tab.
From the Restore tab, select the To Point in Time in the Restore Data pane and enter the date and time to which you want the datafiles restored.

The data must be restored to a point-in-time that is earlier than or equal to the point-in-time set for the Restore Control File option in the Ctrl & SP Files tab.
From the Recover tab, select the To Point in Time in the Recover pane and enter the date and time to which you want the database recovered.

The point in time that you specify for the Recover option must be later than or equal to the point in time that you specified for the CONTROL FILE in the Ctrl & SP Files tab.
From the Options tab, type or select the database incarnation value in the Set DB Incarnation box, if you want to perform the restore from a backup of a previous incarnation.
Click OK in the Oracle Advanced Restore Options window.
When restoring encrypted data, refer to Data Encryption.
Optionally for Oracle RAC, from the Oracle Restore Options (Stream) dialog box, set the instance restore order per stream allotment.

Begin or schedule the restore.

While the job is running you can right-click the job in the Job Controller and select Details to view information on the job. After the data has been restored, you will see a job completion message in the Job Controller and Event Viewer.

If you recover the database to a previous point in time, or restore the control file, then you have to perform a full database backup. This is because a previous point in time recovery or restoring the control file will destroy all previous backups.

Restore and Recover an Entire Database in ARCHIVELOG Mode to the Current Time

The following procedure describes the steps involved in restoring and recovering a database running in ARCHIVELOG mode, with lost data files and control files.

This procedure restores and recovers the database as follows:

From an online backup
With the control file(s) (since they no longer exist)
To the current time and to the original host
Using the Recovery Catalog

Before You Begin:

Review the general and agent-specific restore requirements accessed from Restore Backup Data prior to performing any restore.

Required Capability: See Capabilities and Permitted Actions

To restore and recover Restore an entire database in ARCHIVELOG mode to the current time:

From the CommCell Browser, right-click the instance that contains the database you want to restore and recover, click All Tasks and then click Restore.
From the Oracle Restore Options (General) dialog box, select the following options:
- Select the name of the client computer with the database you want to restore in the Destination Client box (if it is not already selected).
- Select the Restore Control File option.
- Select the Restore Data and Recover options.
- Select the entire database in The Latest Database View pane (if it is not already selected).
- Verify that the Status of the database is displayed as STARTED; if necessary click on the Refresh button to refresh the status.
Click the Advanced button and verify the following options are selected in the identified tab for the Oracle Advanced Restore Options dialog box:
- Restore Control File (if you do not have one) in Ctrl & SP Files
- Restore Data - From the Latest Backup in Restore
- Recover - Current Time in Recover
Click OK in the Oracle Advanced Restore Options window.
When restoring encrypted data, refer to Data Encryption.
Optionally for Oracle RAC, from the Oracle Restore Options (Stream) dialog box, set the instance restore order per stream allotment.

Begin or schedule the restore.

While the job is running you can right-click the job in the Job Controller and select Details to view information on the job. After the data has been restored, you will see a job completion message in the Job Controller and Event Viewer.
The system automatically resets the logs and the database. Before you can restore and recover the database to the current time, it is good practice to perform another full backup and wait for it to complete successfully.

NOTES

If you restore the control file, then you have to perform a full database backup. This is because restoring the control file will destroy all previous backups.

Restore and Recover an Entire Database in NOARCHIVELOG Mode to the Latest Backup

The following procedure describes the steps involved in restoring and recovering an entire database when all datafiles and control files are lost. This procedure restores and recovers an entire database as follows:

From an offline backup
With the control files (since they no longer exist)
To the latest backup and to the original host
Using the Recovery Catalog

When you are restoring data from a database in NOARCHIVELOG mode, you must always restore and recover the entire database

Before You Begin:

Review the general and agent-specific restore requirements accessed from Restore Backup Data prior to performing any restore.

Required Capability: See Capabilities and Permitted Actions

To restore and recover an entire database in NOARCHIVELOG mode to the latest backup:

From the CommCell Browser, right-click the instance that contains the database you want to restore and recover, click All Tasks and then click Restore.
From the Oracle Restore Options (General) dialog box, select the following options:
- Select the name of the client computer with the database you want to restore in the Destination Client box (if it is not already selected).
- Select the Restore Control File option.
- Select the Restore Data and Recover options.
  
  It is critical that the Recover option is selected, as Recover applies any incremental backups that are needed to bring the database back to a consistent state.
- Select the entire database in The Latest Database View pane (if it is not already selected).
- Verify that the Status of the database is displayed as STARTED; if necessary click on the Refresh button to refresh the status.
Click the Advanced button and verify the following options are selected in the identified tab for the Oracle Advanced Restore Options dialog box:
- Restore Control File in Ctrl & SP Files
- Restore Data - From the Latest Backup in Restore
- Recover - Current Time in Recover
Click OK in the Oracle Advanced Restore Options window.
When restoring encrypted data, refer to Data Encryption.
Optionally for Oracle RAC, from the Oracle Restore Options (Stream) dialog box, set the instance restore order per stream allotment.

Begin or schedule the restore.

While the job is running you can right-click the job in the Job Controller and select Details to view information on the job. After the data has been restored, you will see a job completion message in the Job Controller and Event Viewer.

If you restore the control file, then you have to perform a full database backup. This is because restoring the control file will destroy all previous backups.

Restore and Recover an Entire Database in NOARCHIVELOG Mode to a Point-In-Time

The following procedure describes the steps involved in restoring and recovering an entire database when all data files and control files are lost. This procedure restores and recovers an entire database as follows:

From an offline backup
With the control files (since they no longer exist)
To the latest backup and to the original host
Using the Recovery Catalog

When you are restoring data from a database in NOARCHIVELOG mode, you must always restore and recover the entire database.

Before You Begin:

Review the general and agent-specific restore requirements accessed from Restore Backup Data prior to performing any restore.

Required Capability: See Capabilities and Permitted Actions

To restore and recover an entire database in NOARCHIVELOG mode to a point-in-time:

From the CommCell Browser, right-click the instance that contains the database you want to restore and recover, click All Tasks and then click Restore.
From the Oracle Restore Options (General) dialog box, select the following options:
- Select the name of the client computer with the database you want to restore in the Destination Client box (if it is not already selected).
- Select the Restore Control File option.
- Select the Restore Data and Recover options.
  
  It is critical that the Recover option is selected, as Recover applies any incremental backups that are needed to bring the database back to a consistent state.
- Select the entire database in The Latest Database View pane (if it is not already selected).
- Verify that the Status of the database is displayed as STARTED; if necessary click on the Refresh button to refresh the status.

Click the Advanced button and verify the following options are selected in the identified tab for the Oracle Advanced Restore Options dialog box:

Restore Control File - To Point in Time in Ctrl & SP Files

The Control file must be restored to a point in time that is later than or equal to time set for the Restore Data option in the Restore tab.
Restore Data in Restore

The Restore Data option must be earlier than or equal to the point in time that you specified for the Restore Control File option in the Ctrl & SP Files tab.

Recover - Point In Time in Recover

The point in time for the recover option must be later than or equal to the point in time specified for the Restore Control File in the Ctrl & SP Files tab.

If you recover the database to a previous point in time and restore the control file, then you have to perform a full database backup. This is because a previous point in time recovery and restoring the control file will destroy all previous backups.

Click OK in the Oracle Advanced Restore Options window.
When restoring encrypted data, refer to Data Encryption.
Optionally for Oracle RAC, from the Oracle Restore Options (Stream) dialog box, set the instance restore order per stream allotment.

Begin or schedule the restore.

View the progress of the restore in the Job Controller window.
The job will report the restore as failed. This is because no archive redo log files exist. RMAN will report the following message, in reference to this error:
RMAN-00569: =========error message stack follows============
RMAN-03002: failure during compilation of command
RMAN-03013: command type: recover
RMAN-06038: recovery catalog package detected an error
RMAN-03013: command type: recover(4)
RMAN-20242: specification does not match any archivelog in the recovery catalog
Manually recover and open the database using the following steps.
Make sure that ORACLE_SID is set to the database you are restoring and that ORACLE_HOME is set appropriately. Note the following example:
#export ORACLE_SID= <target database SID>
#export ORACLE_HOME= <Oracle home directory>
From the Server Manager window, execute the command displayed in the following example:
SVRMGR>recover database using backup control file until cancel;
Server Manager displays several messages, including the following:
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
Type cancel
The following message is displayed:
Media recovery cancelled.
Execute the commands displayed in the following example:
SVRMGR>alter database open resetlogs;
SVRMGR>exit
Reset the Recovery Catalog by executing the commands displayed in the following example:
rman rcvcat <catalog connect string>
Recovery Manager: Release 8.1.5.00 - Production
RMAN-06008: connected to recovery catalog database
RMAN>connect target;
RMAN-06005: connected to target database: <database_name> DBID=<##>)
RMAN> reset database;
RMAN-03022: compiling command: reset
RMAN-03023: executing command: reset
RMAN-08006: database registered in recovery catalog
RMAN-03023: executing command: full resync
RMAN-08002: starting full resync of recovery catalog
RMAN-08004: full resync complete
RMAN>exit
Resetting the Recovery Catalog creates a new incarnation of the database. Before you can restore and recover the database to the current time, you must perform another full backup and wait for it to complete successfully.
Perform an immediate offline full backup.

Restore and Recover One Control File from an Existing Control File

The following procedure describes the steps involved in restoring one lost control file from other control files that exist.

Before You Begin:

Review the general and agent-specific restore requirements accessed from Restore Backup Data prior to performing any restore.

Required Capability: See Capabilities and Permitted Actions

To restore and recover one control file from an existing control file:

Shutdown the database.
Copy one of the existing control files to the missing control file.
Verify that new control file has the same owner, group, and file permissions as the original control file.
Startup the database.

Restore and Recover All Control Files

Before You Begin:

Review the general and agent-specific restore requirements accessed from Restore Backup Data prior to performing any restore.
If all control files have been lost and datafiles have been lost, restore and recover the control files using the Restore and Recover an Entire Database in ARCHIVELOG Mode to the Current time procedure.

Required Capability: See Capabilities and Permitted Actions

To restore and recover all control files:

Create a new control file using the Oracle create control file command.
For instructions, refer to your Oracle documentation.
Recover the database.

NOTES

After you restore the control file successfully, perform a full database backup. This is because restoring the control file will destroy all previous backups.

Restore Archive Log Files

Before You Begin:

Review the general and agent-specific restore requirements accessed from Restore Backup Data prior to performing any restore.
Make sure that the DBID value for the particular database is displayed in the Instance properties dialog box. If you have not yet created an instance for the database, refer to Create/Modify an Instance for more information.

Required Capability: See Capabilities and Permitted Actions

To restore archive log files using the CommCell Console:

From the CommCell Browser, right-click the instance, select All Tasks then click Restore.
From the Oracle Restore Options (General) tab, select Restore Archive Log. You can also select Restore Data and Recover options if required.
Click Advanced.
From the Advanced Restore Options (Restore) tab, select Restore Archive Logs.
Select any of the following criteria to restore the archive log files:
- Select By Log Time to restore archive log with start time (mm/dd/yy:hh/mm/ss) and End time (mm/dd/yy:hh/mm/ss).
- Select By Log Serial Number (LSN) to restore archive logs based on the specified Log Sequence Numbers (LSNs) that you specify. Specify the Start number (enter log sequence number) and End number (enter log sequence number) to restore archive logs.
If you want to save the archive logs in a different location, enter the path in Target Directory field or click Browse to select a new location.
Click OK to save the settings.

Restore Control Files from Autobackup

Before You Begin:

Review the general and agent-specific restore requirements accessed from Restore Backup Data prior to performing any restore.
Autobackup is only available in Oracle 9i and 10g. If you have not yet configured autobackup of control files, refer to Configuring Autobackup of Control Files for more information.
Make sure that the DBID value for the particular database is displayed in the Instance properties dialog box. If you have not yet created an instance for the database, refer to Create/Modify an Instance for more information.

Required Capability: See Capabilities and Permitted Actions

To restore control files from autobackup using the CommCell Console:

From the CommCell Browser, right-click the instance, select All Tasks then click Restore.
From the Oracle Restore Options (General) tab, click Advanced.
Click the Control and SP Files tab of the Oracle Advanced Restore Options dialog box, then select the options for Restore Control File and From Autobackup.
Click the Options tab in the Oracle Advanced Restore Options dialog box, and select Set DBID. This option will distinguish the target database from the rest of the databases that have the same name in the recovery catalog.
Enter or select any other desired options on this tab, then click OK to save the settings.
Begin or schedule the restore.

Required Capability: See Capabilities and Permitted Actions

To restore control files from autobackup using RMAN:

Start up the target instance in NOMOUNT mode.
Start RMAN, but do not issue any connect statements.
At the RMAN prompt, set the dbid (if you do not know the dbid, you can get it from the RMAN log of the control file autobackup):
RMAN> set dbid=<your_DBID>;
After setting the dbid, connect to the target instance that has been started in NOMOUNT mode:
RMAN> connect target;
Enter the following commands/parameters from the RMAN prompt:
RMAN> run {
2> allocate channel ch1 type 'sbt_tape';
3> restore controlfile from autobackup;
4> }
Mount the database from the restored control file:
RMAN> alter database mount;
Restore and recover the database:
RMAN> run {
2> allocate channel ch1 type 'sbt_tape';
3> restore database;
4> recover database;
5> alter database open resetlogs;
6> }
RMAN> exit

Validate a Backup or Restore

Related Topics

Oracle iDataAgent: Ensuring Successful Oracle Data Protection and Recovery Operations
Oracle RAC iDataAgent: Ensuring Successful Oracle Data Protection and Recovery Operations

See Also:

Required Capability: See Capabilities and Permitted Actions

To validate a backup:

From the CommCell Browser, right-click the subclient containing the backup data you want to validate, then click Properties.
Click the Backup Arguments tab, then select Validate and click OK.
Start a Backup for the subclient. A Validate job will run, which will cause RMAN to examine the database and scan all of the backup pieces to verify that the backup can be successfully restored.
Once the Validate job completes you can view the log file for the job to determine whether there were any errors in the validation. To view the log file:
- From the CommCell Browser, right-click the subclient, click View and then click Backup History.
- Click OK on the History Filter dialog.
- On the Job History window, right-click the Validate job, then select View Log File. The RMAN Output Log will display for the job.
- If you determine that there are any errors in the validation, take the appropriate corrective action before running the actual backup.

Required Capability: See Capabilities and Permitted Actions

To validate a restore:

From the CommCell Browser, right-click the instance whose restore you want to validate, select All Tasks, then click Restore.
From the Restore Options dialog, click Advanced.
Click the Options tab, then select Validate and click OK.
NOTE: For the Oracle iDataAgent, keep in mind that the Options tab is unavailable when the Duplicate DB option is selected on the Restore Options (General) tab.
Start a Basic Restore for the Instance. A Validate job will run, which will cause RMAN to decide which database pieces need to be restored and then scans them to verify their contents, but no output will be created and no data will be over-written.
Once the Validate job completes you can view the log file for the job to determine whether there were any errors in the validation. To view the log file:
- From the CommCell Browser, right-click the instance, click View and then click Restore History.
- Click OK on the History Filter dialog.
- On the Job History window, right-click the Validate job, then select View Log File. The RMAN Output Log will display for the job.
- If you determine that there are any errors in the validation, take the appropriate corrective action before running the actual restore.

Create a Duplicate Database on a Different Host without the Instance Configured

The following procedure describes the steps involved in creating a duplicate database on a different host without the instance configured.

Before You Begin:

Review information on the Duplicate Database feature before beginning this procedure.
Perform the Prerequisite Setup Steps for Creating a Duplicate Database.

Required Capability: See Capabilities and Permitted Actions

To create a duplicate database on a different host without the instance configured:

From the CommCell Console, right-click the source host instance then select All Tasks -> Restore.
From the Oracle Restore Options (General) dialog box, select the Duplicate DB checkbox and click Advanced.
From the Duplicate tab in the Oracle Duplicate Options dialog box, select the Duplicate To checkbox and enter the name for the duplicate database in the Database Name field. Click OK.
From the Oracle Restore Options (General) dialog box, select the Destination Client from the list (when the instance is not configured, the destination client must be the source host) then enter the Catalog Connect string and click Advanced.
From the Duplicate tab in the Oracle Duplicate Options dialog box, configure the following fields:
- Pfile - For Oracle 10g and 9i, type in or Browse to the location of the Startup Pfile.
- Open Restricted - For Oracle 10g, you can select this option if you want to open the database in restricted mode.
- Log File - Select this option, then specify Group or File and click the appropriate Add button to enter specifications for the redo log group/file.
From the Recover tab in the Advanced Restore Options dialog box, select the appropriate recover option.
Select any other desired options, then click Redirect in the Advanced Restore Options dialog box.

From the Redirect tab, choose one of the following then click OK:

To redirect all tablespaces to the same location, select the Redirect All Table Spaces to: checkbox then type in or Browse to the new path.
To redirect tablespaces/datafiles to different locations, select the Redirect checkbox then click the desired objects in the Object column to highlight them, and either type in or Browse to the new path. Click Apply. Repeat this process until all tablespaces/datafiles have been redirected.

To redirect the database temp file, use the DB_FILE_NAME_CONVERT parameter in the initial file for the new database instance. Similarly, to redirect the log files, you can either use the LOG_FILE_NAME_CONVERT parameter in the initial file or use the Log File option in the Advanced Restore Options (Duplicate) dialog box. For more information on setting the parameters in the initial file, see Prerequisite Setup Steps for Creating a Duplicate Database.

From the Duplicate DB Options tab in the Oracle Duplicate Options dialog box, configure the following options as desired:
- Time Zone - Select a time zone for a point-in-time recovery.
- No Filename Check - Select this option to prevent RMAN from performing a check for target datafiles sharing the same names as the duplicated files to see if they are in use. This option is required when you are using the same path (i.e., the standby and primary datafiles and logs have identical filenames).
Click OK on the Advanced Restore Options dialog box.
Begin or schedule the restore. Once the job begins, if you see a pop-up message about the database state, ensure that the duplicate database is in NOMOUNT mode then click Yes to continue.
Verify that the restore completed successfully and that the database is restored to the destination host. If you selected the Recover option verify that the database is consistent.

Create a Duplicate Database on a Different Host with the Instance Configured

The following procedure describes the steps involved in creating a duplicate database on a different host with the instance configured.

Before You Begin:

Review information on the Duplicate Database feature before beginning this procedure.
Perform the Prerequisite Setup Steps for Creating a Duplicate Database.

Required Capability: See Capabilities and Permitted Actions

To create a duplicate database on a different host with the instance configured:

From the CommCell Console, right-click the source host instance then select All Tasks -> Restore.
From the Oracle Restore Options (General) dialog box, select the Duplicate DB checkbox and click Advanced.
From the Duplicate tab in the Oracle Duplicate Options dialog box, select the Duplicate To checkbox and enter the name for the duplicate database in the Database Name field. Click OK.
From the Oracle Restore Options (General) dialog box, select the Destination Client from the list then enter the Catalog Connect string and click Advanced.
From the Duplicate tab in the Oracle Duplicate Options dialog box, configure the following fields:
- Pfile - For Oracle 10g and 9i, type in or Browse to the location of the Startup Pfile.
- Open Restricted - For Oracle 10g, you can select this option if you want to open the database in restricted mode.
- Log File - Select this option, then specify Group or File and click the appropriate Add button to enter specifications for the redo log group/file.
From the Recover tab in the Advanced Restore Options dialog box, select the appropriate recover option.
Select any other desired options, then click Redirect in the Advanced Restore Options dialog box.

From the Redirect tab, choose one of the following then click OK:

To redirect all tablespaces to the same location, select the Redirect All Table Spaces to: checkbox then type in or Browse to the new path.
To redirect tablespaces/datafiles to different locations, select the Redirect checkbox then click the desired objects in the Object column to highlight them, and either type in or Browse to the new path. Click Apply. Repeat this process until all tablespaces/datafiles have been redirected.

From the Duplicate DB Options tab in the Oracle Duplicate Options dialog box, configure the following options as desired:
- Time Zone - Select a time zone for a point-in-time recovery.
- No Filename Check - Select this option to prevent RMAN from performing a check for target datafiles sharing the same names as the duplicated files to see if they are in use. This option is required when you are using the same path (i.e., the standby and primary datafiles and logs have identical filenames).
Click OK on the Advanced Restore Options dialog box.
Begin or schedule the restore. Once the job begins, if you see a pop-up message about the database state, ensure that the duplicate database is in NOMOUNT mode then click Yes to continue.
Verify that the restore completed successfully and that the database is restored to the destination host. If you selected the Recover option verify that the database is consistent.

Create a Duplicate Database on the Same Host without the Instance Configured

The following procedure describes the steps involved in creating a duplicate database on the same host without the instance configured.

Before You Begin:

Review information on the Duplicate Database feature before beginning this procedure.
Perform the Prerequisite Setup Steps for Creating a Duplicate Database.

Required Capability: See Capabilities and Permitted Actions

To create a duplicate database on the same host without the instance configured:

From the CommCell Console, right-click the source host instance then select All Tasks -> Restore.
From the Oracle Restore Options (General) dialog box, select the Duplicate DB checkbox then enter the Catalog Connect string and click Advanced.
From the Duplicate tab in the Oracle Duplicate Options dialog box, configure the following fields:
- Duplicate To - Select this option then enter the name for the duplicate database in the Database Name field.
- Pfile - For Oracle 10g and 9i, type in or Browse to the location of the Startup Pfile.
- Open Restricted - For Oracle 10g, you can select this option if you want to open the database in restricted mode.
- Log File - Select this option, then specify Group or File and click the appropriate Add button to enter specifications for the redo log group/file.
From the Recover tab in the Advanced Restore Options dialog box, select the appropriate recover option.
Select any other desired options, then click Redirect in the Advanced Restore Options dialog box.

From the Redirect tab, choose one of the following then click OK:

To redirect all tablespaces to the same location, select the Redirect All Table Spaces to: checkbox then type in or Browse to the new path.
To redirect tablespaces/datafiles to different locations, select the Redirect checkbox then click the desired objects in the Object column to highlight them, and either type in or Browse to the new path. Click Apply. Repeat this process until all tablespaces/datafiles have been redirected.

From the Duplicate DB Options tab in the Oracle Duplicate Options dialog box, configure the following options as desired:
- Time Zone - Select a time zone for a point-in-time recovery.
- No Filename Check - Select this option to prevent RMAN from performing a check for target datafiles sharing the same names as the duplicated files to see if they are in use. This option is required when you are using the same path (i.e., the standby and primary datafiles and logs have identical filenames).
Click OK on the Advanced Restore Options dialog box.
Begin or schedule the restore. Once the job begins, if you see a pop-up message about the database state, ensure that the duplicate database is in NOMOUNT mode then click Yes to continue.
Verify that the restore completed successfully and that the database is restored to the destination host. If you selected the Recover option verify that the database is consistent.

Create a Duplicate Database on the Same Host with the Instance Configured

The following procedure describes the steps involved in creating a duplicate database on the same host with the instance configured.

Review information on the Duplicate Database feature before beginning this procedure.
Perform the Prerequisite Setup Steps for Creating a Duplicate Database.

Required Capability: See Capabilities and Permitted Actions

To create a duplicate database on the same host with the instance configured:

From the CommCell Console, right-click the source host instance then select All Tasks -> Restore.
From the Oracle Restore Options (General) dialog box, select the Duplicate DB checkbox then enter the Catalog Connect string and click Advanced.
From the Duplicate tab in the Oracle Duplicate Options dialog box, configure the following fields:
- Duplicate To - Select this option then enter the name for the duplicate database in the Database Name field.
- Pfile - For Oracle 10g and 9i, type in or Browse to the location of the Startup Pfile.
- Open Restricted - For Oracle 10g, you can select this option if you want to open the database in restricted mode.
- Log File - Select this option, then specify Group or File and click the appropriate Add button to enter specifications for the redo log group/file.
From the Recover tab in the Advanced Restore Options dialog box, select the appropriate recover option.
Select any other desired options, then click Redirect in the Advanced Restore Options dialog box.

From the Redirect tab, choose one of the following then click OK:

To redirect all tablespaces to the same location, select the Redirect All Table Spaces to: checkbox then type in or Browse to the new path.
To redirect tablespaces/datafiles to different locations, select the Redirect checkbox then click the desired objects in the Object column to highlight them, and either type in or Browse to the new path. Click Apply. Repeat this process until all tablespaces/datafiles have been redirected.

From the Duplicate DB Options tab in the Oracle Duplicate Options dialog box, configure the following options as desired:
- Time Zone - Select a time zone for a point-in-time recovery.
- No Filename Check - Select this option to prevent RMAN from performing a check for target datafiles sharing the same names as the duplicated files to see if they are in use. This option is required when you are using the same path (i.e., the standby and primary datafiles and logs have identical filenames).
Click OK on the Advanced Restore Options dialog box.
Begin or schedule the restore. Once the job begins, if you see a pop-up message about the database state, ensure that the duplicate database is in NOMOUNT mode then click Yes to continue.
Verify that the restore completed successfully and that the database is restored to the destination host. If you selected the Recover option verify that the database is consistent.

Preview a Script

Related Topics

Ensuring Successful Oracle Data Protection and Recovery Operations

Required Capability: See Capabilities and Permitted Actions

To preview a backup script:

From the CommCell Browser, right-click the subclient containing the data whose backup script you want to preview, then click Backup.
From the Backup Options dialog, click Script Preview.
To change the script, click OK to close the preview window, then enter the desired changes on the Backup Options and Advanced Backup Options dialogs, and click Script Preview again to see if the script now reflects the configuration you want. Repeat this if necessary to achieve the desired result.
Once you are satisfied with the script, perform one of the following actions:
- To have the system run the script in RMAN, click OK to close the preview windows, then click OK on the Backup Options dialog to save the current settings. This script will be executed the next time that a backup is run for this subclient.
- To run the script yourself in RMAN, you can copy and paste the script from the preview window into a text file for that purpose (or select the Save as Script option on the Backup Options dialog). Click OK to close the preview window. Click OK to save the subclient configuration changes.

Required Capability: See Capabilities and Permitted Actions

To preview a restore script:

From the CommCell Browser, right-click the instance containing the data whose restore script you want to preview, select All Tasks, then click Restore (or click Browse Backup Data).
From the Oracle Restore Options (General) dialog, click Script Preview.
To change the script, click OK to close the preview window, then enter the desired changes on the Restore Options and Advanced Restore Options dialogs, and click Script Preview again to see if the script now reflects the restore settings you want. Repeat this if necessary to achieve the desired result.
Once you are satisfied with the script, perform one of the following actions:
- To have the system run the script in RMAN, click OK to close the preview window, then click OK on the Restore Options dialog to save the current settings. This script will be executed the next time that a restore is run for this instance.
- To run the script yourself in RMAN, you can copy and paste the script from the preview window into a text file for that purpose (or select the Save as Script option on the Restore Options (Job Initiation) tab). Click OK to close the preview window. Click OK to save the restore settings.

NOTES:

Copying the script from the preview window can be accomplished by pressing <CTRL><C> from the CommCell Console.

Create a Standby Database on a Different Host without the Instance Configured

The following procedure describes the steps involved in creating a standby database on a different host without the instance configured.

Before You Begin

Review the general restore requirements accessed from Restore Backup Data, and the agent-specific restore requirements accessed from Restore Data - Oracle prior to performing any restore.
Review information on the Duplicate Database feature before beginning this procedure.
Prerequisite Setup Steps:
- From the RMAN command line, run an online full backup with CURRENT CONTROLFILE FOR STANDBY of the primary database on the source host. This backup will be used to create the standby database and standby control file.
- Standby Database Preparation (We strongly recommend that you consult the Oracle9i or Oracle10g Data Guard Concepts and Administration guide for more detailed information on this process):
  - Create the standby control file from the backup of the primary control file.
  - Choose filenames for the standby datafiles.
  - Choose filenames for the standby database online redo logs.
  - Set the necessary initialization parameters in the primary initialization parameter file (i.e., Startup PFile).
  - Create an initialization parameter file for the standby database and configure the necessary parameters. Ensure that the Startup Pfile init<SID>.ora is copied from the destination host to the target host with the same path as it is in the target host.
  - Perform any Oracle Net setup and configuration required to connect to the standby database. For example, set up the listener and configure the destination computer's $TNS_ADMIN/tnsnames.ora file for the standby database.
  - Start the standby database in NOMOUNT mode.
- You must create a new instance on the same host before performing this procedure. The new instance should be in NOMOUNT mode. There should be a valid connect string for the auxiliary channel (used to duplicate the database). The system assumes and uses sys/change_on_install for the auxiliary channel. However, you must use this connect string to connect to the auxiliary database when the instance is not configured. Once the instance is configured, ensure that you set the same password for the SYS user account for every primary and standby databases, for the redo data transmission to succeed.
- Do not create a new instance for the destination host in the CommCell Console.
- Ensure that the Oracle iDataAgent is installed on the Destination host.

For Oracle 10g, ensure that you set the Standby Role Initialization parameter, DB_FILE_NAME_CONVERT,to add all the temp data files from the primary database location to the standby database location, as follows:

DB_FILE_NAME_CONVERT='<primary_database_temp_datafile_old _location>','<standby_database_temp_datafile_new_location>'

If this parameter is not set, restore will fail with the following error message:

temporary file TEMP01.DBF conflicts with file used by target database

Required Capability: See Capabilities and Permitted Actions

To create a standby database on a different host without the instance configured:

From the CommCell Console, right-click the source host instance then select All Tasks -> Restore.
From the Oracle Restore Options (General) dialog box, select the Duplicate DB checkbox and enter the Catalog Connect string, then click Advanced.
Click the Duplicate DB Options tab, select the Duplicate For Standby option then enter the Oracle System Identifier for the standby database in the Oracle SID field. Optionally, you may configure any of the following options as desired:
- Time Zone - Select a time zone for a point-in-time recovery.
- No Filename Check - Select this option to prevent RMAN from performing a check for target datafiles sharing the same names as the duplicated files to see if they are in use. This option is required when you are using the same path (i.e., the standby and primary datafiles and logs have identical filenames).
- Do Recover - Select this option to recover the standby database after it has been created.
Click the Recover tab, then select the appropriate recover option.
Click the Redirect tab, then choose one of the following and click OK:
- To redirect all tablespaces to the same location, select the Redirect All Table Spaces to: checkbox then type in or Browse to the new path.
- To redirect tablespaces/datafiles to different locations, select the Redirect checkbox then click the desired objects in the Object column to highlight them, and either type in or Browse to the new path. Click Apply. Repeat this process until all tablespaces/datafiles have been redirected.
Select any other applicable options in the Oracle Duplicate Options dialog box, then click OK.
From the Oracle Restore Options (General) dialog box, select the Destination Client from the list (when the instance is not configured, the destination client must be the source host).
Begin or schedule the restore. Once the job begins, if you see a pop-up message about the database state, ensure that the standby database is in NOMOUNT mode then click Yes to continue.
Verify that the restore completed successfully and that the database is restored to the destination host. If you selected the Recover option verify that the database is consistent.

Create a Standby Database on a Different Host with the Instance Configured

The following procedure describes the steps involved in creating a standby database on a different host with the instance configured.

Before You Begin

Review the general restore requirements accessed from Restore Backup Data, and the agent-specific restore requirements accessed from Restore Data - Oracle prior to performing any restore.
Review information on the Duplicate Database feature before beginning this procedure.
Prerequisite Setup Steps:
- From the RMAN command line, run an online full backup with CURRENT CONTROLFILE FOR STANDBY of the primary database on the source host. This backup will be used to create the standby database and standby control file.
- Standby Database Preparation (We strongly recommend that you consult the Oracle9i or Oracle10g Data Guard Concepts and Administration guide for more detailed information on this process):
  - Create the standby control file from the backup of the primary control file.
  - Choose filenames for the standby datafiles.
  - Choose filenames for the standby database online redo logs.
  - Set the necessary initialization parameters in the primary initialization parameter file (i.e., Startup PFile).
  - Create an initialization parameter file for the standby database and configure the necessary parameters. Ensure that the Startup Pfile init<SID>.ora is copied from the destination host to the target host with the same path as it is in the target host.
  - Perform any Oracle Net setup and configuration required to connect to the standby database. For example, set up the listener and configure the destination computer's $TNS_ADMIN/tnsnames.ora file for the standby database.
  - Start the standby database in NOMOUNT mode.
- You must create a new instance on the same host before performing this procedure. The new instance should be in NOMOUNT mode. There should be a valid connect string for the auxiliary channel (used to duplicate the database). The system assumes and uses sys/change_on_install for the auxiliary channel. However, you must use this connect string to connect to the auxiliary database when the instance is not configured. Once the instance is configured, ensure that you set the same password for the SYS user account for every primary and standby databases, for the redo data transmission to succeed.
- Configure the Oracle instance in the CommCell Console.
- Ensure that the instances are saved properly in the CommCell Console, then open the instance properties and verify that the Oracle instance status of the standby database is NOMOUNT.

DB_FILE_NAME_CONVERT='<primary_database_temp_datafile_old _location>','<standby_database_temp_datafile_new_location>'

If this parameter is not set, restore will fail with the following error message:

temporary file TEMP01.DBF conflicts with file used by target database

Required Capability: See Capabilities and Permitted Actions

To create a standby database on a different host with the instance configured:

From the CommCell Console, right-click the source host instance then select All Tasks -> Restore.
From the Oracle Restore Options (General) dialog box, select the Duplicate DB checkbox and enter the Catalog Connect string, then click Advanced.
Click the Duplicate DB Options tab, select the Duplicate For Standby option then enter the Oracle System Identifier for the standby database in the Oracle SID field. Optionally, you may configure any of the following options as desired:
- Time Zone - Select a time zone for a point-in-time recovery.
- No Filename Check - Select this option to prevent RMAN from performing a check for target datafiles sharing the same names as the duplicated files to see if they are in use. This option is required when you are using the same path (i.e., the standby and primary datafiles and logs have identical filenames).
- Do Recover - Select this option to recover the standby database after it has been created.
Click the Recover tab, then select the appropriate recover option.
Click the Redirect tab, then choose one of the following and click OK:
- To redirect all tablespaces to the same location, select the Redirect All Table Spaces to: checkbox then type in or Browse to the new path.
- To redirect tablespaces/datafiles to different locations, select the Redirect checkbox then click the desired objects in the Object column to highlight them, and either type in or Browse to the new path. Click Apply. Repeat this process until all tablespaces/datafiles have been redirected.
Select any other applicable options in the Oracle Duplicate Options dialog box, then click OK.
Begin or schedule the restore. Once the job begins, if you see a pop-up message about the database state, ensure that the standby database is in NOMOUNT mode then click Yes to continue.
Verify that the restore completed successfully and that the database is restored to the destination host. If you selected the Recover option verify that the database is consistent.

Create a Standby Database on the Same Host without the Instance Configured

The following procedure describes the steps involved in creating a standby database on the same host without the instance configured.

Before You Begin

Review the general restore requirements accessed from Restore Backup Data, and the agent-specific restore requirements accessed from Restore Data - Oracle prior to performing any restore.
Review information on the Duplicate Database feature before beginning this procedure.
Prerequisite Setup Steps:
- From the RMAN command line, run an online full backup with CURRENT CONTROLFILE FOR STANDBY of the primary database on the source host. This backup will be used to create the standby database and standby control file.
- Standby Database Preparation (We strongly recommend that you consult the Oracle9i or Oracle10g Data Guard Concepts and Administration guide for more detailed information on this process):
  - Create the standby control file from the backup of the primary control file.
  - Choose filenames for the standby datafiles.
  - Choose filenames for the standby database online redo logs.
  - Set the necessary initialization parameters in the primary initialization parameter file (i.e., Startup PFile).
  - Create an initialization parameter file for the standby database and configure the necessary parameters.
  - Perform any Oracle Net setup and configuration required to connect to the standby database. For example, set up the listener and configure the destination computer's $TNS_ADMIN/tnsnames.ora file for the standby database.
  - Start the standby database in NOMOUNT mode.
- You must create a new instance on the same host before performing this procedure. The new instance should be in NOMOUNT mode. There should be a valid connect string for the auxiliary channel (used to duplicate the database). The system assumes and uses sys/change_on_install for the auxiliary channel. However, you must use this connect string to connect to the auxiliary database when the instance is not configured. Once the instance is configured, ensure that you set the same password for the SYS user account for every primary and standby databases, for the redo data transmission to succeed.
- Do not create a new instance for the destination host in the CommCell Console.

DB_FILE_NAME_CONVERT='<primary_database_temp_datafile_old _location>','<standby_database_temp_datafile_new_location>'

If this parameter is not set, restore will fail with the following error message:

temporary file TEMP01.DBF conflicts with file used by target database

Required Capability: See Capabilities and Permitted Actions

To create a standby database on the same host without the instance configured:

From the CommCell Console, right-click the source host instance then select All Tasks -> Restore.
From the Oracle Restore Options (General) dialog box, select the Duplicate DB checkbox and enter the Catalog Connect string, then click Advanced.
Click the Duplicate DB Options tab, select the Duplicate For Standby option then enter the Oracle System Identifier for the standby database in the Oracle SID field. Optionally, you may configure any of the following options as desired:
- Time Zone - Select a time zone for a point-in-time recovery.
- No Filename Check - Select this option to prevent RMAN from performing a check for target datafiles sharing the same names as the duplicated files to see if they are in use. This option is required when you are using the same path (i.e., the standby and primary datafiles and logs have identical filenames).
- Do Recover - Select this option to recover the standby database after it has been created.
Click the Recover tab, then select the appropriate recover option.
Click the Redirect tab, then choose one of the following and click OK:
- To redirect all tablespaces to the same location, select the Redirect All Table Spaces to: checkbox then type in or Browse to the new path.
- To redirect tablespaces/datafiles to different locations, select the Redirect checkbox then click the desired objects in the Object column to highlight them, and either type in or Browse to the new path. Click Apply. Repeat this process until all tablespaces/datafiles have been redirected.
Select any other applicable options in the Oracle Duplicate Options dialog box, then click OK.
Begin or schedule the restore. Once the job begins, if you see a pop-up message about the database state, ensure that the standby database is in NOMOUNT mode then click Yes to continue.
Verify that the restore completed successfully and that the database is restored to the destination host. If you selected the Recover option verify that the database is consistent.

Create a Standby Database on the Same Host with the Instance Configured

The following procedure describes the steps involved in creating a standby database on the same host with the instance configured.

Before You Begin

Review the general restore requirements accessed from Restore Backup Data, and the agent-specific restore requirements accessed from Restore Data - Oracle prior to performing any restore.
Review information on the Duplicate Database feature before beginning this procedure.
Prerequisite Setup Steps:
- From the RMAN command line, run an online full backup with CURRENT CONTROLFILE FOR STANDBY of the primary database on the source host. This backup will be used to create the standby database and standby control file.
- Standby Database Preparation (We strongly recommend that you consult the Oracle9i or Oracle10g Data Guard Concepts and Administration guide for more detailed information on this process):
  - Create the standby control file from the backup of the primary control file.
  - Choose filenames for the standby datafiles.
  - Choose filenames for the standby database online redo logs.
  - Set the necessary initialization parameters in the primary initialization parameter file (i.e., Startup PFile).
  - Create an initialization parameter file for the standby database and configure the necessary parameters.
  - Perform any Oracle Net setup and configuration required to connect to the standby database. For example, set up the listener and configure the destination computer's $TNS_ADMIN/tnsnames.ora file for the standby database.
  - Start the standby database in NOMOUNT mode.
- You must create a new instance on the same host before performing this procedure. The new instance should be in NOMOUNT mode. There should be a valid connect string for the auxiliary channel (used to duplicate the database). The system assumes and uses sys/change_on_install for the auxiliary channel. However, you must use this connect string to connect to the auxiliary database when the instance is not configured. Once the instance is configured, ensure that you set the same password for the SYS user account for every primary and standby databases, for the redo data transmission to succeed.
- Configure the Oracle instance in the CommCell Console.
- Ensure that the instances are saved properly in the CommCell Console, then open the instance properties and verify that the Oracle instance status of the standby database is NOMOUNT.

DB_FILE_NAME_CONVERT='<primary_database_temp_datafile_old _location>','<standby_database_temp_datafile_new_location>'

If this parameter is not set, restore will fail with the following error message:

temporary file TEMP01.DBF conflicts with file used by target database

Required Capability: See Capabilities and Permitted Actions

To create a standby database on the same host with the instance configured:

From the CommCell Console, right-click the source host instance then select All Tasks -> Restore.
From the Oracle Restore Options (General) dialog box, select the Duplicate DB checkbox and enter the Catalog Connect string, then click Advanced.
Click the Duplicate DB Options tab, select the Duplicate For Standby option then enter the Oracle System Identifier for the standby database in the Oracle SID field. Optionally, you may configure any of the following options as desired:
- Time Zone - Select a time zone for a point-in-time recovery.
- No Filename Check - Select this option to prevent RMAN from performing a check for target datafiles sharing the same names as the duplicated files to see if they are in use. This option is required when you are using the same path (i.e., the standby and primary datafiles and logs have identical filenames).
- Do Recover - Select this option to recover the standby database after it has been created.
Click the Recover tab, then select the appropriate recover option.
Click the Redirect tab, then choose one of the following and click OK:
- To redirect all tablespaces to the same location, select the Redirect All Table Spaces to: checkbox then type in or Browse to the new path.
- To redirect tablespaces/datafiles to different locations, select the Redirect checkbox then click the desired objects in the Object column to highlight them, and either type in or Browse to the new path. Click Apply. Repeat this process until all tablespaces/datafiles have been redirected.
Select any other applicable options in the Oracle Duplicate Options dialog box, then click OK.
Begin or schedule the restore. Once the job begins, if you see a pop-up message about the database state, ensure that the standby database is in NOMOUNT mode then click Yes to continue.
Verify that the restore completed successfully and that the database is restored to the destination host. If you selected the Recover option verify that the database is consistent.