Action: This is an internal error. Contact Oracle Support Services.
DGM-16901: Unable to initialize environment
Cause: The database environment could not be allocated and initialized.
Action: This is an internal error. Contact Oracle Support Services.
DGM-16902: Unable to allocate handle
Cause: The database handles could not be allocated.
Action: This is an internal error. Contact Oracle Support Services.
DGM-16903: Unable to connect to database
Cause: The specified database was unreachable because it does not exist or was not started.
Action: Correct the request or start the database and try again.
DGM-16904: Unable to set attribute
Cause: The server attributes could not be set.
Action: Check additional error messages.
DGM-16905: Failed.
Cause: The given action failed.
Action: Check additional error messages.
DGM-16906: Unable to accept commands: no memory
Cause: No memory was available for the program.
Action: Increase memory and try again.
DGM-16909: Fatal error - quitting...
Cause: A fatal error was encountered.
Action: See additional error messages and/or contact Oracle Support Services.
DGM-16910: unable to issue command to server
Cause: Commands cannot be issued to the server.
Action: See additional error messages and/or contact Oracle Support Services.
DGM-16911: Warning:
Cause: An action succeeded with warnings.
Action: See error message and take appropriate action.
DGM-16912: Unknown command "string". Try "help"
Cause: An unknown command was issued.
Action: Try again using a valid command.
DGM-16916: Missing site name. Try "help"
Cause: The site name is missing.
Action: Try the command again using correct syntax
DGM-16917: Unable to shut down instance "string".
Cause: DGMGRL could not shut down the given instance because of the errors that displayed prior to this message.
Action: Shut down the instance manually.
DGM-16933: Unable to start instance "string".
Cause: DGMGRL could not start the given instance because of the errors that displayed prior to this message.
Action: Start the instance manually.
DGM-16934: You must start instance "string" manually.
Cause: The operation was successfully completed, and it requires startup of the given instance. However, DGMGRL was unable to perform an automatic startup.
Action: Start the given instance manually.
DGM-16943: You must connect to instance "string" and issue the command again.
Cause: The operation requires DGMGRL to connect to a specific instance to complete, but DGMGRL could not automatically connect to the given instance.
Action: Connect to the given instance and issue the command again.
DGM-16944: Failover succeeded. New primary is "string"
Cause: The failover operation succeeded.
Action: No action is required.
DGM-16945: Syntax error before or at "string"
Cause: The given command could not be processed because a syntax error occurred at the named token.
Action: Try the command again using valid syntax.
DGM-16946: Site "string" was not found
Cause: The named site could not be found.
Action: Try the command again using a valid site.
DGM-16948: Can not proceed to switchover. Primary is still "string".
Cause: The switchover operation could not be executed due to the errors reported before this error message. The primary role has not been changed.
Action: Correct the errors reported before this error message and try the switchover command again.
DGM-16949: "string" was not found
Cause: The named object was not found.
Action: Try the command again using a valid database name.
DGM-16951: Can not proceed to failover.
Cause: The failover operation could not be executed due to the errors reported before this error message.
Action: Correct the errors reported before this error message and try the failover command again.
DGM-16952: unable to describe configuration
Cause: The broker configuration could not be described.
Action: The Data Guard broker process (DMON) could not be contacted. Verify that the DMON process is running.
DGM-16959: NULL answer from DMON
Cause: No answer came from the DMON process.
Action: The Data Guard broker process (DMON) is not available. Verify that the DMON process is running.
DGM-16960: status not available
Cause: The status could not be retrieved.
Action: The Data Guard broker process (DMON) is not available. Verify that the DMON process is running.
DGM-16991: More than one resources have name "string".
Cause: The named resource exists on more than one site.
Action: The request must be more specific. Issue the command again using the ON SITE clause.
DGM-16992: You must shut down instance "string" manually.
Cause: The operation was successfully completed, and it requires shutdown of the given instance. However, DGMGRL was unable to perform an automatic shutdown.
Action: Shut down the given instance manually.
DGM-16999: Instance "string" was not found.
Cause: The named instance could not be found.
Action: Try the command again using a valid instance name.
DGM-17000: More than one instances have name "string".
Cause: The named instance exists on more than one databases.
Action: The request must be more specific. Issue the command again using the ON DATABASE clause.
DGM-17002: Primary database can not be removed.
Cause: The named database to be removed is the primary database.
