Oracle Database Errors or Warnings from Error ORA-16602 to ORA-16613
ORA-16602: database must be disabled to perform this operation
Cause: An attempt was made to edit a database property while the database was enabled.
Action: Disable the database and retry the command.
ORA-16603: Data Guard broker detected a mismatch in configuration ID
Cause: There was a mismatch in configuration unique ID. This could occur if the original configuration was re-created while this database was disconnected from the network or the same database was added to two different Data Guard broker configurations.
Action: Make sure the database belongs to only one broker configuration. Shut down the broker by setting the DG_BROKER_START initialization parameter to false. Then remove the Data Guard broker configuration files. Finally restart the broker by setting the DG_BROKER_START initialization parameter to true.
ORA-16606: unable to find property “string”
Cause: The specified property did not exist.
Action: Specify a valid property name and reissue the request.
ORA-16607: one or more databases have failed
Cause: A failure was detected for one or more databases in the Data Guard broker configuration.
Action: Locate the database(s) with a failure status and correct it.
ORA-16608: one or more databases have warnings
Cause: A warning was detected for one or more databases in the Data Guard broker configuration.
Action: Locate the database(s) with a warning status and correct it.
ORA-16609: database is being disabled
Cause: A command was attempted on a database that was being disabled. For example, attempting to reinstate the old primary database, the database that was the primary database prior to the most recent failover, before it was ready to be reinstated.
Action: Wait for the Data Guard broker to disable the database and then retry the command.
ORA-16610: command “string” in progress
Cause: The specified broker command was already running and the command issued could not be completed.
Action: Wait for the specified command to finish and then retry the command.
ORA-16611: command aborted at user request
Cause: The command was aborted at the user’s request.
Action: No action required.
ORA-16612: string value too long for attribute “string”
Cause: The string value for the named attribute was too long.
Action: Specify a shorter string value.
ORA-16613: initialization in progress for database
Cause: A request was made to modify the Data Guard broker configuration before the Data Guard broker had completed initialization.
Action: Wait until the Data Guard broker has completed initialization before attempting to modify the broker configuration.
Above are list of Oracle Database Errors or Warnings from Error ORA-16602 to ORA-16613 received while performing certain operation against Oracle Database or related products.
What are Oracle Database Error Messages?
Oracle Error Messages may be returned while using products which are part of Oracle Database. Each Oracle Database Error or Warning Message mentioned above contains the Warning or Error Message Statement, a short explanation of the probable causes of the Error message, and a recommended action.
Hope this was helpful.
Information about Oracle Database Error Messages or Warning Messages on Windows and Linux Operating Systems.