RE: RMAN-20242: specification does not match any archive log in the recovery catalog

Admin — Thu, 10 Jun 2010 13:14:23 GMT

RMAN-20242: specification does not match any archivelog in the recovery catalog

There is a solution in metalink for this: (Also check our other posts)

PURPOSE
-------

The purpose of this article is to resolve RMAN-20242 when trying to backup archived log files.

SCOPE & APPLICATION
-------------------

RMAN 'archivelog like' method is very useful when trying to backup archived log
on oracle parallel server and oracle parallel failsafe where archived logs exist
on all nodes local disks.

Resolving RMAN-20242: specification does not match any archivelog in the recovery catalog
-----------------------------------------------------------------------------------------

Trying to run the following RMAN script result with RMAN-20242.

RMAN> run {
2> allocate channel c1 type disk;
3> backup
4> archivelog like 'E:\oracle\oradata\prod\archive%';
5> }

RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: c1
RMAN-08500: channel c1: sid=17 devtype=DISK

RMAN-03022: compiling command: backup
RMAN-03026: error recovery releasing channel resources
RMAN-08031: released channel: c1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure during compilation of command
RMAN-03013: command type: backup
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20242: specificati
on does not match any archivelog in the recovery catalog

To resolve the above error, query v$archived_log to find out the archived log
details and note the format of the name column.

SQL> select * from v$archived_log;

RECID STAMP
---------- ----------
NAME
--------------------------------------------------------------------------------
THREAD# SEQUENCE# RESETLOGS_CHANGE# RESETLOGS FIRST_CHANGE# FIRST_TIM
---------- ---------- ----------------- --------- ------------- ---------
NEXT_CHANGE# NEXT_TIME BLOCKS BLOCK_SIZE CREA REGI STA ARC DEL COMPLETIO
------------ --------- ---------- ---------- ---- ---- --- --- --- ---------
1 419970034
E:\ORACLE\ORADATA\PROD\ARCHIVE\PRODT001S01524.ARC
1 1524 1 21-JAN-01 599954 25-JAN-01
600067 25-JAN-01 103 512 FGRD FGRD NO YES YES 25-JAN-01

Notice the name is in upper case - 'E:\ORACLE\ORADATA\PROD\ARCHIVE\PRODT001S01524.ARC'. Modify
the script and run again.

RMAN> run {
2> allocate channel c1 type disk;
3> backup
4> archivelog like 'E:\ORACLE\ORADATA\PROD\ARCHIVE\PROD%'
5> delete input;
6> release channel c1;
7> }

RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: c1
RMAN-08500: channel c1: sid=17 devtype=DISK

RMAN-03022: compiling command: backup
RMAN-03023: executing command: backup
RMAN-08009: channel c1: starting archivelog backupset
RMAN-08502: set_count=36 set_stamp=420311754 creation_time=29-JAN-01
RMAN-08014: channel c1: specifying archivelog(s) in backup set
RMAN-08504: input archivelog thread=1 sequence=1538 recid=15 stamp=420196579
RMAN-08504: input archivelog thread=1 sequence=1539 recid=16 stamp=420239024
RMAN-08504: input archivelog thread=1 sequence=1540 recid=17 stamp=420310708
RMAN-08504: input archivelog thread=1 sequence=1541 recid=18 stamp=420310800
RMAN-08504: input archivelog thread=1 sequence=1542 recid=19 stamp=420310879
RMAN-08013: channel c1: piece 1 created
RMAN-08503: piece handle=E:\ORACLE\ORA817\DATABASE\14CGQSMA_1_1 comment=NONE
RMAN-08525: backup set complete, elapsed time: 00:00:02
RMAN-08071: channel c1: deleting archivelog(s)
RMAN-08514: archivelog filename=E:\ORACLE\ORADATA\PROD\ARCHIVE\PRODT001S01538.AR
C recid=15 stamp=420196579
RMAN-08514: archivelog filename=E:\ORACLE\ORADATA\PROD\ARCHIVE\PRODT001S01539.AR
C recid=16 stamp=420239024
RMAN-08514: archivelog filename=E:\ORACLE\ORADATA\PROD\ARCHIVE\PRODT001S01540.AR
C recid=17 stamp=420310708
RMAN-08514: archivelog filename=E:\ORACLE\ORADATA\PROD\ARCHIVE\PRODT001S01541.AR
C recid=18 stamp=420310800
RMAN-08514: archivelog filename=E:\ORACLE\ORADATA\PROD\ARCHIVE\PRODT001S01542.AR
C recid=19 stamp=420310879
RMAN-03023: executing command: partial resync
RMAN-08003: starting partial resync of recovery catalog
RMAN-08005: partial resync complete

RMAN-03022: compiling command: release
RMAN-03023: executing command: release
RMAN-08031: released channel: c1

RMAN>

RMAN-20242: specification does not match any archive log in the recovery catalog

Admin — Thu, 10 Jun 2010 13:13:18 GMT

Getting: RMAN-20242: specification does not match any archive log in the recovery catalog

RMAN> run
2> {
3> allocate channel c1 type disk;
4> backup archivelog all;
5> release channel c1;
6> }

RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: c1
RMAN-08500: channel c1: sid=16 devtype=DISK

RMAN-03022: compiling command: backup
RMAN-03026: error recovery releasing channel resources
RMAN-08031: released channel: c1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure during compilation of command
RMAN-03013: command type: backup
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20242: specification does not match any archivelog in the recovery catalog

RMAN>

There are archivelog files in the Destination.

FranklinFaces.com - Oracle & SQL Server Database Forums for all IT Professionals / Oracle Forum / RMAN - Error Codes / RMAN-20000-20999 / RMAN-20242: specification does not match any archive log in the recovery catalog / Latest Posts

RE: RMAN-20242: specification does not match any archive log in the recovery catalog

RMAN-20242: specification does not match any archive log in the recovery catalog