锐客网

  1. 首页 > 生活百科 > it技术 > >

ORA-16826: apply service state is inconsistent

IT知识consistentInconsistentservice

大道之行，天下为公。这篇文章主要讲述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【ORA-16826: apply service state is inconsistent】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< < < < < < < < < < < <
   

 
 
SOLUTIONWorkaround :
Check on which node MRP process is running.
 
On Standby
Make sure  Standby redo logs files are created on standby.
Please reference  Interaction 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 - reference    Usage, Benefits and Limitations of Standby Redo Logs (SRL) Doc ID 219344.1



    推荐阅读


    上一篇：Android组件-1-四大组件

    下一篇：Win10中打开tif格式文件的办法