Oracle Error Messages: 03/27/12

Tuesday 27 March 2012

ORA-16608: one or more databases have warnings

ORA-16608: one or more databases have warnings

Cause: The Data Guard broker detected a warning status for one or more databases.

Action: Locate the database(s) with a warning status and correct it.

ORA-16607: one or more databases have failed

ORA-16607: one or more databases have failed

Cause: The Data Guard broker detected a failure for one or more databases in the Data Guard configuration.

Action: Locate the database(s) with a failure status and correct it.

ORA-16606: unable to find property string

ORA-16606: unable to find property string

Cause: The named property does not exist.

Action: Specify a valid property name and reissue the request.

ORA-16605: unable to delete template, template is in use

ORA-16605: unable to delete template, template is in use

Cause: The Data Guard broker was unable to delete the template because the template is still being used by one or more resources.

Action: Delete all resources using the template before deleting the template. You cannot delete the database template.

ORA-16604: unable to describe template using package string

ORA-16604: unable to describe template using package string

Cause: The Data Guard broker was unable to execute the OnDescribe function in the named package.

Action: Verify that the named package is loaded on the primary database. Also verify that the OnDescribe function is in the package.

ORA-16603: Data Guard broker detected a mismatch in configuration ID

ORA-16603: Data Guard broker detected a mismatch in configuration ID

Cause: The Data Guard broker for this database detected a mismatch in configuration Unique ID. This can occur if the original configuration was recreated while this database was disconnected from the network or the same database was added to two different broker configurations.

Action: Make sure the database belongs to only one broker configuration. Remove the Data Guard broker configuration files and restart the broker.

ORA-16602: object must be disabled to perform this operation

ORA-16602: object must be disabled to perform this operation

Cause: An attempt was made to edit a database object that can only be done while broker management of that database is disabled.

Action: Disable broker management of the database and reissue the request.

ORA-16601: site contains required resources that are disabled

ORA-16601: site contains required resources that are disabled

Cause: The Data Guard broker detected disabled, required resources prior to performing an operation that needs those resources to be enabled.

Action: Enable all required resources and reissue the request.

ORA-16600: failover operation can only be submitted at target database

ORA-16600: failover operation can only be submitted at target database

Cause: This error is returned when a failover request specified a different database than the database to which the client is currently connected.

Action: Explicitly connect to the database to which you wish to failover and reissue the failover request.

ORA-16599: Data Guard broker detected a stale configuration

ORA-16599: Data Guard broker detected a stale configuration

Cause: The Data Guard broker detected a stale configuration during initialization for this database.

Action: The broker will automatically resolve this situation once the primary database completes its initialization.

ORA-16598: Data Guard broker detected a mismatch in configuration

ORA-16598: Data Guard broker detected a mismatch in configuration

Cause: The Data Guard broker detected a significant mismatch in configuration validation between two or more databases in the broker configuration. This can occur when the primary database has a stale broker configuration file.

Action: Contact Oracle Support Services.

ORA-16597: Data Guard broker detects two or more primary databases

ORA-16597: Data Guard broker detects two or more primary databases

Cause: The Data Guard broker detected two or more primary databases in the broker configuration and cannot continue.

Action: Contact Oracle Support Services.

ORA-16596: object not part of the Data Guard broker configuration

ORA-16596: object not part of the Data Guard broker configuration

Cause: A request was made on a database object that is not in the Data Guard broker configuration. The request cannot be completed.

Action: Reissue the request on a database object that is in the broker configuration.

ORA-16595: NetSlave process string failed to terminate

ORA-16595: NetSlave process string failed to terminate

Cause: The specified NetSlave process did not terminate at the request of the Data Guard broker.

Action: Contact Oracle Support Services.

ORA-16594: %s process discovered that DMON process does not exist

ORA-16594: %s process discovered that DMON process does not exist

Cause: The Data Guard broker process (DMON) that was expected to be running on this instance was found to be missing by the Data Guard NetSlave (NSV*) process(es).

Action: Check the Data Guard broker log and DMON process trace file to determine why the DMON process is missing.

