Recovery Manager Command Syntax, 7 of 50

catalog

Syntax

Purpose

Use the catalog command to:

Add information about an operating system datafile copy, archived redo log, or control file copy to the recovery catalog and control file.
Catalog a datafile copy as a level 0 backup, which enables you to use it as part of an incremental backup strategy.
Record the existence of backups of version 8 databases created before RMAN was installed.
Record the existence of Oracle7 backups of read-only or offline normal files made before migrating to Oracle8 or Oracle8i.

See Also:
"Maintaining the RMAN Repository".

Requirements

Execute the catalog command only at the RMAN prompt.
Operate RMAN with a recovery catalog.
For an operating system backup to be cataloged, it must be:
- Accessible on disk.
- A complete image copy of a single file.
- A consistent or inconsistent whole database, tablespace, datafile, control file, or archived redo log backup. If inconsistent, it must have been created using the BEGIN BACKUP/END BACKUP statements. If a control file backup, it should have been made using the ALTER DATABASE BACKUP CONTROLFILE statement.
RMAN treats all such operating system backups as datafile copies.

You cannot use catalog to perform the following operations:

Catalog archived redo logs and control file copies that were created in Oracle7 unless the file belongs to a tablespace that was offline normal or read-only when you migrated the database to Oracle version 8.0 or later.
Re-catalog backup pieces or backup sets.

Keywords and Parameters

controlfilecopy 'filename'

specifies the filename of a control file copy to be added to or updated in the recovery catalog and control file.

datafilecopy 'filename'

specifies the filename of a datafile copy to be added to or updated in the recovery catalog and control file.

archivelog 'filename'

specifies the filename of an archivelog copy to be added to or updated in the recovery catalog and control file.

tag tag_name

specifies the tag of the input file, for example, Sunday_PM_Backup.

level integer

indicates that the file copy should be recorded as an incremental backup at the specified level, typically level 0. You can perform incremental backups using a datafile copy as the base level 0 backup.

Examples

Cataloging an Archived Redo Log

This statement catalogs the archived redo logs log1, log2, and log3:

catalog archivelog 'log1', 'log2', 'log3';

Cataloging a File Copy as an Incremental Backup

The following example catalogs datafile copy tbs_2.c as an incremental level 0 backup:

catalog datafile '/oracle/copy/tbs_2.c' level 0;

Cataloging an Operating System Copy

The following makes an operating system copy of a datafile using the RMAN host command and then catalogs the copy (sample output included):

host 'cp $ORACLE_HOME/dbs/sales.f $ORACLE_HOME/dbs/sales.bak';
catalog datafilecopy '$ORACLE_HOME/dbs/sales.bak';

RMAN-03022: compiling command: catalog
RMAN-03023: executing command: catalog
RMAN-08050: cataloged datafile copy
RMAN-08513: datafile copy filename=/oracle/dbs/sales.bak recid=121 stamp=342972501
RMAN-03023: executing command: partial resync
RMAN-08003: starting partial resync of recovery catalog
RMAN-08005: partial resync complete

controlfilecopy 'filename'	specifies the filename of a control file copy to be added to or updated in the recovery catalog and control file.
datafilecopy 'filename'	specifies the filename of a datafile copy to be added to or updated in the recovery catalog and control file.
archivelog 'filename'	specifies the filename of an archivelog copy to be added to or updated in the recovery catalog and control file.
tag tag_name	specifies the tag of the input file, for example, Sunday_PM_Backup.
level integer	indicates that the file copy should be recorded as an incremental backup at the specified level, typically level 0. You can perform incremental backups using a datafile copy as the base level 0 backup.