Fix: Warning: ORA-16826: apply service state is inconsistent with the DelayMins property in DGMGRL

Toubleshoot: Warning: ORA-16826: apply service state is inconsistent with the DelayMins property - in DGMGRL ( Dataguard broker environment)


Error Description:
Show configuration command shows following warning in DGMGRL.

DGMGRL> connect sys@STANDBY
Password: xxxxx
Connected.
DGMGRL> show configuration;

Configuration - DR_Config

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

Fast-Start Failover: DISABLED

Configuration Status:
WARNING

DGMGRL> show database 'STANDBY';

Database - STANDBY

  Role:            PHYSICAL STANDBY
  Intended State:  APPLY-ON
  Transport Lag:   0 seconds
  Apply Lag:       7 minutes 4 seconds
  Real Time Query: OFF
  Instance(s):     STANDBY

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

Database Status: WARNING


Solution Description:

The error is because of the mismatch with the delaymins property of the data guard. If your DelayMins = '0' is coming like this from "show database 'STANDBY' " database, then You have to run the following command to fix this warning.

Note: Be sure both primary and standby database listeners should up and running.

SQL> select name,open_mode,database_role from v$database;

NAME      OPEN_MODE            DATABASE_ROLE
--------- -------------------- ----------------
STANDBY   MOUNTED              PHYSICAL STANDBY

SQL> alter database recover managed standby database cancel;

Database altered.

SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT FROM SESSION;

Database altered.

-- Now check after the above activity
DGMGRL> show database 'STANDBY';

Database - STANDBY

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

Database Status: SUCCESS