ORA-16826: apply service state is inconsistent


APPLIES TO:

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

GOAL

Data Guard 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 referenceInteraction Between the Data Guard Broker and a Data Guard Configuration Doc ID 249703.1

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

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

How to avoid this issue


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.

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

相关文章

数据库版本:11.2.0.4 RAC(1)问题现象从EM里面可以看到,在23号早上8:45~8:55时,数据库等待会话暴增...
(一)问题背景最近在对一个大约200万行数据的表查看执行计划时,发现存在异常,理论上应该返回100多万...
(一)删除备份--DELETE命令用于删除RMAN备份记录及相应的物理文件。当使用RMAN执行备份操作时,会在RM...
(1)DRA介绍 数据恢复顾问(Data Recovery Advise)是一个诊断和修复数据库的工具,DRA能够修复数据文...
RMAN(Recovery Manager)是Oracle恢复管理器的简称,是集数据库备份(backup)、修复(restore)和恢复...
(1)备份对象 可以使用RMAN进行的备份对象如下: --整个数据库:备份所有的数据文件和控制文件; --数...