0 Replies Latest reply: Apr 9, 2013 12:42 PM by Orna Weisman RSS

    Gap resolution is not  always happening with real time apply

    Orna Weisman
      Hi

      I noticed a strange behavior in one of my 10.2.0.4 dataguards , and I am wondering if anyone else has encountered it :

      When there is an archive gap that need to be resolved , the gap is NOT always being identified and acted upon , when the recovery is started as such :

      ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT FROM SESSION.

      its just sitting there doing nothing, and nothing is written to the alert log regarding the gap and nothing is being transferred from the primary as needed.

      However, if I restart the apply , omitting the 'USING CURRENT LOGFILE' clause , the gap is identified and acted upon, as such :

      ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION.

      At first I thought its merely due to me stopping and starting the apply process ( nothing like a "reboot" , right ? ) , but that is not the case.
      if I restart , but still use the USING CURRENT LOGFILE clause , the gap is still not being identified .

      Anyone had this issue ? any theories as to why that happens ?