Oracle9i Recovery Manager Reference
Release 1 (9.0.1)

Part Number A90136-02
Go To Documentation Library
Home
Go To Product List
Book List
Go To Table Of Contents
Contents
Go To Index
Index

Master Index

Feedback

Go to previous page Go to beginning of chapter Go to next page

RMAN Commands , 12 of 60


CHANGE

Syntax


Text description of rcmsyn63.gif follows
Text description of the illustration rcmsyn63.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.

BACKUP 

Operates on the specified backups: backup sets, backup pieces, and proxy copies. If you do not specify an option for BACKUP, then CHANGE BACKUP operates on all backups recorded in the repository.

Note: Use the KEY column of the LIST output to obtain the primary key usable in the CHANGE command. 

 

OF listObjList 

Restricts the list of objects operated on to the object type specified in the listObjList clause. If you do not specify an object, then CHANGE defaults to all copies.

See Also: "listObjList" 

 

maintQualifier 

restricts the command based on the specified options.

See Also: "maintQualifier" 

COPY 

Operates on datafile copies, archived redo logs, and image copies of archived redo logs. If you do not specify an option for COPY, then CHANGE COPY operates on all copies recorded in the repository.  

 

OF listObjList 

restricts the list of objects operated on to the object type specified in the listObjList clause. If you do not specify an object, then CHANGE defaults to all copies.

See Also: "listObjList" 

 

maintQualifier 

restricts the command based on the specified options.

See Also: "maintQualifier" 

recordSpec 

Specifies the object whose availability status you are changing. See "recordSpec"

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. 

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 you can use the AVAILABLE option to reflect this change. 

UNCATALOG 

Removes references to a datafile copy or archived redo log (but not a backup piece or backup set) 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 uncataloged records can sometimes reappear in the catalog metadata. 

 

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. 

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.

Note: You can also specify KEEP in the backupSpec clause.

See Also: "keepOption" 

Examples

Updating a Backup Set to Status UNAVAILABLE: Example

This example changes the status of a backup set to UNAVAILABLE. You do not need to allocate a maintenance channel:

CHANGE BACKUPSET 100 UNAVAILABLE;

Uncataloging a Datafile Copy: Example

This example uncatalogs a datafile copy that was removed by an operating system utility:

% rm /dir1/df1_copy.f
% rman target / nocatalog
RMAN> CHANGE DATAFILECOPY '/dir1/df1_copy.f' UNCATALOG;

Changing the Retention Status of a Backup Set: Example

This example changes an ordinary backup into a long-term backup:

CHANGE BACKUPSET 231 KEEP FOREVER NOLOGS;

Go to previous page Go to beginning of chapter Go to next page
Oracle
Copyright © 1996-2001, Oracle Corporation.

All Rights Reserved.
Go To Documentation Library
Home
Go To Product List
Book List
Go To Table Of Contents
Contents
Go To Index
Index

Master Index

Feedback