2 Replies Latest reply: Feb 26, 2014 12:46 AM by user591655 RSS

The archive log cannot be applied on 11.2.0.3 standby.

liaison1 Newbie
Currently Being Moderated

The archive log cannot apply to the standby DB

Problem Description
---------------------------------------------------
We created a DG standby database on 11.2.0.3. Both primary and standby DB are using ASM. The archive apply looks fine to begin with. However, archive log apply was stopped last night. When I try to manually apply got the error:

SQL> recover standby database;
ORA-00279: change 12258525927820 generated at 02/24/2014 01:04:27 needed for
thread 1
ORA-00289: suggestion : +DG2
ORA-00280: change 12258525927820 for thread 1 is in sequence #18755
 
ORA-00308: cannot open archived log '+DG2'
ORA-17503: ksfdopn:2 Failed to open file +DG2
ORA-15045: ASM file name '+DG2' is not in reference form

 

Here is the list of the archive log being sent to the lsildb20p.

 

ARCHIVELOG  UNPROT  COARSE   FEB 25 10:00:00  Y    thread_1_seq_18762.998.840451699

ARCHIVELOG  UNPROT  COARSE   FEB 25 10:00:00  Y    thread_1_seq_18763.999.840451701

ARCHIVELOG  UNPROT  COARSE   FEB 25 10:00:00  Y    thread_1_seq_18764.1000.840451703

ARCHIVELOG  UNPROT  COARSE   FEB 25 10:00:00  Y    thread_1_seq_18765.1001.840451719

ARCHIVELOG  UNPROT  COARSE   FEB 25 10:00:00  Y    thread_1_seq_18766.1002.840451721

ARCHIVELOG  UNPROT  COARSE   FEB 25 10:00:00  Y    thread_1_seq_18767.1003.840451729

ARCHIVELOG  UNPROT  COARSE   FEB 25 10:00:00  Y    thread_1_seq_18768.1004.840451741

ARCHIVELOG  UNPROT  COARSE   FEB 25 10:00:00  Y    thread_1_seq_18769.1005.840451743

ARCHIVELOG  UNPROT  COARSE   FEB 25 10:00:00  Y    thread_1_seq_18770.1006.840451757

ARCHIVELOG  UNPROT  COARSE   FEB 25 10:00:00  Y    thread_1_seq_18771.1007.840451761

ARCHIVELOG  UNPROT  COARSE   FEB 25 10:00:00  Y    thread_1_seq_18772.1008.840451773

ARCHIVELOG  UNPROT  COARSE   FEB 25 10:00:00  Y    thread_1_seq_18773.1009.840451779

ARCHIVELOG  UNPROT  COARSE   FEB 25 10:00:00  Y    thread_1_seq_18774.1010.840451785

ARCHIVELOG  UNPROT  COARSE   FEB 25 10:00:00  Y    thread_1_seq_18775.1011.840451795

ARCHIVELOG  UNPROT  COARSE   FEB 25 10:00:00  Y    thread_1_seq_18776.1012.840451801

ARCHIVELOG  UNPROT  COARSE   FEB 25 10:00:00  Y    thread_1_seq_18777.1013.840451805

ARCHIVELOG  UNPROT  COARSE   FEB 25 10:00:00  Y    thread_1_seq_18778.1014.840451819

ARCHIVELOG  UNPROT  COARSE   FEB 25 10:00:00  Y    thread_1_seq_18779.1015.840451821

ARCHIVELOG  UNPROT  COARSE   FEB 25 10:00:00  Y    thread_1_seq_18780.1016.840451833

ARCHIVELOG  UNPROT  COARSE   FEB 25 10:00:00  Y    thread_1_seq_18781.1017.840451841

ARCHIVELOG  UNPROT  COARSE   FEB 25 10:00:00  Y    thread_1_seq_18782.1018.840451845

ARCHIVELOG  UNPROT  COARSE   FEB 25 10:00:00  Y    thread_1_seq_18783.1019.840451857

ARCHIVELOG  UNPROT  COARSE   FEB 25 10:00:00  Y    thread_1_seq_18784.1020.840451861

ARCHIVELOG  UNPROT  COARSE   FEB 25 10:00:00  Y    thread_1_seq_18785.1021.840451875

ARCHIVELOG UNPROT  COARSE   FEB 25 10:00:00  Y    thread_1_seq_18786.993.840451681     Archive log apply stopped there.  the %t_%s_%r format is defined in archive format for both primary and standby. 

ARCHIVELOG UNPROT  COARSE   FEB 25 10:00:00  Y thread_1_seq_18787.994.840451681        <=  why number is not in sequence 993,994,995,.... after 1021.   Should this is the problem likely?

ARCHIVELOG UNPROT  COARSE   FEB 25 10:00:00  Y thread_1_seq_18788.995.840451683

ARCHIVELOG UNPROT  COARSE   FEB 25 10:00:00  Y thread_1_seq_18789.997.840451687

