Dataguard : ORA-16826 apply service state is inconsistent when changing mode to MaxProtection

Posted By Sagar Patil

This morning I moved my Standby database from Maxperformance to Maxprotection while it returned ORA-16826

DGMGRL> show configuration;
Configuration – sample
Protection Mode: MaxProtection
Databases:
primary   – Primary database
secondary – Physical standby database
Warning: ORA-16826: apply service state is inconsistent with the DelayMins
property
Fast-Start Failover: DISABLED
Configuration Status:
WARNING

When I tried to remove secondary database to correct ORA-16826, I have following error ORA-16627

DGMGRL> remove database ‘secondary’;
Error: ORA-16627: operation disallowed since no standby databases would remain to support protection mode

To correct this issue, I need to move it to MAXPerformance mode

DGMGRL> EDIT CONFIGURATION SET PROTECTION MODE AS  MAXPerformance;
Succeeded.

DGMGRL> remove database secondary;
Removed database “secondary” from the configuration

DGMGRL> ADD DATABASE ‘secondary’ AS CONNECT IDENTIFIER IS secondary MAINTAINED A
S PHYSICAL;
Database “secondary” added

DGMGRL> show database secondary;
Database – secondary
Role:            PHYSICAL STANDBY
Intended State:  OFFLINE
Transport Lag:   (unknown)
Apply Lag:       (unknown)
Real Time Query: OFF
Instance(s): secondary
Database Status:
DISABLED

DGMGRL> enable database secondary;
Enabled.

DGMGRL> show configuration;
Configuration – sample
Protection Mode: MaxPerformance
Databases:
primary   – Primary database
secondary – Physical standby database
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS

DGMGRL> EDIT CONFIGURATION SET PROTECTION MODE AS  MAXPROTECTION;
Error: ORA-16627: operation disallowed since no standby databases would remain to support protection mode
Failed.

DGMGRL> EDIT DATABASE ‘secondary’ SET PROPERTY ‘LogXptMode’=’SYNC’;
Property “LogXptMode” updated

DGMGRL> EDIT CONFIGURATION SET PROTECTION MODE AS  MAXPROTECTION;
Operation requires shutdown of instance “primary” on database “primary”
Shutting down instance “primary”…
Database closed.
Database dismounted.
ORACLE instance shut down.
Operation requires startup of instance “primary” on database “primary”
Starting instance “primary”…

DGMGRL> connect sys/manager@primary
Connected.
DGMGRL> show configuration;
Configuration – sample
Protection Mode: MaxProtection
Databases:
primary   – Primary database
secondary – Physical standby database
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS

Leave a Reply

You must be logged in to post a comment.

Top of Page

Top menu