Mir Sayeed Hassan – Oracle Blog

ORA-16826: apply service state is inconsistent with the DelayMins property on Oracle Database 11gr2(11.2.0.4)

Check the status of database

SQL> select instance_name,version,status,open_mode from V$instance, v$database;

INSTANCE_NAME VERSION STATUS OPEN_MODE
—————- —————– ———— ——————–
pri-db 11.2.0.4.0 OPEN READ WRITE

Check this Broker configuration of database on both primary & standby database

Primary DB

[oracle@pri-db ~]$ dgmgrl
DGMGRL for Linux: Version 11.2.0.4.0 - 64bit Production
Copyright (c) 2000, 2009, Oracle. All rights reserved.
Welcome to DGMGRL, type "help" for information.

DGMGRL> connect sys
Password: *******
Connected.

DGMGRL> show configuration

Configuration - PRDG
Protection Mode: MaxPerformance
Databases:
pri-db - Primary database
std-db - Physical standby database
Warning: ORA-16826: apply service state is inconsistent with the DelayMins property
Fast-Start Failover: DISABLED

Configuration Status:
WARNING

Standby DB

[oracle@std-db ~]$ dgmgrl

DGMGRL for Linux: Version 11.2.0.4.0 - 64bit Production
Copyright (c) 2000, 2009, Oracle. All rights reserved.
Welcome to DGMGRL, type "help" for information.

DGMGRL> connect sys
Password: ******* 
Connected.

DGMGRL> show configuration

Configuration - PRDG
Protection Mode: MaxPerformance
Databases:
pri-db - Primary database
std-db - Physical standby database
Warning: ORA-16826: apply service state is inconsistent with the DelayMins property
Fast-Start Failover: DISABLED

Configuration Status:
WARNING

Note:

Issue: The DGBROKER Configuration Service is not consistent you have to wait for sometime or reenable the dgbroker configuration to fix this issue or there is no standby redologs
Solution: Login to the Standby database & Enable the Standby Service again by DGBrokcer OR Manually stop and restart the Service

Enable the DBBROKER Configuration on standby database & verify

DGMGRL> enable configuration
Enabled.

Verify on both primary & standby db

Primary DB:

DGMGRL> show configuration

Configuration - PRDG
Protection Mode: MaxPerformance
Databases:
pri-db - Primary database
std-db - Physical standby database

Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS

Standby DB

DGMGRL> show configuration

Configuration - PRDG
Protection Mode: MaxPerformance
Databases:
kermandb - Primary database
stdkermandb - Physical standby database
Fast-Start Failover: DISABLED

Configuration Status:
SUCCESS

If its not resolved by using above soluion issue the below method.

Manually stop and start from SQLPLUS

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

=====Hence resolved, tested & verified====