@H_403_2@

APPLIES TO:

Oracle Database - Enterprise Edition - Version 11.2.0.1 and later
Information in this document applies to any platform.
@H_403_2@

GOAL

Data Guard Broker Configuration@H_403_2@

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@H_403_2@

@H_403_2@

@H_403_2@

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<<<<<<<<<<<<@H_403_2@

@H_403_2@

@H_403_2@

SOLUTION

Workaround :@H_403_2@

Check on which node MRP process is running.@H_403_2@

On Standby@H_403_2@

Make sure Standby redo logs files are created on standby.@H_403_2@

Please referenceInteraction Between the Data Guard Broker and a Data Guard Configuration Doc ID 249703.1@H_403_2@

@H_403_2@

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

or@H_403_2@

sql>alter database recover managed standby database cancel;
sql> alter database recover managed standby database using current logfile disconnect;@H_403_2@

@H_403_2@

Verify Broker Configuration@H_403_2@

DGMGRL> show configuration

Configuration - orcl1_site

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

Fast-Start Failover: DISABLED

Configuration Status:
SUCCESS <<<<<<<<<<<<<<<<<<
@H_403_2@

DGMGRL> 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 <<<<<<<<<<<<<<<<<<<<<<@H_403_2@

How to avoid this issue@H_403_2@

1. This Problem occurs if Managed Recovery is started manually which should not be done at all if there is an active Data Guard Broker Configuration.
@H_403_2@

Typically the Data Guard Broker should start Managed Recovery .

2. It can also happen if there are no Standby Redo Logs in Place or they are incorrect configured - referenceUsage,Benefits and Limitations of Standby Redo Logs (SRL) Doc ID 219344.1@H_403_2@