Toad World

ORA-19527: physical standby redo log must be renamed

Avatar photo
Post author:Written By

Data Guard was configured a few days back at one of the customers site. An ORA-19527 error is continuously reported in the standby database alert.log (database name is changed)

MediaBanner-ToadWorld-600x100-IM-JY-63709.psd-1-4

Errors in file /u01/app/oracle/diag/rdbms/orcl/ORCL1/trace/ORCL1_rfs_3504.trc:

ORA-19527: physical standby redo log must be renamed
ORA-00312: online log 9 thread 1: '+DATAC1/ORCL/ONLINELOG/group_9.459.960055023'
Though this didn't stop the data guard replication, the customer wanted to get-rid the message. Starting with v10g, this was an expected behavior to improve the switchover and failover. With v10g, when MRP is started, it will attempt to clear the online log files.

This is also an expected behavior when the log_file_name_convert parameter is set on the standby database. But, in our case, the log_file_name_convert was not required as PRIMARY and STANDBY has the same directory structure (DISK GROUPS for DATA and RECO).

The workaround to get rid of the message, when there is no different in the directory structure, is just to set some dummy values to the parameter, as shown in the below example:

SQL> ALTER SYSTEM SET log_file_name_convert='dummy','dummy';

After the parameter was set, the ORA message was no longer seen in the alert.log

References:
ORA-19527 reported in Standby Database when starting Managed Recovery (Doc ID 352879.1)
ORA-19527: Physical Standby Redo Log Must Be Renamed…during switchover (Doc ID 2194825.1)

 
Tags:

About the Author

Syed Jaffar Hussain

An Oracle Database Expert for over 15 years from his 20 years of Information Technology (IT) career. Over the past 15 years of Oracle journey, he involved with several local and large scaled international banks where he implemented and managed highly complex cluster and non-cluster environments with over 100’s of business critical databases. Recognizing his efforts and contribution towards the Oracle community, Oracle awarded him the prestigious ‘Best DBA of the year, 2011’ and Oracle ACE Director status. He also acquired industry best Oracle credentials, Oracle Certified Master (OCM), Oracle RAC Expert, OCP DBA 8i,9i,10g & 11g in addition to ITIL Expertise. Syed is an active Oracle speaker, regularly presents technical sessions and webinars on various Oracle database technologies at many Oracle events. You can visit his technical blog, http://jaffardba.blogspot.com where he discuss and writes the workaround/solution about the issues confronted from his day-to-day activities. Apart from being the part of the core Technical Review committee member for a few Oracle technology oriented books, he also co-authored an Oracle 11g R1/R2 Real Application Cluster Essentials and Oracle Expert RAC books. His blog can be found at http://jaffardba.blogspot.com/

Notable Replies

  1. says:
    santu.shine

    Hi Syed,

    Thanks for the article. I was facing the issue and searched google and found your article which helped me resolve the issue. Would like to add some more on this.
    If we have broker configuration, then we may need some more changes.

    Status of DGMGRL after parameter change

    oracle@xldn30311tor::trace > dgmgrl /
    DGMGRL for Linux: Release 18.0.0.0.0 - Production on Mon Feb 8 08:31:03 2021
    Version 18.8.0.0.0

    Copyright (c) 1982, 2018, Oracle and/or its affiliates. All rights reserved.

    Welcome to DGMGRL, type "help" for information.
    Connected to ""
    Connected as SYSDG.
    DGMGRL> show configuration;

    Configuration - dg_config

    Protection Mode: MaxPerformance
    Members:
    - Primary database
    - Physical standby database
    Warning: ORA-16792: configurable property value is inconsistent with member setting

    Fast-Start Failover: DISABLED

    Configuration Status:
    WARNING (status updated 18 seconds ago)

    DGMGRL>

    DGMGRL> show database 'InconsistentProperties'
    INCONSISTENT PROPERTIES
    INSTANCE_NAME PROPERTY_NAME MEMORY_VALUE SPFILE_VALUE BROKER_VALUE
    LogFileNameConvert dummy, dummy dummy,dummy

    DGMGRL> EDIT DATABASE set property LogFileNameConvert ='dummy,dummy';
    Warning: ORA-16675: database instance restart required for property value modification to take effect

    Property "logfilenameconvert" updated
    DGMGRL>

    Restart DB:

    oracle@xldn30311tor::trace > srvctl stop db -d
    oracle@xldn30311tor::trace > srvctl start db -d -o mount

    Status of DGMGRL

    oracle@xldn30311tor::trace > dgmgrl /
    DGMGRL for Linux: Release 18.0.0.0.0 - Production on Mon Feb 8 08:40:19 2021
    Version 18.8.0.0.0

    Copyright (c) 1982, 2018, Oracle and/or its affiliates. All rights reserved.

    Welcome to DGMGRL, type "help" for information.
    Connected to ""
    Connected as SYSDG.
    DGMGRL> show configuration;

    Configuration - dg_config

    Protection Mode: MaxPerformance
    Members:
    - Primary database
    - Physical standby database

    Fast-Start Failover: DISABLED

    Configuration Status:
    SUCCESS (status updated 32 seconds ago)

    DGMGRL>

    Regards,
    Santosh Kumar

  2. says:
    nikki.medinger

    Hi Santu, Thanks for replying to the blog article and adding to it. Your response helps others. As editor of the Toad World blogs, I wanted to thank you. We appreciate your feedback and contribution to the community!

Continue Discussion