Skip to Content
avatar image
Former Member

Oracle data guard - Logs not applying

Hi,

I had configured Oracle dataguard and was working fine when both the primary and secondary servers were on the same network. We shifted the standby server to a remote location. Since then the logs were not moving to the standby server. So I took a fresh backup of the primary server and restored on the standby server and created a fresh standby control file. Now, the logs are moving from primary to secondary. There was a gap of 60 logs between the time backup was taken on primary and restored on the secondary. Now those 60 logs are also getting copied to falarch folder. (it is still being copied as it takes time over WAN).

The problem is these logs are not being applied to the database. When I do SQL>select * from v$archive_log; the output is no row selected.

alter database recover managed standby database cancel;

ORA-6136 Managed standby recovery not active

Can anyone please help me to resolve this?

Regards

Ivan

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • avatar image
    Former Member
    Feb 16, 2012 at 01:13 PM

    Hello Ivan,

    Have you already tried to copy those archives manually to the standby destination?

    Best regards,

    Thiago

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Thaigo,

      The log files are getting copied automatically to the falarch folder. I am waiting for that to complete in some time. The current logs are being copied to oraarch folder, and the previous missing logs are being copied to falarch.

      Regards

      Ivan

  • avatar image
    Former Member
    Feb 16, 2012 at 01:26 PM

    Hi Ivan,

    What is the version of Oracle?

    Did you try the following?

    alter database recover mananged standby database disconnect from session;

    ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;

    Br,

    Venky

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Venky,

      Yes the logs transferred completely. But when I tried the command ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL; I would get the message database altered. But in the saptrace\background I would get the error about the PSAPSR3 tablespace related error. When I checked on the primary this tablespace was 99.3% full. I tried increasing this tablespace in secondary by BRTOOLS, but it would crash every time. Since I could not spend more time in that remote DR site I had to bring the DR server back to primary site.

      WIll check next week.

  • avatar image
    Former Member
    Feb 17, 2012 at 11:02 AM

    Hi Ivan,

    Please check the following

    
    
    SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS FROM V$MANAGED_STANDBY; 
    
    

    Check to see that mrp0 is active and running...

    If u do not see the mrp0 process , see why mrp0 has stopped running in saptrace/background ?

    Secondly, if the logs are shipped automatically they will be registered in the v$archived_log view

    select sequence#, archived, applied from v$archived_log order by sequence#;
    

    Third, if u do not see any errors above....see if the logs get applied manually

    
    recover standby database
    
    

    Finally check the alert log file for any errors

    Thanks,

    Salman

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Nov 13, 2013 at 07:08 AM

    Hello,

    We are facing the same issue though our DR is still at same location and gets same error for the command ( ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL; ) .

    ORA-16136: Managed Standby Recovery not active

    We cant find the tracefile or logfile to check the error details. Can you please help us to resolve the issue.

    Quick response will be appreciated.

    Regards,

    Khuram

    Add comment
    10|10000 characters needed characters exceeded