Oracle in a Nutshell

Name

CHANGE

Synopsis

Oracle9i syntax:

CHANGE 
   { { BACKUP | COPY } [OF listObjList]
      [mntQualifer [mntQualifer]...} 
   | recordSpec 
      [DEVICE TYPE deviceSpecifier [, deviceSpecifier]...]
   }
   { AVAILABLE | UNAVAILABLE | UNCATALOG | keepOption } 
   [DEVICE TYPE deviceSpecifier [, deviceSpecifier]...];

Oracle8i syntax:

CHANGE 
   { ARCHIVELOG 
      { primary_key [, primary_key...] 
      | 'filename' [,'filename' ...] }
   | archivelogRecordSpecifier
   | BACKUPPIECE { 'media_handle' [,'media_handle' ...]
                  | primary_key [, primary_key ...]
                  | TAG [=] [']tag_name['] }
   | BACKUPSET primary_key [, primary_key ...]
   | { CONTROLFILECOPY | DATAFILECOPY }
     { primary_key [, primary_key ...] 
     | 'filename' [,'filename' ...]
     | TAG [=] [']tag_name['] [, [']tag_name ['] ... ] }
   | PROXY { 'media_handle' [,'media_handle' ...]
           | primary_key [, primary_key ...]
           | TAG [=] [']tag_name['] }
   } 
   { DELETE | AVAILABLE | UNAVAILABLE 
   | UNCATAOG | CROSSCHECK };

Enables you to perform maintenance on backup sets or their associated backup pieces. Such maintenance might include changing the status repository records for backup sets and backup pieces or deleting backup pieces from disk or tape media; the latter would also remove the associated records from the target database’s control files and from the optional recovery catalog

Keywords

AVAILABLE

Changes the status of backups or copies to AVAILABLE.

UNAVAILABLE

Changes the status of backups or copies to UNAVAILABLE. Backups marked as UNAVAILABLE are not used by RMAN. Therefore, a subsequent recovery operation ...