DGM-17007: Unsupported platform, observer cannot start
Cause: The Observer was started on an operating system that does not support multi-threading
Action: Start the Observer on an operating system that supports multi-threading
Category Archives: DGM Database Error Messages
DGM-17002: Primary database cannot be removed
DGM-17002: Primary database cannot be removed
Cause: The named database to be removed is the primary database
Action: Remove the broker configuration instead
DGM-17000: Two or more instances have the name “string”
DGM-17000: Two or more instances have the name "string"
Cause: The named instance exists on more than one database
Action: Use the ON DATABASE clause and reissue the command
DGM-16999: Instance “string” was not found
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-16992: You must shut down instance “string” manually
DGM-16992: You must shut down instance "string" manually
Cause: The operation was completed successfully and requires a shut down of the specified instance. DGMGRL attempted to shut down the instance but was unable to
Action: Shut down the specified instance manually
DGM-16991: Two or more resources have the name “string”
DGM-16991: Two or more resources have the name "string"
Cause: The named resource exists on more than one site
Action: Use the ON SITE clause and reissue the command
DGM-16979: Unable to log on to the primary or standby database as SYSDBA
DGM-16979: Unable to log on to the primary or standby database as SYSDBA
Cause: The username/password used by the observer to log on to the primary database and fast-start failover target standby database does not have valid SYSDBA credentials
Action: Make sure the primary database and Fast-start failover target database are using a remote login password file. Make sure the SYSDBA password is the same at both databases and that the SYSDBA password is used in the CONNECT command. Start the observer again
DGM-16960: Status not available
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 and retry the command
DGM-16959: No response from broker server process
DGM-16959: No response from broker server process
Cause: No response was received from the broker server process (DMON)
Action: The Data Guard broker process (DMON) is not available. Verify that the DMON process is running and retry the command
DGM-16954: Unable to open and lock the Observer configuration file
DGM-16954: Unable to open and lock the Observer configuration file
Cause: The Observer configuration file cannot be opened or cannot be locked for exclusive access
Action: Make sure the Observer has the correct operating system privileges to write the file and there is no other Observer that is using the same file. Try the command again