RMAN Restore and Recovery - Oracle RMAN for Absolute Beginners - page 185

Step 9. Start Up the Database in Mount Mode
You should now be able to start up your database in mount mode:

RMAN> alter database mount;

At this point, your control files exist and have been opened, but none of the data files or online redo logs exist yet.

Step 10. Make the Control File Aware of the Location of the RMAN Backups
First, use the CROSSCHECK command to let the control file know that none of the backups or archive redo logs are in the
same location that they were in on the original server:

RMAN> crosscheck backup; # Crosscheck backups
RMAN> crosscheck copy; # Crosscheck image copies and archive logs

Then, use the CATALOG command to make the control file aware of the location and names of the backup pieces
that were copied to the destination server.

■ don't confuse the CATALOG command with the recovery catalog schema. the CATALOG command adds rMaN
metadata to the control file, whereas the recovery catalog schema is a user, generally created in a separate database,
that can be used to store rMaN metadata.

Note

In this example any RMAN files that are in the /ora01/rman/DEVDB directory will be cataloged in the control file:

RMAN> catalog start with '/ora01/rman/DEVDB';

Here is some sample output:

List of Files Unknown to the Database
=====================================
File Name: /ora01/rman/DEVDB/rman1_bqnvb2k5_1_1.bk
File Name: /ora01/rman/DEVDB/rman1_bonvb2js_1_1.bk
File Name: /ora01/rman/DEVDB/rman_ctl_c-3423216220-20130113-06.bk
File Name: /ora01/rman/DEVDB/rman1_bsnvb2p3_1_1.bk

Do you really want to catalog the above files (enter YES or NO)?

Now, type YES (if everything looks okay). You should then be able to use the RMAN LIST BACKUP command to
view the newly cataloged backup pieces:

RMAN> list backup;