Oracle 11g Error Codes and Solution Suggestions from ORA-16500 to ORA-16600

Posted on by Fatih Acar

Oracle 11g Error Codes and Solution Suggestions from ORA-16500 to ORA-16600

ORA-16501: the Data Guard broker operation failed
Cause: The Data Guard broker operation failed.
Action: See accompanying messages for details.
ORA-16502: the Data Guard broker operation succeeded with warnings
Cause: The Data Guard broker operation succeeded with warnings.
Action: See accompanying messages for details.
ORA-16503: cannot exceed the maximum number of databases in this configuration
Cause: The Data Guard broker configuration already contained the maximum number of databases that could be configured and managed by the broker.
Action: Select and remove an existing database from the broker configuration, then reissue the command to add another database to the configuration. Note that when COMPATIBLE is set lower than 11.2.0.0.0, the broker can configure and manage up to 10 databases. When COMPATIBLE is set to 11.2.0.0.0 or higher, this limit is increased to 31.
ORA-16504: the Data Guard configuration already exists
Cause: A request to create a Data Guard configuration was made while connected to a database that is part of an existing configuration.
Action: To create a new configuration, the existing configuration must be deleted.
ORA-16506: out of memory
Cause: Process exceeded private or shared memory limits.
Action: Check for memory leaks, increase system parameters and restart.
ORA-16509: request timed out
Cause: The Data Guard broker timed out out the request.
Action: Check the Data Guard broker log file for more information. Ensure that the network connections between the databases are functioning properly and retry the request.
ORA-16513: maximum requests exceeded
Cause: The maximum number of requests that the broker can service
Action: Wait for the broker to complete processing the requests before issuing more requests.
ORA-16516: current state is invalid for the attempted operation
Cause: The broker may have returned this error for either switchover operations or for database state change operations. If this error was returned for a switchover operation, the broker determined that either:
– The databases changing roles are shut down.
– The primary database is not shipping redo data.
– The standby database that will become the primary database is not applying redo data. If this error was returned for database state change operations, the database state specified was invalid.
Action: If this error is returned when attempting a switchover operation, make sure that:
– The databases changing roles are started.
– The primary database is shipping redo data.
– The standby database is applying redo data. If this error is returned when attempting a database state change operation, make sure a valid database state is specified.
ORA-16523: operation requires the client to connect to instance “string“
Cause: The switchover or failover operation required the client to connect to the apply instance of the target database.
Action: Connect to the indicated instance and reissue the SWITCHOVER or FAILOVER command.
ORA-16524: unsupported command, option, or argument
Cause: A command, option, or fast-start failover condition argument was specified that is not supported in this release.
Action: If trying to enable or disable a fast-start failover condition, try a different Oracle error number. Otherwise, contact Oracle Support Services.

