LCD-00100: internal error, argument (number(
Cause: An internal error has occurred
Action: Report it to your System Administrator immediately
Cause: An internal error has occurred
Action: Report it to your System Administrator immediately
DGM-17007: Unsupported platform, observer cannot start
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.
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.
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.
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.
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.
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 o shut down the instance but was unable to.
Action: Shut down the specified instance manually.
Cause: The operation was completed successfully and requires a shut down of the specified instance. DGMGRL attempted o 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.
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 or 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.
Cause: The username or 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.
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.
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.
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.
DGM-16953: XML document is too long
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.
Cause: The length of the XML document exceeded the internal limit.
Action: This is an internal error. Contact Oracle Support Services.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
DGM-16933: Unable to start instance string
DGM-16933: Unable to start instance string
Cause: DGMGRL could not start the specified instance because of the errors that displayed with this message.
Action: Start the instance manually.
Cause: DGMGRL could not start the specified instance because of the errors that displayed with this message.
Action: Start the instance manually.
DGM-16917: Unable to shut down instance string
DGM-16917: Unable to shut down instance string
Cause: DGMGRL could not shut down the specified instance because of the errors that are displayed with this message.
Action: Shut down the instance manually.
Cause: DGMGRL could not shut down the specified instance because of the errors that are displayed with this message.
Action: Shut down the instance manually.
DGM-16916: Missing site name, try help
DGM-16916: Missing site name, try help
Cause: The site name is missing from the command.
Action: Try the command again using correct syntax.
Cause: The site name is missing from the command.
Action: Try the command again using correct syntax.
DGM-16912: Unrecognized command string , try help
DGM-16912: Unrecognized command string , try help
Cause: An unrecognized command was issued.
Action: Try again using a valid command.
Cause: An unrecognized command was issued.
Action: Try again using a valid command.
DGM-16911: Warning:
DGM-16911: Warning:
Cause: The command succeeded with warnings.
Action: See accompanying error messages and take the appropriate action.
Cause: The command succeeded with warnings.
Action: See accompanying error messages and take the appropriate action.
DGM-16910: Unable to issue command to server
DGM-16910: Unable to issue command to server
Cause: Command could not be issued to the server.
Action: See additional error messages and or or contact Oracle Support Services.
Cause: Command could not be issued to the server.
Action: See additional error messages and or or contact Oracle Support Services.
DGM-16909: Fatal error - quitting...
DGM-16909: Fatal error - quitting...
Cause: A fatal error was encountered.
Action: See additional error messages and or or contact Oracle Support Services.
Cause: A fatal error was encountered.
Action: See additional error messages and or or contact Oracle Support Services.
DGM-16906: Unable to accept commands: no memory
DGM-16906: Unable to accept commands: no memory
Cause: No memory was available for the attempted operation.
Action: Check your system and retry the command.
Cause: No memory was available for the attempted operation.
Action: Check your system and retry the command.
DGM-16905: Failed.
DGM-16905: Failed.
Cause: The command failed to execute.
Action: Check additional error messages.
Cause: The command failed to execute.
Action: Check additional error messages.
DGM-16904: Unable to set attribute
DGM-16904: Unable to set attribute
Cause: The server attributes could not be set.
Action: Check additional error messages.
Cause: The server attributes could not be set.
Action: Check additional error messages.
DGM-16903: Unable to connect to database
DGM-16903: Unable to connect to database
Cause: The specified database was unreachable because it did not exist or was not started.
Action: Start the database or validate network connections and try again.
Cause: The specified database was unreachable because it did not exist or was not started.
Action: Start the database or validate network connections and try again.
DGM-16902: Unable to allocate handle
DGM-16902: Unable to allocate handle
Cause: The database handle could not be allocated.
Action: This is an internal error. Contact Oracle Support Services.
Cause: The database handle could not be allocated.
Action: This is an internal error. Contact Oracle Support Services.
DGM-16901: Unable to initialize environment
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.
Cause: The database environment could not be allocated and initialized.
Action: This is an internal error. Contact Oracle Support Services.
DGM-16900: Unable to initialize client
DGM-16900: Unable to initialize client
Cause: The client could not be initialized.
Action: This is an internal error. Contact Oracle Support Services.
Cause: The client could not be initialized.
Action: This is an internal error. Contact Oracle Support Services.
NID-00604: No control files found in database
NID-00604: No control files found in database
Cause: Instance has no control files recorded
Action: Report as a bug - the first argument is the internal error number
Cause: Instance has no control files recorded
Action: Report as a bug - the first argument is the internal error number
NID-00603: No datafiles found in database
NID-00603: No datafiles found in database
Cause: Controlfile has not datafiles recorded
Action: Report as a bug - the first argument is the internal error number
Cause: Controlfile has not datafiles recorded
Action: Report as a bug - the first argument is the internal error number
NID-00602: Could not allocate number bytes for string
NID-00602: Could not allocate number bytes for string
Cause: Memory allocation failed.
Action: Free memory at the operating system level and retry operation.
Cause: Memory allocation failed.
Action: Free memory at the operating system level and retry operation.
NID-00601: Internal Error - (number( (string( (number( (number(
NID-00601: Internal Error - (number( (string( (number( (number(
Cause: This is the generic internal error number for program exceptions. This indicates that the program has encountered an exceptional condition.
Action: Report as a bug - the first argument is the internal error number
Cause: This is the generic internal error number for program exceptions. This indicates that the program has encountered an exceptional condition.
Action: Report as a bug - the first argument is the internal error number
NID-00600: Internal Error - (number( (number( (number( (number(
NID-00600: Internal Error - (number( (number( (number( (number(
Cause: This is the generic internal error number for program exceptions. This indicates that the program has encountered an exceptional condition.
Action: Report as a bug - the first argument is the internal error number
Cause: This is the generic internal error number for program exceptions. This indicates that the program has encountered an exceptional condition.
Action: Report as a bug - the first argument is the internal error number
NID-00508: HELP Displays these messages NO
NID-00508: HELP Displays these messages NO
Cause: Informational message.
Action: No action required.
Cause: Informational message.
Action: No action required.
NID-00507: APPEND Append to output log NO
NID-00507: APPEND Append to output log NO
Cause: Informational message.
Action: No action required.
Cause: Informational message.
Action: No action required.
NID-00506: SETNAME Set a new database name only NO
NID-00506: SETNAME Set a new database name only NO
Cause: Informational message.
Action: No action required.
Cause: Informational message.
Action: No action required.
NID-00505: REVERT Revert failed change NO
NID-00505: REVERT Revert failed change NO
Cause: Informational message.
Action: No action required.
Cause: Informational message.
Action: No action required.
NID-00504: LOGFILE Output Log (NONE)
NID-00504: LOGFILE Output Log (NONE)
Cause: Informational message.
Action: No action required.
Cause: Informational message.
Action: No action required.
NID-00503: DBNAME New database name (NONE)
NID-00503: DBNAME New database name (NONE)
Cause: Informational message.
Action: No action required.
Cause: Informational message.
Action: No action required.
NID-00502: TARGET Username or Password (NONE)
NID-00502: TARGET Username or Password (NONE)
Cause: Informational message.
Action: No action required.
Cause: Informational message.
Action: No action required.
NID-00501: ---------------------------------------------------
NID-00501: ---------------------------------------------------
Cause: Informational message.
Action: No action required.
Cause: Informational message.
Action: No action required.
NID-00500: Keyword Description (Default)
NID-00500: Keyword Description (Default)
Cause: Informational message.
Action: No action required.
Cause: Informational message.
Action: No action required.
NID-00490: LOG being redirected to STDERR due to errors.
NID-00490: LOG being redirected to STDERR due to errors.
Cause: Could no write message to log file.
Action: N or A.
Cause: Could no write message to log file.
Action: N or A.
NID-00482: Database is not aware of previous backups and archived logs in Recovery Area.
NID-00482: Database is not aware of previous backups and archived logs in Recovery Area.
Cause: Because the database id was changed, previous backups and archived redo logs in recovery area are not managed by this database.
Action: This is the informational message only.
Cause: Because the database id was changed, previous backups and archived redo logs in recovery area are not managed by this database.
Action: This is the informational message only.
NID-00481: DBNEWID - Cancelled.
NID-00481: DBNEWID - Cancelled.
Cause: Informational message.
Action: No action required.
Cause: Informational message.
Action: No action required.
NID-00480: Database is intact - database is ready to be open or shut down.
NID-00480: Database is intact - database is ready to be open or shut down.
Cause: Informational message.
Action: No action required.
Cause: Informational message.
Action: No action required.
NID-00452: Succesfully changed database ID.
NID-00452: Succesfully changed database ID.
Cause: Informational message.
Action: No action required.
Cause: Informational message.
Action: No action required.
NID-00451: Succesfully changed database name.
NID-00451: Succesfully changed database name.
Cause: Informational message.
Action: No action required.
Cause: Informational message.
Action: No action required.
NID-00450: Succesfully changed database name and ID.
NID-00450: Succesfully changed database name and ID.
Cause: Informational message.
Action: No action required.
Cause: Informational message.
Action: No action required.
NID-00442: Database has been shutdown, open database with RESETLOGS option.
NID-00442: Database has been shutdown, open database with RESETLOGS option.
Cause: Informational message.
Action: No action required.
Cause: Informational message.
Action: No action required.
NID-00441: All previous backups and archived redo logs for this database are unusable.
NID-00441: All previous backups and archived redo logs for this database are unusable.
Cause: Informational message.
Action: No action required.
Cause: Informational message.
Action: No action required.
NID-00440: Database ID for database string changed to number.
NID-00440: Database ID for database string changed to number.
Cause: Informational message.
Action: No action required.
Cause: Informational message.
Action: No action required.
NID-00436: Modify parameter file and generate a new password file before restarting.
NID-00436: Modify parameter file and generate a new password file before restarting.
Cause: Informational message.
Action: No action required.
Cause: Informational message.
Action: No action required.
Subscribe to:
Posts (Atom)