Accidentally or purposely,
we sometimes need to disable a database from DG broker configuration. This is
done by using command on DGMGRL.
|
[oracle:DB_DG ~]$ dgmgrl /
DGMGRL for Linux: Version 11.2.0.4.0 - 64bit
Production
Copyright (c) 2000, 2009, Oracle. All rights
reserved.
Welcome to DGMGRL, type "help" for
information.
Connected.
DGMGRL> show configuration
Configuration - TEST DG configuration
Protection
Mode: MaxPerformance
Databases:
DB_PROD - Primary database
DB_DG -
Physical standby database
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS
DGMGRL> disable database 'DB_DG'
Disabled.
|
Later, if we try to
enable the database again, ORA-16541 will be returned.
|
DGMGRL> enable database 'DB_DG'
ORA-16541: database is not enabled
Configuration details cannot be determined by DGMGRL
|
To enable this database
in the configuration successfully, try to enable it while connected with the
other database in this dataguard configuration. For example, I faced this error
when I disabled my standby database as you can see above. To enable this, I
logged into my primary database host and connected with the primary database
using DGMGRL, and I was able to enable my standby database that I disabled
previously.
|
[oracle:DB_PROD ~]$ dgmgrl /
DGMGRL for Linux: Version 11.2.0.4.0 - 64bit
Production
Copyright (c) 2000, 2009, Oracle. All rights
reserved.
Welcome to DGMGRL, type "help" for
information.
Connected.
DGMGRL> show configuration
Configuration - TEST DG configuration
Protection
Mode: MaxPerformance
Databases:
DB_PROD - Primary database
DB_DG -
Physical standby database (disabled)
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS
DGMGRL> enable database 'DB_DG';
Enabled.
DGMGRL> show configuration
Configuration - TEST DG configuration
Protection
Mode: MaxPerformance
Databases:
DB_PROD - Primary database
DB_DG -
Physical standby database
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS
|
No comments:
Post a Comment