plus archivelog' and RMAN optimization

1 min read

May 17, 2007 12:00:00 AM

I just want to raise a warning flag for DBAs using RMAN and flash recovery area in Oracle 10g. An RMAN script is usually something like:

backup database plus archivelog

However, the behavior of plus archivelog depends on whether optimization is enabled or disabled in RMAN. The RMAN reference document says that when the plus archivelog command is part of a backup script, RMAN:

runs an ALTER SYSTEM ARCHIVE LOG CURRENT statement.
runs the BACKUP ARCHIVELOG ALL command. Note that if backup optimization is enabled, RMAN only backs up logs that have not yet been backed up.
backs up the files specified in the BACKUP command.
runs an ALTER SYSTEM ARCHIVE LOG CURRENT statement.
backs up any remaining archived redo logs

As the result, if backup optimization is off (which it is by default in RMAN), plus archivelogs will backup all archivelogs. If the archivelog destination is a flash recovery area, your database may keep very old archivelogs (assuming space is not an issue). Thus, the backup size will gradually grow and fill up the flash recovery area, since each backup includes all archivelogs in the flash recovery area. The lesson is, to avoid backing up archivelogs that have already been backed up when using plus archivelog in a backup script, make sure you enable RMAN optimization. Hope this helps.

On this page

Ready to unlock value from your data?

With Pythian, you can accomplish your data transformation goals and more.

Speak with Pythian consultants now →

What We Do

plus archivelog' and RMAN optimization

Share this

Share this

More resources

RMAN - Validating Archivelog Backup

Enabling achivelog mode in 12c RAC database

RMAN Recipes: How to Switch Oracle Logs Automatically

Ready to unlock value from your data?