Resetting the status in DGMGRL – GDS

In regular Data Guard configuration, if there is any inconsistency or to refresh the configuration – usually we disable and enable the configuration. So that all the variables are loaded and in this part, there are plenty of possibilities to fix minor issues related to configuration.

This is well and good in a normal environment, but when we are managing the GDS/GSM then the step’s weren’t same. Consider in below example, we can see the warning because of transport lag has exceeded the specified threshold.

DGMGRL> show configuration
Configuration - sh1
Protection Mode: MaxPerformance
 Members:
 sh1 - Primary database
 sh3 - Physical standby database
 Warning: ORA-16855: transport lag has exceeded specified threshold
Fast-Start Failover: DISABLED
Configuration Status:
WARNING (status updated 4 seconds ago)
DGMGRL>

Usually, these warning’s will be get fixed automatically or sometime by doing disable/enable these warnings can be fixed.

DGMGRL> disable configuration
Error: ORA-16522: configuration is part of Global Data Services pool
Failed.
DGMGRL>

But, due to the GDS involvement these type of activities not allowed at configuration level, because it can impact the services. Hence these options are not allowed anymore. So instead of disabling/ enabling of the configuration, still it is possible at database level so that configuration of the database can be reloaded.

DGMGRL> disable database sh3;
Disabled.
DGMGRL> enable database sh3;
Enabled.
DGMGRL> show configuration
Configuration - sh1
Protection Mode: MaxPerformance
Members:
sh1 - Primary database
sh3 - Physical standby database
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS (status updated 23 seconds ago)
DGMGRL>

Having said that, instead of disabling/enabling it is better to fix the issue by increasing transport lag threshold.But in few cases, we have to use the above method as well.