ORA-16593: XML conversion failed

ORA-16593: XML conversion failed

Cause: There was an error in the XML request document

Action: Correct the errors and submit the request again.

ORA-16592: missing field string in document

ORA-16592: missing field string in document

Cause: There was an error at the given token.

Action: Correct the errors and submit the request again.

ORA-16591: unknown field string in document

ORA-16591: unknown field string in document

Cause: There was an error at the given token.

Action: Correct the errors and submit the request again.

ORA-16590: Data Guard configuration does not contain a primary database

ORA-16590: Data Guard configuration does not contain a primary database

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16589: Data Guard Connection process detected a network transfer error

ORA-16589: Data Guard Connection process detected a network transfer error

Cause: The Data Guard Connection process (DRCX) detected an error while transferring data from one database to another. This error is returned in the following situations: inconsistency in the block count of the file.

Action: Contact Oracle Support Services.

ORA-16588: no more internal buffers

ORA-16588: no more internal buffers

Cause: See trace file.

Action: Contact Oracle Support Services.

ORA-16587: ambiguous object specified to Data Guard broker

ORA-16587: ambiguous object specified to Data Guard broker

Cause: The request specified an object that the broker could not uniquely distinguish between other objects in the configuration.

Action: Try to further distinguish the object specified for the operation and reissue the request.

ORA-16586: could not edit database property through instance

ORA-16586: could not edit database property through instance

Cause: The request intended to change a database property but specified an instance.

Action: Specify the database instead to change the database property.

ORA-16585: illegal operation on a primary site

ORA-16585: illegal operation on a primary site

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16584: illegal operation on a standby site

ORA-16584: illegal operation on a standby site

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16583: bad Data Guard Connection Process DRCX state

ORA-16583: bad Data Guard Connection Process DRCX state

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16582: could not edit instance specific property

ORA-16582: could not edit instance specific property

Cause: The request intended to change an instance specific property, but specified a database with two or more instances.

Action: Specify a specific instance instead to change the property value.

ORA-16581: Data Guard NetSlave failed to send message to DRCX

ORA-16581: Data Guard NetSlave failed to send message to DRCX

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16580: bad Data Guard NetSlave network link

ORA-16580: bad Data Guard NetSlave network link

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16579: bad Data Guard NetSlave state detected

ORA-16579: bad Data Guard NetSlave state detected

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16578: failed to read Data Guard configuration file

ORA-16578: failed to read Data Guard configuration file

Cause: A failure was encountered while the broker was reading the configuration file on permanent storage.

