Oracle Database Errors or Warnings from Error ORA-16638 to ORA-16648


ORA-16638: could not get the instance status
Cause: The broker could not determine whether the specified instance was running.
Action: See the next error message in the error stack for more detailed information. If the situation described in the next error in the stack can be corrected, do so; otherwise, contact Oracle Support Services.
ORA-16639: specified instance inactive or currently unavailable
Cause: An attempt was made to perform an operation on an instance that was not running or was unavailable.
Action: Ensure that the instance specified in the operation is running and then retry the operation.
ORA-16640: CRS warns that multiple instances may still be running
Cause: The broker failed to have CRS stop instance monitoring and shut down all but one instance. CRS instance monitoring did stop, but CRS may not have been able to shut down all but one instance. The broker operation was canceled.
Action: Suspend CRS management of this database using SRVCTL STOP DATABASE -D <name> -O NONE. Reissue the broker request.

ORA-16642: DB_UNIQUE_NAME mismatch
Cause: The expected DB_UNIQUE_NAME value did not match the actual DB_UNIQUE_NAME value for the database that the broker contacted using the connect identifier that was associated with that database.
Action: Verify that the connect identifier correctly connects to the intended database. Verify that the name of the database the broker expects to find by that connect identifier matches the actual DB_UNIQUE_NAME for that database.
ORA-16643: unable to determine location of broker configuration files
Cause: The Data Guard broker was unable to determine the location of its configuration files from the DG_BROKER_CONFIG_FILE[1|2] initialization parameters.
Action: Retry the operation and, if the error persists, contact Oracle Support Services.
ORA-16644: apply instance not available
Cause: The broker operation could not finish, because it requires a running apply instance for the standby database, and either there was no such instance designated for the standby database or the designated apply instance was not currently available.
Action: Start the designated apply instance or wait until the broker specifies an instance to be the apply instance and reissue the command.

ORA-16645: unexpected new instance interrupted current operation
Cause: A new instance unexpectedly joined the Data Guard configuration at a point when the current operation may proceed only if the set of known instances is not changing dynamically.
Action: Reissue the operation after the new instance has joined the Data Guard configuration.
ORA-16646: fast-start failover is disabled
Cause: The operation was not allowed because fast-start failover was disabled.
Action: Enable fast-start failover and retry the operation.
ORA-16647: could not start more than one observer
Cause: The observer could not start because there was another observer already observing the Data Guard configuration for which fast-start failover may have been enabled.
Action: Stop the running observer. Retry the operation.
ORA-16648: a new observer registered with identifier string
Cause: The observer was registered with the Data Guard broker and will begin observing the Data Guard configuration for conditions that warrant doing a fast-start failover.
Action: None

Above are list of Oracle Database Errors or Warnings from Error ORA-16638 to ORA-16648 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.

SQLServerF1 Team
Information about Oracle Database Error Messages or Warning Messages on Windows and Linux Operating Systems.


Leave a Reply

Your email address will not be published. Required fields are marked *