Oracle Database Errors or Warnings from Error ORA-16614 to ORA-16626
ORA-16614: Data Guard broker configuration is disabled
Cause: An attempt to enable a database failed because the Data Guard broker configuration was disabled.
Action: Enable the Data Guard broker configuration and issue the DGMGRL CLI SHOW CONFIGURATION command to see if there are any databases that are still disabled. If the database you tried to enable is still disabled, issue the DGMGRL CLI SHOW DATABASE command to check the status of the database. If the database status indicates that the database needs to be reinstated then issue the DGMGRL CLI REINSTATE DATABASE command to reinstate and enable the database. If the database does not require reinstatement then issue the DGMGRL CLI ENABLE DATABASE command to enable the database.
ORA-16617: unknown object identifier specified in request
Cause: Object identifier specified in the request was invalid or unknown.
Action: Verify that a valid object identifier is specified and reissue reissue the request.
ORA-16619: health check timed out
Cause: The standby database could not be reached during a routine health check.
Action: This typically indicates a network problem where the standby database is unable to respond to the primary database within a predefined time frame. Check the network connections between the primary and standby databases.
ORA-16620: one or more databases could not be reached for a delete operation
Cause: One or more standby databases could not be reached for either a DGMGRL CLI REMOVE DATABASE or a REMOVE CONFIGURATION command.
Action: This typically indicates a network problem where the standby database is unable to respond to the primary database. In the event of this situation, examine the primary database Data Guard broker log to determine which standby databases could not be reached. For each standby database not reached, connect to that database and shut down the broker by setting the initialization parameter, DG_BROKER_START, to false. After the broker has been shut down for the standby database, locate the Data Guard broker configuration files from the standby database DG_BROKER_CONFIG_FILE[1|2] initialization parameter values and delete them. Then restart the broker by setting DG_BROKER_START to true.
ORA-16621: database name for ADD DATABASE must be unique
Cause: An attempt was made to add a database to the broker configuration that already included a database with the specified name. The database names must be unique.
Action: Verify that a unique name is specified for the new database to be added. Also, the database name must match the DB_UNIQUE_NAME initialization parameter of the database.
ORA-16622: two or more broker database objects resolve to the same database
Cause: Multiple database objects referred to the same database.
Action: Examine the details of all databases in the broker configuration and verify that there are not two or more databases referring to the same database. If two or more database profiles in the broker configuration have the same value for the DGConnectIdentifier database property, either:
– Remove and re-add the erroneously defined database(s) to resolve the ambiguity.
– Ensure that the DGConnectIdentifier database property for each database allows the broker to properly connect to that database.
ORA-16623: database detected role change
Cause: A successful switchover or failover operation had been completed and was detected during database startup or broker health check. If this database was unavailable during a switchover or failover operation, it may not be a viable standby database for the new primary database and was disabled by the Data Guard broker.
Action: Connect to the new primary database and examine the broker configuration for databases that were disabled and that may require reinstatement or re-creation.
ORA-16624: broker protocol version mismatch detected
Cause: A network protocol version number mismatch was detected. This could happen if the databases in the broker configuration were not running the same version of Oracle. The broker would disable standby databases that were not running the same version of Oracle as the primary database if this situation was detected.
Action: Examine the version of Oracle installed on all databases in the broker configuration to ensure they are identical. Once all of the datbases in the broker configuration are running the same version of Oracle, reenable the standby databases that were disabled.
ORA-16625: cannot reach the database
Cause: The command could not be executed because the database required to complete the command was not reachable from the database where the command was issued. If the command modifies the configuration, the command must be processed by the copy of the broker running on an instance of the primary database.
Action: Check the network connections between all of the databases in the configuration. Alternatively, connect to a different database in the Data Guard broker configuration and retry the command. If an attempt was made to determine the status of a particular database in the configuration, connect to that database and get the current value of the StatusReport property for that database.
ORA-16626: failed to enable specified database
Cause: This status was returned when attempting to enable a standby database that:
– Could not locate itself in the broker configuration file.
– Failed to distinguish itself from two or more databases in the configuration file.
– Determined it missed a role change within the configuration.
Action: To correct the problem, try one of these actions:
– Confirm that the host and SID names for the database exactly match the values in the HOST_NAME and INSTANCE_NAME columns of V$INSTANCE.
– Confirm that there are not two or more databases with the same connect identifier. That is, multiple databases in the broker configuration should not reach the same database.
– If a failover had been performed and the old primary database has been re-created (or a standby database has been re-created), make sure the Data Guard broker configuration files have been removed for that database. Do NOT remove the configuration files that are in use by the new primary database.
Above are list of Oracle Database Errors or Warnings from Error ORA-16614 to ORA-16626 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.