Skip Headers
Oracle® Database Backup and Recovery Reference
10g Release 2 (10.2)

Part Number B14194-03
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

CHANGE

Syntax

change::=

Description of change.gif follows
Description of the illustration change.gif

maintSpec::=

Description of maintspec.gif follows
Description of the illustration maintspec.gif

Purpose

To make the following changes:

Restrictions and Usage Notes

Keywords and Parameters

To obtain the primary keys of the records whose status you want to change, run a LIST command or query the recovery catalog views.

Syntax Element Description
maintSpec
Specifies which files you want to CHANGE. Refer to "maintSpec" for descriptions of the options in this caluse.
AVAILABLE Changes the status of a backup or copy to AVAILABLE in the repository. View the status in the LIST output or recovery catalog views.
keepOption
Changes the exemption status of a backup or copy in relation to the configured retention policy. For example, specify CHANGE ... NOKEEP to make a backup that is currently exempt from the retention policy eligible for OBSOLETE status.

You can also specify KEEP in the backupSpec clause.

Note: You cannot use keepOption with flash recovery area files.

See Also: "keepOption"

UNAVAILABLE Changes the status of a backup or copy to UNAVAILABLE in the repository. View the status in the LIST output or recovery catalog views. This option is provided for cases when the file cannot be found or has migrated offsite. RMAN does not use a file that is marked UNAVAILABLE in a RESTORE or RECOVER command. If the file is later found or returns to the main site, then use the AVAILABLE option to update its status.
UNCATALOG Removes references to a datafile copy, backup piece, or archived redo log from the recovery catalog, and updates records in the target control file to status DELETED. The CHANGE ... UNCATALOG command does not touch physical backups and copies. Use this command to notify RMAN when a file is deleted by some means other than a DELETE command.

Caution: If you resynchronize from a backup control file, or upgrade the recovery catalog, then records previously removed from the RMAN repository with CHANGE... UNCATALOG may reappear in the recovery catalog.

DEVICE TYPE deviceSpecifier Executes the CHANGE for the specified device type only (see "deviceSpecifier"). This option is valid only if you have configured automatic channels and have not manually allocated channels. For example, if you run CHANGE UNCATALOG...DEVICE TYPE DISK, then RMAN only uncatalogs files on disk.

Examples

Updating Backups to Status UNAVAILABLE: Example This example changes the status of backup set 100 as well as all backups of server parameter files created more than a day ago to UNAVAILABLE:

CHANGE BACKUPSET 100 UNAVAILABLE;
CHANGE BACKUP OF SPFILE COMPLETED BEFORE 'SYSDATE-1' UNAVAILABLE;

You do not need to allocate a maintenance channel.

Uncataloging and Cataloging Archived Logs: Example In this example, you move all archived logs to a new directory, uncatalog them, and then recatalog them in the new location:

HOST 'mv $ORACLE_HOME/oradata/trgt/arch/* /fs2/arch';
CHANGE ARCHIVELOG ALL UNCATALOG;
CATALOG START WITH '/fs2/arch';

Changing the Retention Status of a Backupset: Example This example, which requires a recovery catalog, changes an ordinary backup into a long-term backup:

CHANGE BACKUP TAG 'consistent_db_bkup'
  KEEP FOREVER NOLOGS;