Databases Reference
In-Depth Information
How It Works
If you're encountering disk space issues, the error message will vary depending on whether you're using a FRA and
which operating system you're using. You can resolve disk space issues in a number of ways. If you're in an emergency
situation, the quickest way to resolve the issue may be to change the location of the backup directory. If you're looking
for a long-term solution, you'll probably want to consider adding more disk space to the backup location and/or
changing your RMAN retention policy.
If you're using a FRA, then you can dynamically issue an
alter system
command to change the location and size
of the backup directory. If you're not using a FRA, you can use the
configure
command to change the location of the
backups (see Recipe 5-16 for an example of how to do this).
If there are old archived redo log files, consider backing them up and then deleting them from disk. You can use
commands such as
report obsolete
to show which RMAN backup files and archived redo log files are no longer
required as per the retention policy. If there are obsolete files, then you can use the
delete obsolete
command to
have RMAN remove them from the backup media.
■
Consider using compressed backups to decrease the amount of disk space consumed. rMan's basic default
compression algorithm produces a significant reduction in the size of the backups.
Tip
Dealing with the RMAN-06059 Error
Problem
You've just switched from user-managed backups to using RMAN backups and are attempting to run the following
command:
RMAN> backup database plus archivelog;
Your backup process doesn't get very far when RMAN throws this error:
RMAN-03002: failure of backup plus archivelog command at...
RMAN-06059: expected archived log not found, loss of archived log
compromises recoverability
Your boss happens to be in your office when you are attempting to back up the database and lets you know that
“compromised recoverability” will translate into “compromised job security.”
Solution
The problem is that the control file has information regarding archive redo logs that are no longer on disk (or have
been manually moved). You must update RMAN's repository to reflect that archived redo log files have been either
physically deleted or moved to another location on disk. Use the
crosscheck
command to inform RMAN that archived
redo log files have been physically removed from disk, as shown here:
RMAN> crosscheck archivelog all;
Now run your backup command again; this time it should succeed:
RMAN> backup database plus archivelog;