ARCHIVELOG  UNPROT  COARSE   FEB 25 10:00:00  Y    thread_1_seq_18790.1022.840451877

ARCHIVELOG  UNPROT  COARSE   FEB 25 10:00:00  Y    thread_1_seq_18791.1023.840451883

ARCHIVELOG  UNPROT  COARSE   FEB 25 10:00:00  Y    thread_1_seq_18792.1024.840451885

ARCHIVELOG  UNPROT  COARSE   FEB 25 10:00:00  Y    thread_1_seq_18793.1025.840451891

ARCHIVELOG  UNPROT  COARSE   FEB 25 10:00:00  Y    thread_1_seq_18794.1026.840451901

ARCHIVELOG  UNPROT  COARSE   FEB 25 10:00:00  Y    thread_1_seq_18795.1027.840451909

ARCHIVELOG  UNPROT  COARSE   FEB 25 10:00:00  Y    thread_1_seq_18796.1028.840451917

ARCHIVELOG  UNPROT  COARSE   FEB 25 10:00:00  Y    thread_1_seq_18797.1029.840451925

ARCHIVELOG  UNPROT  COARSE   FEB 25 10:00:00  Y    thread_1_seq_18798.1030.840451935

ARCHIVELOG  UNPROT  COARSE   FEB 25 10:00:00  Y    thread_1_seq_18799.1031.840451941

ARCHIVELOG  UNPROT  COARSE   FEB 25 10:00:00  Y    thread_1_seq_18800.1032.840451951

ARCHIVELOG  UNPROT  COARSE   FEB 25 10:00:00  Y    thread_1_seq_18801.1033.840451957

ARCHIVELOG  UNPROT  COARSE   FEB 25 10:00:00  Y    thread_1_seq_18802.1034.840451961

ARCHIVELOG  UNPROT  COARSE   FEB 25 10:00:00  Y    thread_1_seq_18803.1035.840451967

ARCHIVELOG  UNPROT  COARSE   FEB 25 10:00:00  Y    thread_1_seq_18804.1036.840451975

ARCHIVELOG  UNPROT  COARSE   FEB 25 11:00:00  Y    thread_1_seq_18805.996.840451685

ARCHIVELOG  UNPROT  COARSE   FEB 25 12:00:00  Y    thread_1_seq_18806.1039.840455589

ARCHIVELOG  UNPROT  COARSE   FEB 25 13:00:00  Y    thread_1_seq_18807.1040.840458609

ARCHIVELOG  UNPROT  COARSE   FEB 25 14:00:00  Y    thread_1_seq_18808.1041.840460523

 

thanks for help!

  • 1. Re: The archive log cannot be applied on 11.2.0.3 standby.
    CKPT Guru
    Currently Being Moderated

    SQL> recover standby database;

    ORA-00279: change 12258525927820 generated at 02/24/2014 01:04:27 needed for

    thread 1

    ORA-00289: suggestion : +DG2

    ORA-00280: change 12258525927820 for thread 1 is in sequence #18755

     

    Standby requires the sequence 18755, The sequence either not sent from primary or its missing even though it already sent.

    If you have in primary then copy manually and try to fix them (or) restore archive from backups if available.

    In case archive is not available in both primary and standby databases, then certainly you have to use Incremental backups to recover and make sync between them.

     

    http://www.oracle-ckpt.com/rman-incremental-backups-to-roll-forward-a-physical-standby-database-2/

     

    ARCHIVELOG UNPROT  COARSE   FEB 25 10:00:00  Y    thread_1_seq_18786.993.840451681     Archive log apply stopped there.  the %t_%s_%r format is defined in archive format for both primary and standby. 

    ARCHIVELOG UNPROT  COARSE   FEB 25 10:00:00  Y thread_1_seq_18787.994.840451681        <=  why number is not in sequence 993,994,995,.... after 1021.   Should this is the problem likely?

    ARCHIVELOG UNPROT  COARSE   FEB 25 10:00:00  Y thread_1_seq_18788.995.840451683

    ARCHIVELOG UNPROT  COARSE   FEB 25 10:00:00  Y thread_1_seq_18789.997.840451687


    Am really not worried about the archive log format on primary and standby database. The number is managed with OMF and your attention is not required, You have to ensure of the thread and sequence. If you dont want to use OMF then you can disable it either. But i dont think it is an issue either. 

  • 2. Re: The archive log cannot be applied on 11.2.0.3 standby.
    user591655 Journeyer
    Currently Being Moderated

    Hi,

     

    make sure diskgroup is accessible.

    You should try your recovery using RMAN.  If you do it in sqlplus then it's expected
    that you have the logs on disk to do the recovery.

    From RMAN make sure the logs are catalog.  Execute the following command.

    RMAN> CATALOG START WITH '+DG2'; # catalog all files from an ASM disk group

    -- Now from sqlplus:

    SQL> recover standby database;

    Specify AUTO

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points