Issue:
After completing the reinstate process, I checked my configuration. It throws me a warning message with ORA-16629.
DGMGRL> reinstate database 'BHU_A';
Reinstating database "BHU_A", please wait...
Reinstatement of database "BHU_A" succeeded
DGMGRL> show configuration;
Configuration - DG_BHU
Protection Mode: MaxAvailability
Databases:
BHU_B - Primary database
Warning: ORA-16629: database reports a different protection level from the protection mode
BHU_A - Physical standby database
Fast-Start Failover: DISABLED
Configuration Status:
WARNING
TO CHECK THE COMPLETE DETAILS OF THE DATABASE
DGMGRL> show database verbose 'BHU_B';
SOLUTION:
Since I am running in the MAX AVAILABILITY, I tried to check the following parameter on the primary site
DGMGRL> show database verbose 'BHU_B';
Database - BHU_B
Role: PRIMARY
Instance(s):
BHU_1
BHU_2
Properties:
DGConnectIdentifier = 'BHU_B_DG'
ObserverConnectIdentifier = ''
LogXptMode = 'SYNC'
.
.
(*) - Please check specific instance for the property value
Database Status:
SUCCESS
you can see the difference in the parameter log_archive_dest_2 of each instance.
Node#1
check log_archive_dest_2 or check destination, where archive shipping is enable
Node#2
check log_archive_dest_2 or check destination, where archive shipping is enable
I tried to Re-Apply or change the protection mode to max availability on the primary database.
DGMGRL> EDIT CONFIGURATION SET PROTECTION MODE AS MAXAVAILABILITY;
Succeeded.
DGMGRL> show configuration;
Configuration - DG_BHU
Protection Mode: MaxAvailability
Databases:
BHU_B - Primary database
BHU_A - Physical standby database
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS
DGMGRL>
No comments:
Post a Comment