1 2 3 Previous Next 30 Replies Latest reply: Dec 2, 2013 8:05 PM by petra-K Go to original post RSS
      • 15. Re: DG Standby db not giving normal report?
        Karan Kukreja

        Issue this command :

         

        select process,status,sequence# from v$managed_standby;

         

        this will tell you which log it is applying. The MRP has the job of applying logs only and thats what it is doing. The sequence will be for sure changing which is not reflecting in your query.

         

        regards

        KK

        • 16. Re: DG Standby db not giving normal report?

          SQL> select name, value from v$dataguard_Stats;

           

           

          NAME

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

          VALUE

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

          transport lag

          +00 00:00:00

           

           

          apply lag

          +00 01:24:41

           

           

          apply finish time

          +00 00:00:03.000

           

           

           

           

          NAME

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

          VALUE

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

          estimated startup time

          13

           

          ok its waiting for log now. Thank Anar,KK, & John.

          • 17. Re: DG Standby db not giving normal report?
            Anar Godjaev

            apply lag

            +00 01:24:41

             

            Can you please paste alert log in Secondary location?

             

            tail -50f alert_XXXXX.log

             

            For example in my system:

             

            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

            • 18. Re: DG Standby db not giving normal report?

              SQL> select process,status,sequence# from v$managed_standby;

               

               

              PROCESS   STATUS        SEQUENCE#

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

              ARCH      CLOSING            3498

              ARCH      CONNECTED             0

              ARCH      CLOSING            3495

              ARCH      CLOSING            3496

              RFS       IDLE               3499

              RFS       IDLE                  0

              RFS       IDLE                  0

              MRP0      WAIT_FOR_LOG       3499

               

               

              8 rows selected.

              • 19. Re: DG Standby db not giving normal report?

                Hi Anar,

                 

                tail -50f alert_PRODDR.log

                Mon Dec 02 18:38:03 2013

                RFS[97073]: Assigned to RFS process 1466374

                RFS[97073]: Identified database type as 'physical standby': Client is ARCH pid 815318

                Mon Dec 02 18:38:40 2013

                Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST

                Mon Dec 02 18:39:04 2013

                RFS[97074]: Assigned to RFS process 1351886

                RFS[97074]: Identified database type as 'physical standby': Client is ARCH pid 815318

                Mon Dec 02 18:39:40 2013

                Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST

                Mon Dec 02 18:40:04 2013

                RFS[97075]: Assigned to RFS process 2064584

                RFS[97075]: Identified database type as 'physical standby': Client is ARCH pid 815318

                Mon Dec 02 18:40:40 2013

                Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST

                Mon Dec 02 18:41:05 2013

                RFS[97076]: Assigned to RFS process 880672

                RFS[97076]: Identified database type as 'physical standby': Client is ARCH pid 815318

                Mon Dec 02 18:41:40 2013

                Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST

                Mon Dec 02 18:42:05 2013

                RFS[97077]: Assigned to RFS process 2105412

                RFS[97077]: Identified database type as 'physical standby': Client is ARCH pid 815318

                Mon Dec 02 18:42:40 2013

                Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST

                Mon Dec 02 18:43:06 2013

                RFS[97078]: Assigned to RFS process 1466394

                RFS[97078]: Identified database type as 'physical standby': Client is ARCH pid 815318

                Mon Dec 02 18:43:40 2013

                Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST

                Mon Dec 02 18:44:06 2013

                RFS[97079]: Assigned to RFS process 880682

                RFS[97079]: Identified database type as 'physical standby': Client is ARCH pid 815318

                Mon Dec 02 18:44:40 2013

                Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST

                Mon Dec 02 18:45:07 2013

                RFS[97080]: Assigned to RFS process 1904660

                RFS[97080]: Identified database type as 'physical standby': Client is ARCH pid 815318

                Mon Dec 02 18:45:40 2013

                Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST

                Mon Dec 02 18:46:08 2013

                RFS[97081]: Assigned to RFS process 2035858

                RFS[97081]: Identified database type as 'physical standby': Client is ARCH pid 815318

                Mon Dec 02 18:46:40 2013

                Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST

                Mon Dec 02 18:47:08 2013

                RFS[97082]: Assigned to RFS process 1802270

                RFS[97082]: Identified database type as 'physical standby': Client is ARCH pid 815318

                Mon Dec 02 18:47:40 2013

                Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST

                • 20. Re: DG Standby db not giving normal report?

                  Hi Anar,

                   

                  Why is my apply log is lagging behind?   Yours is 00?

                  • 21. Re: DG Standby db not giving normal report?
                    Anar Godjaev

                    Do you have Oracle Metalink id?

                     

                    I recommend read following Oracle support id  :  Troubleshooting - Heartbeat failed to connect to standby (Doc ID 1432367.1)

                     


                    Updateted:

                     

                    Can you please send me In primary location:

                     

                    SELECT status, error

                    FROM V$ARCHIVE_DEST_STATUS

                    WHERE STATUS <> 'DEFERRED' AND STATUS <> 'INACTIVE';

                    • 22. Re: DG Standby db not giving normal report?
                      Karan Kukreja

                      The lag could be because all of a sudden many archives have been generated and due to network limitation have not yet been transferred to the standby location. The gap should reduce and eventually become 00  as it will be able to pace up during non peak hours. we often face this issue but its ok by the business.

                      • 23. Re: DG Standby db not giving normal report?

                        Hi Anar,

                         

                        SQL> SELECT status, error

                        FROM V$ARCHIVE_DEST_STATUS

                        WHERE STATUS <> 'DEFERRED' AND STATUS <> 'INACTIVE';  2    3

                         

                         

                        STATUS    ERROR

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

                        VALID

                        VALID

                        • 24. Re: DG Standby db not giving normal report?
                          Anar Godjaev

                          Ok, Primary database it is connected secondary database, there are no problems....

                           

                          Please read Troubleshooting - Heartbeat failed to connect to standby (Doc ID 1432367.1)  (recommend)

                          • 25. Re: DG Standby db not giving normal report?

                            Hi kk, anar

                             

                            Our service level agreement is ...our DR standby should be only 30 minutes delayed for the latest applied log.

                            Meaning if disaster strikes only 30 minutes transaction is lost?

                             

                            How can I check if my standby is updated to the last 30 minutes?

                             

                             

                            Thanks,

                            • 26. Re: DG Standby db not giving normal report?
                              Karan Kukreja

                              Hi ,

                               

                              Check the last applied and verify the timestamp of that archive from prod. If no error is seen in the alert logs you may have to ask the network guys to increase the network bandwidth.

                               

                              Helpful link :

                               

                              https://forums.oracle.com/thread/948540

                              regards

                              KK

                              • 27. Re: DG Standby db not giving normal report?

                                Hi kk,

                                 

                                Actually my concern are those database with smaller transactions. We have 50Mb size redologs, and some of the database took 1 day to be able to switch or fill it, hence the DR standby site is lagging 1day+. Do I need to command alter database switch log file every 30 minutes to force log apply?

                                • 28. Re: DG Standby db not giving normal report?

                                  Hi All,

                                   

                                  I thought starting up the MPR0 process is gonna solve my non applied archive logs to STANDBY. But I noticed some logs are not updated, and there are missing archivelog at STANDBY like 3507 and 3508 and up to current, it was not auto transferred.

                                  I tried to manually copy them at STANDBY then issue the command :

                                   

                                  SQL> recover managed standby database disconnect from session;

                                  ORA-01153: an incompatible media recovery is active

                                   

                                  But I got error:

                                   

                                  Please help

                                   

                                  Thanks

                                  • 29. Re: DG Standby db not giving normal report?

                                    I did again

                                     

                                    SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;

                                     

                                     

                                    Database altered.

                                     

                                     

                                    SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;

                                     

                                     

                                    Database altered.