3 Replies Latest reply: Oct 7, 2013 5:27 AM by shipon_97 RSS

    Log apply shows 'NO' status in PRIMARY NODE !

    shipon_97

      Dear Friends ,

      I am using Oracle 10g(10.2.0.1.0) Dataguard in Redhat Ent Linux 5.4 Platform . Last few days ago I restart PRIMARY Database and I see that , in PRIMARY & STANDBY node, logs are applied correctly . But after one days of  restarting database I found that log apply shows 'NO'  status on the PRIMARY node .

       

      But in the STANDBY node it shows all logs are applied . I don't get any error in the PRIMARY as well as STANDBY  node's alert log while I make log switch from the PRIMARY End .


      I mention some output below :

       

       

      PRIMARY NODE :

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

      SQL> select sequence#, applied from v$archived_log order by sequence# desc;

       

      SEQUENCE# APP

      ---------- ---

            2552 YES

            2552 NO

            2551 YES

            2551 NO

            2550 YES

            2550 NO

            2549 NO

            2549 YES

            2548 YES

            2548 NO

            2547 NO

            2547 YES

            2546 NO

            2546 YES

       

      STANDBY NODE :

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

        select sequence#, applied from v$archived_log order by sequence# desc;SQL>

       

      SEQUENCE# APP

      ---------- ---

            2552 YES

            2551 YES

            2550 YES

            2549 YES

            2548 YES

            2547 YES

            2546 YES

            2545 YES

            2544 YES

            2543 YES

            2542 YES

            2541 YES

            2540 YES

       

      Here you see that every log is applied but primary doesn't ow this .

       

      PRIMAR NODE :

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

      SQL>

      select     ds.dest_id id,     ad.status,     ds.database_mode db_mode,     ad.archiver type,     ds.recovery_mode,     ds.protection_mode

      ,     ds.standby_logfile_count "SRLs",     ds.standby_logfile_active active,     ds.archived_seq#from     v$archive_dest_status     ds

      ,     v$archive_dest          adwhere     ds.dest_id = ad.dest_id and     ad.status != 'INACTIVE' order by     ds.dest_id;

       

       

              ID STATUS    DB_MODE         TYPE       RECOVERY_MODE           PROTECTION_MODE            SRLs     ACTIVE ARCHIVED_SEQ#

      ---------- --------- --------------- ---------- ----------------------- -------------------- ---------- ---------- -------------

               1 VALID     OPEN            ARCH       IDLE                    MAXIMUM PERFORMANCE           0     0           2552

               2 VALID     MOUNTED-STANDBY LGWR       MANAGED REAL TIME APPLY MAXIMUM PERFORMANCE          16     5           2551

       

      SQL> select error_code, message,timestamp from v$dataguard_status where dest_id=2 order by timestamp desc;

      no rows selected

      It shows no error on the above output .

       

      Can anybody please tell me why log applied  difference is occured on the PRIMARY Node .

        • 1. Re: Log apply shows 'NO' status in PRIMARY NODE !
          Anar Godjaev

          Hi

           

          it is normally,

           

          Can you please cheek this script in Standby:

           

          select timestamp, message from v$dataguard_Status;

          select name, value from v$dataguard_Stats;

           

          Please see result:

           

          NAME                      VALUE

          ------------------------- --------------------------------------------------

          transport lag                  +00 00:00:00

          apply lag                     +00 00:00:00

          apply finish time          +00 00:00:00.000

          estimated startup time    29

           

           

          Thank you

          • 2. Re: Log apply shows 'NO' status in PRIMARY NODE !
            shipon_97

            Thx Anar ,

             

            The output is below :

             

            SQL> select name, value from v$dataguard_Stats;

             

            NAME                             VALUE

            -------------------------------- ----------------------------------------------------------------

            apply finish time                +00 00:00:00.0

            apply lag                        +00 00:00:32

            estimated startup time           7

            standby has been open            N

            transport lag                    +00 00:00:14

             

            SQL > select timestamp, message from v$dataguard_Status;

             

            07-OCT-13 Primary database is in MAXIMUM PERFORMANCE mode

            07-OCT-13 RFS[2519]: Successfully opened standby log 21: '/u01/app/oracle/flash_recovery_area/PBLSTAN/onlinelog/redo21.log'

            07-OCT-13 Media Recovery Waiting for thread 1 sequence 29691 (in transit)

            07-OCT-13 Primary database is in MAXIMUM PERFORMANCE mode

            07-OCT-13 RFS[2519]: Successfully opened standby log 22: '/u01/app/oracle/flash_recovery_area/PBLSTAN/onlinelog/redo22.log'

            07-OCT-13 Media Recovery Waiting for thread 1 sequence 29692 (in transit)

            07-OCT-13 Primary database is in MAXIMUM PERFORMANCE mode

            07-OCT-13 RFS[2519]: Successfully opened standby log 21: '/u01/app/oracle/flash_recovery_area/PBLSTAN/onlinelog/redo21.log'

            07-OCT-13 Media Recovery Waiting for thread 1 sequence 29693 (in transit)

            07-OCT-13 Primary database is in MAXIMUM PERFORMANCE mode

            07-OCT-13 RFS[2519]: Successfully opened standby log 22: '/u01/app/oracle/flash_recovery_area/PBLSTAN/onlinelog/redo22.log'

            07-OCT-13 Media Recovery Waiting for thread 1 sequence 29694 (in transit)

             

            is it OK ?

            • 3. Re: Log apply shows 'NO' status in PRIMARY NODE !
              Anar Godjaev

              HI Shipon

               

              Yes it is ok. Don't worry.

               

              For example: My alert.log

               

              07-OCT-13          ARC1: Completed archiving thread 2 sequence 41159 (0-0)

              07-OCT-13          ARC0: Beginning to archive thread 1 sequence 43892 (742761523291-742765230652)

              07-OCT-13          ARC0: Completed archiving thread 1 sequence 43892 (0-0)

              07-OCT-13          Media Recovery Waiting for thread 2 sequence 41160 (in transit)

              07-OCT-13          Media Recovery Log +DATA/azkkdbdr/archivelog/2013_10_07/thread_1_seq_43892.6791.828174335

              07-OCT-13          Media Recovery Waiting for thread 1 sequence 43893 (in transit)

              07-OCT-13          ARC3: Beginning to archive thread 1 sequence 43893 (742765230652-742769726560)

              07-OCT-13          ARC3: Completed archiving thread 1 sequence 43893 (0-0)

              07-OCT-13          Media Recovery Waiting for thread 1 sequence 43894 (in transit)

              07-OCT-13          ARC1: Beginning to archive thread 2 sequence 41160 (742765230643-742769730839)

              07-OCT-13          ARC1: Completed archiving thread 2 sequence 41160 (0-0)

              07-OCT-13          Media Recovery Waiting for thread 2 sequence 41161 (in transit)

              07-OCT-13          ARC0: Beginning to archive thread 1 sequence 43894 (742769726560-742775355316)

              07-OCT-13          ARC0: Completed archiving thread 1 sequence 43894 (0-0)

              07-OCT-13          Media Recovery Log +DATA/azkkdbdr/archivelog/2013_10_07/thread_1_seq_43894.6788.828176017

              07-OCT-13          Media Recovery Waiting for thread 1 sequence 43895 (in transit)

              07-OCT-13          ARC3: Beginning to archive thread 2 sequence 41161 (742769730839-742775360402)

              07-OCT-13          ARC3: Completed archiving thread 2 sequence 41161 (0-0)

              07-OCT-13          Media Recovery Waiting for thread 2 sequence 41162 (in transit)

              07-OCT-13          ARC1: Beginning to archive thread 1 sequence 43895 (742775355316-742782783772)

              07-OCT-13          ARC1: Completed archiving thread 1 sequence 43895 (0-0)

              07-OCT-13          Media Recovery Log +DATA/azkkdbdr/archivelog/2013_10_07/thread_1_seq_43895.6786.828176915

              07-OCT-13          Media Recovery Waiting for thread 1 sequence 43896 (in transit)

               

               

              256 rows selected.

               

               

               

               

              NAME                      VALUE

              ------------------------- --------------------------------------------------

              transport lag             +00 00:00:00

              apply lag                 +00 00:00:00

              apply finish time         +00 00:00:00.000

              estimated startup time    29

               

              Note:  You  network speed slow maybe   apply lag      +00 00:00:32

               

              Thank you