Oracle Database migration to a remote Data Protector cell--Best practices

Recovery Catalog export

As for the Oracle Control File, Data Protector performs a backup of the Oracle Recovery Catalog at

the end of every Oracle backup session by default. This functionality can be disabled in the

Application Specific Options window, inside the Oracle backup specification.

First, the Oracle Recovery Catalog is exported to the file system and then, by means of a file system

backup, copied to the target device.

For restore purposes, the DP GUI and the CLI can be used. Both are documented in the Oracle

Integration Manual.

See Appendix D for more information on how to import the Recovery Catalog on the target system.

Restore Scenarios

Procedure Details

This section gives a step-by-step description of performing a restore and recovery of the Oracle

database on the target system. We cover the procedure for three different scenarios:

1. Control File autobackup and Recovery Catalog are used

2. Recovery Catalog is used but no Control File autobackup

3. No Control File autobackup nor Recovery Catalog are used

We assume the following for all three scenarios:

• A full online backup (plus archive logs) from the DB10g database on ita022 was taken successfully

• The original tapes/media have already been imported into the target cell manager

• The source data center is not available

• The target system preparation has already been performed

• The RCVCAT recovery catalog, if used, has been imported in the target environment (RCAT)

• The DBID of the database to be restored is known. (Refer to the Appendix for more information.)

• The ORACLE_SID is set in the user environment

• Within the RMAN configuration, SBT_TAPE is set to default TYPE.

In the following scripts, no channel allocation command is used. The reason is, in the default RMAN

configuration, SBT_TAPE is configured as the default type, thus, RMAN will allocate, if needed, TAPE

channels in the scripts.

To activate it, (default TYPE is DISK), connect in RMAN to your target database (and Recovery

Catalog if used) and issue the command:

RMAN> CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';

There is no need to set any OB2BARTYPE, OB2APPNAME, nor OB2BARLIST variables to be able to

perform the restore.

For all cases, we will follow the next restore and recovery sequence:

1. Connect to the Recovery Catalog using RMAN

2. Set the DBID

3. Startup nomount: as no SPFILE is available at this time, Oracle will startup the

instance with a default SPFILE

4. Restore the SPFILE from the backup.