ORA-16525: the Data Guard broker is not yet available
Cause: The Data Guard broker process was either not yet started, was initializing, or failed to start.
Action: If the broker has not been started, set the DG_BROKER_START initialization parameter to true and allow the broker to finish initializing before making the request. If the broker failed to start, check the Data Guard log for possible errors. Otherwise, retry the operation.
ORA-16526: unable to allocate memory to process request
Cause: The Data Guard broker was unable to allocate memory for a request.
Action: Increase the size of the System Global Area (SGA).
ORA-16527: unable to allocate broker System Global Area (SGA) memory
Cause: The Data Guard broker was unable to allocate memory within the System Global Area (SGA).
Action: Increase the size of the System Global Area (SGA) memory.
ORA-16528: unable to allocate Program Global Area (PGA) memory
Cause: There was insufficient space in Program Global Area (PGA) to allocate memory.
Action: Increase process virtual memory.
ORA-16530: invalid buffer or length
Cause: A NULL buffer or a length of zero was specified.
Action: Correct the command parameters and retry the command.
ORA-16532: Data Guard broker configuration does not exist
Cause: A broker operation was requested that required a broker configuration to already be created.
Action: Create a Data Guard broker configuration prior to performing other broker operations. If only one instance of a RAC database is reporting this error, ensure that the DG_BROKER_CONFIG_FILE[1|2] initialization parameters are set to file locations that are shared by all instances of the RAC database.
ORA-16534: switchover, failover or convert operation in progress
Cause: The Data Guard broker returned this status because a switchover, failover or convert operation was in progress. The broker could not accept new requests until the operation finished.
Action: Wait until the operation is complete and reissue the request.
ORA-16535: Oracle Restart or Oracle Clusterware prevented completion of broker operation
Cause: The broker could not complete the operation because Oracle Restart (for single instance databases) or Oracle Clusterware (for RAC databases) could not stop services or instances on this database.
Action: Check the Data Guard broker log file for more information and stop the appropriate services or instances using SRVCTL. Then retry the broker operation.
ORA-16538: no match on requested item
Cause: The Data Guard broker did not recognize the specified property or state name, or a fast-start failover condition was specified that is not enabled.
Action: Verify command parameters and reissue the request.
ORA-16540: invalid argument
Cause: One of the arguments for the specified request was invalid for the request type.
Action: Verify arguments and then reissue the request.
ORA-16541: database is not enabled
Cause: The database specified in the request was not enabled.
Action: Select an enabled database and reissue the request.
ORA-16544: modifying DG_BROKER_START requires SID=’*’ qualifier
Cause: The setting for the DG_BROKER_START parameter must be exactly the same on all RAC database instances. The SID=’*’ qualifier was required in the command.
Action: Reenter the command using the SID=’*’ qualifier.
ORA-16547: cannot disable or delete the primary database
Cause: An attempt was made to disable broker management of the primary database or delete the primary database from the broker configuration while the configuration was enabled.
Action: If you wish to disable broker management of the primary database when the configuration is enabled, you must instead disable broker management of the entire broker configuration. If you wish to delete the primary database from the broker configuration while the configuration is enabled, you must instead delete the entire broker configuration.
ORA-16548: database not enabled
Cause: An attempt was made to modify or query a disabled database. This error is also returned on an attempt to enable, modify, or query a database that the broker has disabled because of a switchover or failover operation. The broker disables its management of a database when it detects that the database needs to be re-created because of a failover or switchover operation.
Action: If broker management of the database is disabled, enable it and reissue the request.
ORA-16549: invalid string
Cause: An invalid or NULL string value was specified.
Action: Correct command parameters and retry.
ORA-16550: truncated result
Cause: A string property value was truncated due to insufficient buffer size.
Action: Specify a larger receive buffer.
ORA-16551: short string copied
Cause: A string property value that did not fill the receive buffer was placed in the receive buffer.
Action: This is an informational message only.
ORA-16552: error occurred while generating directives for client
Cause: The operation could not be completed because the broker required assistance from the client that it was unable to provide because of the accompanying error.
Action: See the accompanying error message for more information and follow the directions provided in the Action section of that message. Then retry the operation.
ORA-16555: database is not active
Cause: An operation was attempted on a database that was not active. not active.
Action: Verify that the database is active and retry the operation.
ORA-16556: observer version mismatch
Cause: This version of the observer was incompatible with the version of the specified Oracle database server to which the observer had been connected. This observer client cannot be used to observe the specified Oracle server.
Action: Use a version of the observer that is compatible with the Oracle database server to be observed.
ORA-16557: database is already in use
Cause: An attempt was made to create a duplicate database in the broker configuration, or to add a duplicate instance (sid) for an existing database in the broker configuration.
Action: Check the database to be added to ensure there are no duplicates.
ORA-16558: database specified for switchover is not a standby database
Cause: An attempt was made to switchover to a database that was not a standby database.
Action: Locate an enabled standby database and select that database as the target of the switchover.
ORA-16561: cannot remove an active instance
Cause: The instance to be removed was running.
Action: Shut down the instance and reissue the REMOVE command.
ORA-16568: cannot set property string
Cause: The specified property could not be modified because it was either a monitorable property or a property that did not exist.
Action: Retry the command with a valid configurable property.
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-16570: database needs restart
Cause: The Data Guard broker operation required this database instance to be shut down and restarted.
Action: If DGMGRL or Enterprise Manager has not already done so, shut down the Oracle instance and then restart it.
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 file name as indicated by the DG_BROKER_CONFIG_FILE[1|2] initialization parameters and retry the operation.
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] initialization parameters were changed, ensure the file name on disk and the parameter value match, there is space on the device, and the proper permissions are granted. For a RAC database, ensure that these initialization parameters are set to file locations that are shared by all instances of the RAC database.
ORA-16573: attempt to change or access configuration file for an enabled broker configuration
Cause: The operation was rejected because the Data Guard broker configuration file was in use. The attempted operation was unsafe while broker management of the configuration was enabled. For example:
– An attempt was made to alter the DG_BROKER_CONFIG_FILE[1|2] initialization parameters while the broker was running.
– Non-broker access (such as DBMS_FILE_TRANSFER) to the configuration files was attempted. See the alert log for additional information.
Action: Disable the broker configuration and shut down the Data Guard broker, then retry the operation. If the operation includes altering the DG_BROKER_CONFIG_FILE[1|2] initialization parameters, be sure that the new parameter values correctly specify the files at their expected location before reenabling broker management of the configuration.
ORA-16574: switchover disallowed when required databases are shut down
Cause: Switchover failed because either the primary database or the designated standby database were shut down.
Action: Ensure that the primary and standby databases are running and that primary database is shipping redo data to the designated standby database. Also ensure that that the designated standby database is applying the redo data received from the primary database.
ORA-16575: request terminated because failover is in progress
Cause: This error was returned when the broker terminated a request because it was processing a failover command.
Action: Wait for failover to complete and then retry the request.
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 file name as indicated by the DG_BROKER_CONFIG_FILE[1|2] initialization parameters.
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 file name as indicated by the DG_BROKER_CONFIG_FILE[1|2] initialization parameters. Contact Oracle Support Services.
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 file name as indicated by the DG_BROKER_CONFIG_FILE[1|2] initialization parameters.
ORA-16582: cannot change instance-specific property
Cause: An attempt was made to change an instance-specific property for a database that had more than one instance.
Action: Retry the command and identify a specific instance whose property value is to be changed.
ORA-16584: operation cannot be performed on a standby database
Cause: The database specified for the operation was a standby database, or the operation was attempted on a standby database.
Action: Check the database type and retry the operation. If the command must be executed on a primary database, connect to the primary database and retry the operation.
ORA-16585: operation cannot be performed on a primary database
Cause: The database specified for the operation was a primary database, or the operation was attempted on a primary database.
Action: Check the database type and retry the operation. If the command must be executed on a standby database, connect to a standby database and retry the operation.
ORA-16586: cannot change database property with EDIT INSTANCE command
Cause: An attempt was made to change a database property using an EDIT INSTANCE command instead of an EDIT DATABASE command.
Action: Use the EDIT DATABASE command to change database properties.
ORA-16587: ambiguous object specified to Data Guard broker
Cause: An object was specified that the broker could not uniquely distinguish from other objects in the configuration.
Action: Try to further distinguish the object specified for the operation and reissue the command.
ORA-16589: Data Guard broker detected network transfer error
Cause: The Data Guard broker detected an error while transferring data from one database to another. This may happen when:
– the broker detects an inconsistency in the block count of configuration file when the file is transmitted between databases.
– the broker encountered an error when writing the configuration file.
Action: Contact Oracle Support Services.
ORA-16594: DMON background process is not running
Cause: The Data Guard broker background process, DMON, was not running.
Action: Check the Data Guard broker log and DMON process trace file to determine why the DMON process is not running.
ORA-16595: process string failed to terminate
Cause: The specified process did not terminate at the request of the Data Guard broker.
Action: Contact Oracle Support Services.
ORA-16596: database not part of the Data Guard broker configuration
Cause: The specified database is not in the Data Guard broker configuration.
Action: Retry the command with a database that is in the broker configuration.
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 could not continue.
Action: Contact Oracle Support Services.
ORA-16598: Data Guard broker detected a mismatch in configuration
Cause: The Data Guard broker detected a significant mismatch while performing configuration membership validation between two or more databases in the broker configuration. This can occur when the primary database has stale broker configuration files.
Action: Contact Oracle Support Services.
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-16600: not connected to target standby database for failover
Cause: The failover command failed because the client was not connected to the target standby database.
Action: Explicitly connect to the standby database to be failed over to and retry the failover command.

Leave a Reply

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

Time limit is exhausted. Please reload CAPTCHA.