Action: Verify space, permissions and filename as indicated by the dg_broker_ config_file(1|2( parameters.

ORA-16577: corruption detected in Data Guard configuration file

ORA-16577: corruption detected in Data Guard configuration file

Cause: The Data Guard broker detected errors while loading the configuration file.

Action: Verify space, permissions and filename as indicated by the dg_broker_ config_file(1|2( parameters. Contact Oracle Support Services.

ORA-16576: failed to update Data Guard configuration file

ORA-16576: failed to update Data Guard configuration file

Cause: A failure was encountered while the broker was updating the Data Guard broker configuration file on permanent storage.

Action: Verify space, permissions and filename as indicated by the dg_broker_ config_file(1|2( parameters.

ORA-16575: request terminated at broker discretion

ORA-16575: request terminated at broker discretion

Cause: This status is returned when the broker terminates a user- initiated request. The broker will terminate all other current and pending requests when it begins processing a failover request. These other requests are terminated with this status.

Action: There is no action to be taken.

ORA-16574: switchover disallowed when required databases are offline

ORA-16574: switchover disallowed when required databases are offline

Cause: Switchover failed because the primary database and or or the designated standby database are offline.

Action: Check the states of the broker configuration, primary database and standby database. Set their states to ONLINE if necessary.

ORA-16573: attempt to change configuration file for an enabled broker configuration

ORA-16573: attempt to change configuration file for an enabled broker configuration

Cause: The Data Guard broker configuration file parameter was currently in use because broker management of the configuration was enabled. The attempt to alter that parameter was rejected.

Action: Disable the configuration and shut down the Data Guard broker before changing this value. Be sure to rename the configuration file at the OS level to match the new value before reenabling broker management of the configuration.

ORA-16572: Data Guard configuration file not found

ORA-16572: Data Guard configuration file not found

Cause: The Data Guard broker configuration file was either unavailable or did not exist.

Action: Verify that the configuration file was successfully created. If the dg_ broker_config_file(1|2( parameter was changed, ensure the filename on disk and the parameter value match, there is space on the device, and you have the right permissions.

ORA-16571: Data Guard configuration file creation failure

ORA-16571: Data Guard configuration file creation failure

Cause: The Data Guard broker was unable to create the configuration file on permanent storage.

Action: Verify space, permissions and filename as indicated by the dg_broker_ config_file(1|2( parameters and retry.

ORA-16570: operation requires restart of database string

ORA-16570: operation requires restart of database string

Cause: The Data Guard broker operation required a database to be shutdown and restarted.

Action: If DGMGRL or Enterprise Manager has not already done so, shutdown the Oracle instance and then restart it.

ORA-16569: Data Guard configuration is not enabled

ORA-16569: Data Guard configuration is not enabled

Cause: The requested operation required that broker management of the Data Guard configuration must be enabled.

Action: Enable the Data Guard configuration and reissue the request.

ORA-16568: cannot set property string

ORA-16568: cannot set property string

Cause: The named property could not be modified. The property may not be editable or may not exist.

Action: Retry the operation with a valid property.

ORA-16567: Data Guard broker internal parser error at string

ORA-16567: Data Guard broker internal parser error at string

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16566: unsupported document type

ORA-16566: unsupported document type

Cause: The XML document submitted is not supported.

Action: Correct the errors and submit the request again.

ORA-16565: duplicate property, syntax error at string

ORA-16565: duplicate property, syntax error at string

Cause: There was an error at the given token.

Action: Correct the errors and submit the request again.

ORA-16564: lookup failed, syntax error at string

ORA-16564: lookup failed, syntax error at string

Cause: There was an error at the given token.

Action: Correct the errors and submit the request again.

ORA-16563: unable to add value, syntax error at string

ORA-16563: unable to add value, syntax error at string

Cause: There was an error at the given token.

Action: Correct the errors and submit the request again.

ORA-16562: intended_state not used here, syntax error at string

ORA-16562: intended_state not used here, syntax error at string

Cause: There was an error at the given token.

Action: Correct the errors and submit the request again.

ORA-16561: cannot remove an active instance

ORA-16561: cannot remove an active instance

Cause: The instance to be removed is currently running.

Action: Shut down the instance and reissue the REMOVE command.

ORA-16560: unable to convert document, syntax error at string

ORA-16560: unable to convert document, syntax error at string

Cause: There was an error at the given token.

Action: Correct the errors and submit the request again.

ORA-16559: out of memory at string

ORA-16559: out of memory at string

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16558: the database specified for switchover is not a standby database

ORA-16558: the database specified for switchover is not a standby database

Cause: An attempt was made to switchover to a database that is not a standby database.

Action: Locate an enabled standby database and select that database as the target of the switchover.

ORA-16557: the database is already in use

ORA-16557: the database is already in use

Cause: An attempt was made to create a duplicate database in the broker configuration.

Action: Check the database to be added and be sure there are no duplicates.

ORA-16556: error message is in XML already

ORA-16556: error message is in XML already

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16555: the Data Guard database is not active

ORA-16555: the Data Guard database is not active

Cause: An operation was attempted on a database that is currently not active (off path).

Action: Verify that the database is active.

ORA-16554: translation not valid

ORA-16554: translation not valid

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16553: the Data Guard broker process (DMON) failed to shutdown

ORA-16553: the Data Guard broker process (DMON) failed to shutdown

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16552: an error occurred when generating the CLIENT OPERATION table

ORA-16552: an error occurred when generating the CLIENT OPERATION table

Cause: An error occurred while Data Guard broker was generating the CLIENT OPERATION table.

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 Customer Support.