Databases Reference
In-Depth Information
changed backup piece unavailable
...
Changed 1 objects to UNAVAILABLE status
RMAN>
Use the change ... unavailable option when you know you don't want a particular backup or copy to be
restored yet but don't want to delete that backup or copy either. If you uncatalog the backup set, it'll have a status of
deleted in the repository. However, if you just use the change command to make the backup set unavailable, you can
always make that available again when you have more space on this disk and are able to move the backup set to its
original location.
How It Works
Once you mark a backup file unavailable, RMAN won't use that file in a restore or recover operation. Note that you
can't mark files in the flash recovery area as unavailable. Once you find copies of the unavailable, misplaced, or lost
backups and restore them, you can mark all the backups you had marked unavailable previously as available again by
using the keyword available as part of the change command, as shown here:
RMAN> change backupset 10 available;
using channel ORA_DISK_1
changed backup piece available
...
Changed 1 objects to AVAILABLE status
RMAN>
When you change the status of a file to available, RMAN searches for that file and makes sure it actually exists.
You can use the change option to modify the status of backups and copies from previous incarnations of a database.
You can use the change command in a Data Guard environment to update the status of backups. The command
itself doesn't check whether a file is accessible on the backup media but simply changes the status of that backup in
the repository to whatever you specify. For example, if you performed a backup using an NFS-mounted disk and that
disk subsequently becomes inaccessible, you can connect to either the primary database or the standby database
and issue the change command to set the status of the backup as unavailable. Later, once the disk becomes accessible
again, you can change its status back to available.
Changing the Status of Archival Backups
Problem
You have made an archival backup for long-term storage to comply with some business requirements. These
requirements have changed over time, and you now want to change the status of the archival backup.
Solution
Use the change command when you want to change the status of an archival backup pertaining to the long-term
retention of that backup. You can use the change command in two ways to alter the retention requirements of your
archival backups.
 
Search WWH ::




Custom Search