4 Replies Latest reply on Aug 10, 2016 8:42 PM by BPeaslandDBA

    Oracle ODG Managed Recovery Issue

    user13354807

      At Standby oracle DB we have configured SRL (Standby recovery logs) and started recovery using "Managed Recovery Process"  instead of using Real Time Recovery (with using current log file)

      But, we have observed that the logs are getting applied using Real Time recovery only.  Also, when we are using the delay option then its giving delay option as illegal.

      Below here are the logs, please suggest on this.

       

      alter database recover managed standby database disconnect from session

      Thu Aug 04 11:11:55 2016

      Attempt to start background Managed Standby Recovery process (SP1)

      Starting background process MRP0

      Thu Aug 04 11:11:55 2016

      MRP0 started with pid=7, OS id=19043

      Thu Aug 04 11:11:55 2016

      MRP0: Background Managed Standby Recovery process started (SP1)

      Thu Aug 04 11:12:00 2016

      Started logmerger process

      Thu Aug 04 11:12:00 2016

      Managed Standby Recovery starting Real Time Apply

      Thu Aug 04 11:12:02 2016

      Parallel Media Recovery started with 16 slaves

      Thu Aug 04 11:12:02 2016

      Waiting for all non-current ORLs to be archived...

      Thu Aug 04 11:12:02 2016

      All non-current ORLs have been archived.

      Thu Aug 04 11:12:02 2016

      Recovery of Online Redo Log: Thread 1 Group 11 Seq 17626 Reading mem 0

        Mem# 0: /oracle/SP1/origlogA/srllog_g11m1.dbf

      Completed: alter database recover managed standby database disconnect from session

      Thu Aug 04 11:25:29 2016

        • 1. Re: Oracle ODG Managed Recovery Issue
          user13354807

          any views on this issue ?

          • 2. Re: Oracle ODG Managed Recovery Issue
            BPeaslandDBA

            we have observed that the logs are getting applied using Real Time recovery only

             

            Can you show more of the alert log that shows this?

             

             

            Also, when we are using the delay option then its giving delay option as illegal.

             

            Can you show this as well?

             

            Which Oracle version? Are you using the DG Broker?

            Cheers,
            Brian

            • 3. Re: Oracle ODG Managed Recovery Issue
              user13354807

              hi,

               

              Oracle version  - Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production

              yes, we are using Oracle DataGuard.

               

              alertlog -

              Completed: alter database recover managed standby database disconnect from session

              Thu Aug 04 11:25:29 2016

              db_recovery_file_dest_size of 10240 MB is 0.00% used. This is a

              user-specified limit on the amount of space that will be used by this

              database for recovery-related files, and does not reflect the amount of

              space available in the underlying filesystem or ASM diskgroup.

              Thu Aug 04 11:25:32 2016

              Default pga_aggregate_limit value is too high for the

              amount of physical memory in the system

              pga_aggregate_limit is 45875 MB

              limit based on physical memory and SGA usage is 35768 MB

              Thu Aug 04 11:47:23 2016

              RFS[1]: Selected log 12 for thread 1 sequence 17627 dbid 1667780269 branch 898547949

              Thu Aug 04 11:47:23 2016

              Media Recovery Waiting for thread 1 sequence 17627 (in transit)

              Thu Aug 04 11:47:23 2016

              Archived Log entry 16721 added for thread 1 sequence 17626 ID 0x636878ad dest 1:

              Thu Aug 04 11:47:24 2016

              Recovery of Online Redo Log: Thread 1 Group 12 Seq 17627 Reading mem 0

                Mem# 0: /oracle/<sid>/origlogB/srllog_g12m1.dbf

              Thu Aug 04 12:28:17 2016

              RFS[1]: Selected log 11 for thread 1 sequence 17628 dbid 1667780269 branch 898547949

              Thu Aug 04 12:28:17 2016

              Media Recovery Waiting for thread 1 sequence 17628 (in transit)

              Thu Aug 04 12:28:17 2016

              Archived Log entry 16722 added for thread 1 sequence 17627 ID 0x636878ad dest 1:

              Thu Aug 04 12:28:18 2016

              Recovery of Online Redo Log: Thread 1 Group 11 Seq 17628 Reading mem 0

                Mem# 0: /oracle/<sid>/origlogA/srllog_g11m1.dbf

              Thu Aug 04 13:01:58 2016

              RFS[1]: Selected log 12 for thread 1 sequence 17629 dbid 1667780269 branch 898547949

              Thu Aug 04 13:01:58 2016

              Media Recovery Waiting for thread 1 sequence 17629 (in transit)

              Thu Aug 04 13:01:58 2016

              Archived Log entry 16723 added for thread 1 sequence 17628 ID 0x636878ad dest 1:

              Thu Aug 04 13:01:59 2016

              Recovery of Online Redo Log: Thread 1 Group 12 Seq 17629 Reading mem 0

                Mem# 0: /oracle/<sid>/origlogB/srllog_g12m1.dbf

              Thu Aug 04 13:48:38 2016

              RFS[1]: Selected log 11 for thread 1 sequence 17630 dbid 1667780269 branch 898547949

              Thu Aug 04 13:48:38 2016

              Media Recovery Waiting for thread 1 sequence 17630 (in transit)

              • 4. Re: Oracle ODG Managed Recovery Issue
                BPeaslandDBA

                This system does appear to be using real-time apply. Otherwise, you would see messages like this:

                 

                Media Recovery Log /u01/app/oracle/admin/stdby/arch/7_27595_677462342.dbf

                 

                Those are not in the alert log, but MRP is active and running just fine. But just to be sure, what does RECOVERY_MODE from V$ARCHIVE_DEST_STATUS show?

                 

                Is that not your desired outcome? Normally, real-time apply is desired except if you intentionally want a delay. You did say this at one point:

                 

                Also, when we are using the delay option then its giving delay option as illegal.

                 

                Can you show the exact command you issued and the exact message?

                 

                Also...are you using the DG Broker or not?

                 

                Cheers,
                Brian