DGM-16953: XML document is too long
Cause: The length of the XML document exceeded the internal limit
Action: This is an internal error. Contact Oracle Support Services
Category Archives: DGM Database Error Messages
DGM-16952: Configuration details cannot be determined by DGMGRL
DGM-16952: Configuration details cannot be determined by DGMGRL
Cause: The broker configuration could not be found
Action: 1) The Data Guard broker process (DMON) could not be contacted. Verify that the DMON process is running. 2) No broker configuration currently exists. You must create one. 3) You are connected to a standby database in the broker configuration that has either been disabled or deleted. While the standby is in this state, the details of the broker configuration are not available on the standby database. Connect to the primary database and reissue the command. 4) You are connected to a database in the broker configuration that must be reinstated or reinstantiated. While in this state, details of the broker configuration are not available. Either reinstate or reinstantiate the database and reissue the command, or connect to the primary database and reissue the command
DGM-16951: Unable to failover
DGM-16951: Unable to failover
Cause: The failover operation could not be executed due to the errors reported with this error message
Action: Correct the errors and try the FAILOVER command again
DGM-16949: Object “string” was not found
DGM-16949: Object "string" was not found
Cause: The named object was not found
Action: Try the command again using a valid database name
DGM-16948: Unable to switchover, primary database is still “string”
DGM-16948: Unable to switchover, primary database is still "string"
Cause: The switchover operation could not be executed due to the errors reported with this error message. The primary role has not been changed
Action: Correct the errors and try the SWITCHOVER command again
DGM-16946: Site “string” was not found
DGM-16946: Site "string" was not found
Cause: The named site could not be found
Action: Try the command again using a valid site name
DGM-16945: Syntax error before or at “string”
DGM-16945: Syntax error before or at "string"
Cause: The command could not be processed because of a syntax error in the named token
Action: Try the command again using valid syntax
DGM-16944: Failover succeeded, new primary is “string”
DGM-16944: Failover succeeded, new primary is "string"
Cause: The failover command completed successfully
Action: No action is required
DGM-16943: You must connect to instance “string” and issue the command again
DGM-16943: You must connect to instance "string" and issue the command again
Cause: The operation required DGMGRL to connect to a specific instance to complete, but DGMGRL could not automatically connect to the given instance
Action: Connect to the specified instance and issue the command again
DGM-16934: You must start instance “string” manually
DGM-16934: You must start instance "string" manually
Cause: The operation completed successfully and requires a restart of the specified instance. DGMGRL attempted to restart the instance but was unable to
Action: Start the specified instance manually