Skip to Content
avatar image
Former Member

Oracle data guard config error - Redo transport service for standby database error

capture1.png capture.png

Hi All,

I am facing unusual error redo transport service for standby database error as shown below.

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

I have checked the v$flash_recovery_area_usage and we have enough space both in primary and standby but somehow I can see below error in alert log

Error 16086 creating standby archive log file at host 'xxx' *** 2018-02-12 14:59:11.940 4338 krsh.c LGWR: Attempting destination LOG_ARCHIVE_DEST_2 network reconnect (16086) *** 2018-02-12 14:59:11.940 4338 krsh.c LGWR: Destination LOG_ARCHIVE_DEST_2 network reconnect abandoned *** 2018-02-12 14:59:11.941 4338 krsh.c Error 16086 for archive log file 4 to 'xxx'

Any assistance much appreciated.

Thanks

Sateesh

capture.png (17.8 kB)
capture1.png (58.3 kB)
Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Feb 14 at 11:41 AM

    Hi Sateesh,

    If you are using DataGuard Manager to transfer the redologs, use below commands to bet an overview and info about the possible cause:

    DGMGRL> show configuration -> This will show ypu exactly if there are any errors.

    DGMGRL> show database <db_unique_name> -> Same as above but for one node only.

    Besides this Oracle provides a very good article for troubleshooting, just search with keywords below:

    "dgmgrl log 12.1"

    Regards,

    János

    Add comment
    10|10000 characters needed characters exceeded

  • Feb 13 at 01:30 AM

    Hi Sateesh,

    This seems network unavailability, please attach alert log from both primary and standby.

    Although not the same error, please perform the basic check as mentioned in kba 1701375.

    Best regards,
    James

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Sateesh,

      So you meant "ALTER SYSTEM SET log_archive_dest_state_2='DEFER' SCOPE=BOTH;" was set by purpose?

      Does "ALTER SYSTEM SET log_archive_dest_state_2='DEFER' SCOPE=BOTH;" ever worked?

      log_archive_dest_state_2='DEFER' is used to turn off the log shipping, I am not sure the impact of log_archive_dest_state_2='DEFER' afterwards.


      Best regards, James

  • Feb 16 at 04:28 PM

    If this is an intermittent issue then you should look at the network side. Faced this issue in the past when the standby goes out of sync when the log shipping gets interrupted due to bad network. We had the network team investigate the network settings and after making few some changes and the issue got resolved.

    Add comment
    10|10000 characters needed characters exceeded