BACKUP RECOVERY AREA

Problem: RMAN BACKUP RECOVERY AREA does not backup files present in FRA & exit with following messages

specification does not match any archive log in the recovery catalog
specification does not match any datafile copy in the repository
specification does not match any backupset in the repository
backup cancelled because all files were skipped

But files are physically present in the FRA

SQL> show parameter recovery

NAME TYPE VALUE
———————————— ———– ——————————
db_recovery_file_dest string +FLASH
db_recovery_file_dest_size big integer 50G

SQL> show parameter archive

NAME TYPE VALUE
——————– ———– ——————————
log_archive_dest_1 string LOCATION=+FLASH/TESTDB/ OPTIONAL REOPEN=300

Physical backup existance can be checked by using ASMCMD

ASMCMD [+FLASH/TESTDB/backupset/2008_02_06] > ls -al

Type Redund Striped Time Sys Name

BACKUPSET UNPROT COARSE FEB 06 00:00:00 Y +FLASH/7vidn06f_1_1 => annnf0_FULL_BACKUP_032707115955_0.302.618365137

BACKUPSET UNPROT COARSE FEB 07 00:00:00 Y +FLASH/7uidn06f_1_1 => annnf0_FULL_BACKUP_032707115955_0.442.618365137

Solution:

This problem is caused by putting the archivelogs and backupset into the Flash recovery area by explicitly specifying the diskgroup in log_archive_dest_n. This setting will create them in the FRA location but they are not considered to be part of the FRA in space management algorithm.

This can be confirmed by selecting the values from v$backup_piece & v$archived_log

SQL> select thread#, sequence#,is_recovery_dest_file, name from v$archived_log
/
SQL> select IS_RECOVERY_DEST_FILE from v$backup_piece
/

To resolve this problem

SQL> ALTER SYSTEM SET LOG_ARCHIVE_DEST_1= ‘LOCATION=USE_DB_RECOVERY_FILE_DEST’
/

Then do a small test by

SQL> ALTER SYSTEM ARCHIVELOG CURRENT
/

IS_RECOVERY_DEST_FILE for this archivelogs should be shown as YES

Now test the backup

$ rman target / catalog=rman_catalog

RMAN> run
2> {
3> ALLOCATE CHANNEL ch1 TYPE ‘SBT_TAPE';
4> BACKUP RECOVERY AREA;
5> RELEASE CHANNEL ch1;
6> }

About these ads
This entry was posted in Oracle Database Backup, Oracle Recovery Manager and tagged . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s