ORA-16826: apply service state is inconsistent with the DelayMins property

APPLIES TO:

Oracle Database - Enterprise Edition - Version 11.2.0.1 to 12.1.0.2 [Release 11.2 to 12.1]
Information in this document applies to any platform.

GOAL

***Checked for relevance on 8-Jul-2015***

Dataguard Broker Configuration

DGMGRL> show configuration verbose;

Configuration - orcl1_site

  Protection Mode: MaxPerformance
  Databases:
    orcl1   - Primary database
    dgorcl1 - Physical standby database
      Warning: ORA-16826: apply service state is inconsistent with the DelayMins property     <<<<<<<<<<<<<<<

  Properties:
    FastStartFailoverThreshold      = '30'
    OperationTimeout                = '30'
    FastStartFailoverLagLimit       = '30'
    CommunicationTimeout            = '180'
    FastStartFailoverAutoReinstate  = 'TRUE'
    FastStartFailoverPmyShutdown    = 'TRUE'
    BystandersFollowRoleChange      = 'ALL'

Fast-Start Failover: DISABLED

Configuration Status:
WARNING

   

DGMGRL> SHOW DATABASE      dgorcl1

Database - dgorcl1

  Role:            PHYSICAL STANDBY
  Intended State:  APPLY-ON
  Transport Lag:   0 seconds
  Apply Lag:       2 minutes 33 seconds
  Real Time Query: OFF
  Instance(s):
    dgorcl11 (apply instance)
    dgorcl12

  Database Warning(s):
    ORA-16826: apply service state is inconsistent with the DelayMins property<<<<<<<<<

Database Status:
WARNING<<<<<<<<<<<<

   

SOLUTION

Workaround :

Check on Which node MRP process is running.

 

On Standby

Make sure  Standby redo logs files are created on standby.

Please refere < Doc ID 249703.1> for the same.

 

DGMGRL> edit database <standby database> set state=apply-off;
DGMGRL> edit database <standby database> set state=apply-on;

or

SQL>alter database recover managed standby database cancel;
SQL> alter database recover managed standby database using current logfile disconnect;

  

Verify Broker Configuration

DGMGRL> show configuration

Configuration - orcl1_site

  Protection Mode: MaxPerformance
  Databases:
    orcl1   - Primary database
    dgorcl1 - Physical standby database

Fast-Start Failover: DISABLED

Configuration Status:
SUCCESS                         <<<<<<<<<<<<<<<<<<

 

GMGRL> show database dgorcl1

Database - dgorcl1

  Role:            PHYSICAL STANDBY
  Intended State:  APPLY-ON
  Transport Lag:   0 seconds
  Apply Lag:       0 seconds
  Real Time Query: OFF
  Instance(s):
    dgorcl11 (apply instance)
    dgorcl12

Database Status:
SUCCESS  <<<<<<<<<<<<<<<<<<<<<<

  

How to avoid this issue


1. This Problem can only happen if Managed Recovery is started manually which should not be done at all if there is an active Data Guard Broker Configuration - reference Doc ID 249703.1

    Typically the Data Guard Broker should start Managed Recovery .

2. It can also happen if there are no Standby RedoLogs in Place or they are incorrect configured - reference Doc ID 219344.1 to set them up.

 

The above document is from Oracle Support (Doc ID 1608166.1)

Comments