Skip to Content
avatar image
Former Member

Redo log files are not applied in DR of primary

Hi All,

I have a DR database of primary on QA Serevr. The Redo log files are not properly applied in the DR database.

The Oracle version is 11.2.0.1 Some of the files get shipped and applied to DR database automatically but not all.

SQL> select status, error from v$archive_dest where dest_id=2; gives following massage

ERROR ORA-16086: Redo data cannot be written to the standby redo log

Please suggest.

Regards,

Shashi

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • avatar image
    Former Member
    Nov 17, 2011 at 04:10 AM

    Hi,

    Perhaps increasing the recovery area size could help.

    http://arjudba.blogspot.com/2010/09/ora-16086-redo-data-cannot-be-written.html

    Regards,

    Srikishan

    Add comment
    10|10000 characters needed characters exceeded

  • Nov 17, 2011 at 05:37 AM

    Hi,

    Can you provide log details from alert_SID.log file. Whats the error code while applying such redo log files.

    Also I assume that Oracle version 11.2.0.1 is not recommended version for SAP products. Please check PAM for the same.

    Regards,

    Deepak Kori

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi,

      Sorry for delay in response. Here I am attaching the error captured in standby database.

      Please advise

      alert_abc.log

      RFS[1780]: Identified database type as 'physical standby': Client is LGWR SYNC pid 21855

      Primary database is in MAXIMUM AVAILABILITY mode

      Standby controlfile consistent with primary

      Standby controlfile consistent with primary

      RFS[1780]: No standby redo logfiles of file size 94371840 AND block size 512 exist

      Clearing online log 16 of thread 0 sequence number 0

      Errors in file /oracle/diag/rdbms/abc_location11/abc/trace/abc_rfs_27994.trc:

      ORA-00367: checksum error in log file header

      ORA-00315: log 16 of thread 0, wrong thread # 1 in header

      ORA-00312: online log 16 thread 0: '/oracle/abc/origlogB/log_g116m1.dbf'

      Mon Nov 14 00:49:16 2011

      Clearing online log 9 of thread 0 sequence number 0

      Errors in file /oracle/diag/rdbms/abc_location11/abc/trace/abc_arc0_15653.trc:

      /oracle/diag/rdbms/abc_location11/abc/trace/abc_rfs_27994.trc

      • 2011-11-14 00:49:19.385

      DDE rules only execution for: ORA 312

      -


      START Event Driven Actions Dump -


      -


      END Event Driven Actions Dump -


      -


      START DDE Actions Dump -


      Executing SYNC actions

      -


      START DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (Async) -


      DDE Action 'DB_STRUCTURE_INTEGRITY_CHECK' was flood controlled

      -


      END DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (FLOOD CONTROLLED, 1 csec) -


      Executing ASYNC actions

      -


      END DDE Actions Dump (total 0 csec) -


      ORA-00367: checksum error in log file header

      ORA-00315: log 16 of thread 0, wrong thread # 1 in header

      ORA-00312: online log 16 thread 0: '/oracle/abc/origlogB/log_g116m1.dbf'

      DDE rules only execution for: ORA 312

      -


      START Event Driven Actions Dump -


      -


      END Event Driven Actions Dump -


      -


      START DDE Actions Dump -


      Executing SYNC actions

      -


      START DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (Async) -


      DDE Action 'DB_STRUCTURE_INTEGRITY_CHECK' was flood controlled

      -


      END DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (FLOOD CONTROLLED, -641 csec) -


      Executing ASYNC actions

      -


      END DDE Actions Dump (total 0 csec) -


      ORA-19527: physical standby redo log must be renamed

      ORA-00312: online log 16 thread 0: '/oracle/abc/origlogB/log_g116m1.dbf'

      Error 19527 clearing SRL 16

      /oracle/diag/rdbms/abc_location11/abc/trace/abc_arc0_15653.trc

      ORA-19527: physical standby redo log must be renamed

      ORA-00312: online log 9 thread 0: '/oracle/abc/origlogA/log_g19m1.dbf'

      Error 19527 clearing SRL 9

      DDE rules only execution for: ORA 312

      -


      START Event Driven Actions Dump -


      -


      END Event Driven Actions Dump -


      -


      START DDE Actions Dump -


      Executing SYNC actions

  • avatar image
    Former Member
    Jan 05, 2012 at 09:03 PM

    Hey,

    Did you check the following link:

    ORA-19527: physical standby redo log must be renamed _ issue in standby DB

    If yes, please let us know steps carried so far and where you need help.

    Regards,

    Sai R

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi,

      Thanks for the response. I have gone through the suggested link but i have some different issue here as the archive dest 2 is not becoming valid anyway.

      Please suggest me.

      Thanks,