DBAsupport.com Forums - Powered by vBulletin
Page 1 of 2 12 LastLast
Results 1 to 10 of 17

Thread: Archive log RMAN doubt

  1. #1
    Join Date
    Aug 2002
    Posts
    176

    Archive log RMAN doubt

    I have posted a previous doubt on Listing similarly when i try to backup the archive logs it tells me


    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.

    Can anyone Advice pls.
    Success Consists of Getting Up Just One More Time Than You've Fallen Down
    Be Blessed

  2. #2
    Join Date
    Mar 2000
    Location
    Chennai.Tamilnadu.India.
    Posts
    658

    Solution

    Hi,

    There is a Solution for your Problem in the Metalink....
    Please read the same...If still you have problem please log your concern.....

    Even though you have are not mentioned "Like" command in Lower case as mentioned in the Metalink case...Try that way and Let Us know.

    =============================================

    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>

    ==============================
    Cheers

    Padmam
    Last edited by padmam; 03-24-2003 at 03:31 PM.
    Attitude:Attack every problem with enthusiasam ...as if your survival depends upon it

  3. #3
    Join Date
    Jun 2001
    Location
    Helsinki. Finland
    Posts
    3,938

    Re: Archive log RMAN doubt

    Originally posted by Rohit
    I have posted a previous doubt on Listing similarly when i try to backup the archive logs it tells me


    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.

    Can anyone Advice pls.
    Run first:

    change archivelog all crosscheck;
    Oracle Certified Master
    Oracle Certified Professional 6i,8i,9i,10g,11g,12c
    email: ocp_9i@yahoo.com

  4. #4
    Join Date
    Aug 2002
    Posts
    176
    Thansk You so much Julian , but that command also displays the same error.


    RMAN> run
    2> {
    3> allocate channel c1 type disk;
    4> change archivelog all crosscheck;
    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=14 devtype=DISK

    RMAN-03022: compiling command: change
    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: change
    RMAN-06004: ORACLE error from recovery catalog database: RMAN-20242: specification does not match any archivelog in the recovery catalog

    RMAN>

    Can you pls Advice
    Thanks
    Success Consists of Getting Up Just One More Time Than You've Fallen Down
    Be Blessed

  5. #5
    Join Date
    Sep 2000
    Location
    Chennai, India
    Posts
    865

    Re: Archive log RMAN doubt

    Originally posted by Rohit


    RMAN> run
    2> {
    3> allocate channel c1 type disk;
    4> backup archivelog all;
    5> release channel c1;
    6> }
    Replace the above with the following ...

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


    or better still try the following code (with trivial modifications for your specific situation)

    Code:
    RMAN> run {
    2> allocate channel d1 type disk;
    3> backup
    4> format '/backups/log_t%t_s%s_p%p'
    5> (archivelog all);
    6> release channel d1;
    7> }
    BTW, what is the version of oracle that you are running?

    HTH.

  6. #6
    Join Date
    Jun 2001
    Location
    Helsinki. Finland
    Posts
    3,938
    Originally posted by Rohit
    Thansk You so much Julian , but that command also displays the same error.


    RMAN> run
    2> {
    3> allocate channel c1 type disk;
    4> change archivelog all crosscheck;
    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=14 devtype=DISK

    RMAN-03022: compiling command: change
    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: change
    RMAN-06004: ORACLE error from recovery catalog database: RMAN-20242: specification does not match any archivelog in the recovery catalog

    RMAN>

    Can you pls Advice
    Thanks
    The command change archivelog all crosscheck; gives you the same error right? Which version of Oracle is it?
    Oracle Certified Master
    Oracle Certified Professional 6i,8i,9i,10g,11g,12c
    email: ocp_9i@yahoo.com

  7. #7
    Join Date
    Aug 2002
    Posts
    176
    we are using oracle 8.1.6 on windows 2000
    Success Consists of Getting Up Just One More Time Than You've Fallen Down
    Be Blessed

  8. #8
    Join Date
    Nov 2002
    Location
    New Delhi, INDIA
    Posts
    1,796
    8.1.6 for both catalog as well as the database ??
    Amar
    "There is a difference between knowing the path and walking the path."

    Amar's Blog  Get Firefox!

  9. #9
    Join Date
    Nov 2000
    Location
    greenwich.ct.us
    Posts
    9,092
    Assuming everything is setup correctly, I used to get this error when there was nothing to backup in the log_archive_dest. I solved this problem by forcing a log switch before I started my archivelog backup.
    Jeff Hunter

  10. #10
    Join Date
    Aug 2002
    Posts
    176
    Yea Both Catalog and Target are 8.1.6 and there are archive logs currently in the destination which were created after the registartion of the database with the catalog.

    Thanks
    Success Consists of Getting Up Just One More Time Than You've Fallen Down
    Be Blessed

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


Click Here to Expand Forum to Full Width