Error ora 16810 multiple errors or warnings detected for the database

Oracle 11g Error Codes and Solution Suggestions from ORA-16800 to ORA-17000

ORA-16800: redo transport service for a standby database incorrectly set to ALTERNATE

Cause: The redo transport service for a standby database was set to ALTERNATE when no other destination is set to alternate to this destination.

Action: Reenable the standby database or the entire configuration to allow the configuration property settings to be propagated to the initialization parameters.

ORA-16801: redo transport-related property is inconsistent with database setting

Cause: The values of one or more redo transport-related configuration properties were inconsistent with database in-memory settings or server parameter file settings. This may happen by directly altering initialization parameters instead of editing configurable property values using Data Guard broker.

Action: Query the InconsistentLogXptProps property on the primary database or check the Data Guard broker log to find which properties are set inconsistently. Reset these properties to make them consistent with the database settings. Alternatively, enable the database or the entire configuration to allow the configurable property settings to be propagated to the initialization parameters.

ORA-16802: downgrading redo transport mode from SYNC disallowed

Cause: An attempt was made to downgrade the redo transport mode of a standby database from SYNC to ASYNC when the configuration was in Maximum Protection or Maximum Availability mode and the primary database was a RAC database. This was not disallowed even though there may have been other standby databases with redo transport modes set to SYNC to support the protection mode.

Action: Do one of the following if the redo transport mode of the standby must be downgraded:

– Shut down all instances of the primary database and restart one instance with the initialization parameter CLUSTER_DATABASE set to FALSE. Downgrade the redo transport mode of the standby database of interest. Then, shutdown the instance, set the the CLUSTER_DATABASE initialization parameter to TRUE, and restart all primary database instances.

– Downgrade the protection mode to Maximum Performance mode and then, downgrade the redo transport mode of the standby database of interest. Finally, upgrade the protection mode. This will require a restart of all primary database instances if upgrading to Maximum Protection mode. Note that the above only works when there is at least one standby database in the configuration that has its redo transport mode set to SYNC.

ORA-16803: unable to query a database table or fixed view

Cause: Failed to query a database table or fixed view. The database may not be opened or mounted.

Action: Check the Data Guard broker log for more details.

ORA-16804: one or more configuration properties have invalid values

Cause: Data Guard broker health check detected that one or more configuration properties in the broker configuration had invalid values. The property values were changed while broker management of the database was disabled.

Action: Check Data Guard broker log for more details on which properties have invalid values and reset them through the Data Guard broker.

ORA-16805: change of LogXptMode property violates overall protection mode

Cause: The broker disallowed the attempt to change the LogXptMode configurable property for the standby database because, if allowed, the overall protection mode for the configuration would have been violated.

Action: If the LogXptMode configuration property must be changed for the specified standby database, first downgrade the overall protection mode for the broker configuration. After that operation has completed, the LogXptMode configuration property for the standby database can be changed.

ORA-16806: supplemental logging is not turned on

Cause: Supplemental logging was not turned on while there was a logical standby database in the configuration. This could happen either on the primary database or on the logical standby database that was being switched over to be the primary database.

Action: Check the Data Guard broker log for more details. Issue the ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (PRIMARY KEY, UNIQUE INDEX) COLUMNS to add supplemental logging.

ORA-16807: unable to change database protection mode

Cause: An attempt to issue the ALTER DATABASE SET STANDBY TO MAXIMIZE {PROTECTION | AVAILABILITY | PERFORMANCE} failed.

Action: Check the Data Guard broker log and the Oracle log for more information.

ORA-16808: primary database is not open

Cause: A prior attempt to open the primary database was disallowed because the primary had shut itself down earlier after being isolated from both the fast-start failover observer and the target standby database for more than FastStartFailoverThreshold seconds. It was assumed that a fast-start failover was underway. Since that time, re-contact with either the observer or the target standby database indicates that no such failover had actually occurred. The primary database can now be opened.

Action: Open the database by issuing the SQL*Plus ALTER DATABASE OPEN command.

ORA-16809: multiple warnings detected for the database

Cause: The broker detected multiple warnings for the database.

Action: To get a detailed status report, check the status of the database specified using either Enterprise Manager or the DGMGRL CLI SHOW DATABASE command.

ORA-16810: multiple errors or warnings detected for the database

Cause: The broker detected multiple errors or warnings for the database.

Action: To get a detailed status report, check the status of the database specified using either Enterprise Manager or the DGMGRL CLI SHOW DATABASE command.

ORA-16811: apply instance not recorded by the Data Guard broker

Cause: The broker did not register an apply instance for a standby database.

Action: Reenable the standby database to clear the error.

ORA-16812: log apply service not running on apply instance recorded by the broker

Cause: Log apply services were not running on the instance the Data Guard broker expected them to be running upon.

Action: Reenable the standby database to clear the error.

ORA-16813: log apply service not running on apply instance string recorded by the broker

Cause: Log apply services were not running on the instance the Data Guard broker expected them to be running upon.

Action: Reenable the standby database to clear the error.

ORA-16814: incorrect redo transport setting for AlternateLocation for standby database

Cause: The Data Guard broker detected an incorrect redo transport setting for a standby database AlternateLocation property. The incorrect setting could be one of the following:

– The AlternateLocation property was empty, but the redo transport to the standby database had an ALTERNATE setting.

– The AlternateLocation property was not empty and the redo transport to the standby database had no ALTERNATE setting.

– The AlternateLocation property did not match the ALTERNATE setting in the redo transport. The mismatch may include service string, directory specification of the alternate location, or the DB_UNIQUE_NAME attribute.

– The LOG_ARCHIVE_DEST_STATE_n parameter corresponding to the alternate location was not set to ALTERNATE.

– The flash recovery area was being used by the standby database for archived logs, but the redo transport to the standby database still had an ALTERNATE setting for the AlternateLocation property. Data Guard broker logs provide more details on which of the above cases caused the error.

Action: Reenable the primary database to clear the error.

ORA-16815: incorrect redo transport setting for AlternateLocation for standby database “string“

Cause: The Data Guard broker detected an incorrect redo transport setting for a standby database AlternateLocation property. The incorrect setting could be one of the following:

– The AlternateLocation property was empty, but the redo transport to the standby database had an ALTERNATE setting.

– The AlternateLocation property was not empty and the redo transport to the standby database had no ALTERNATE setting.

– The AlternateLocation property did not match the ALTERNATE setting in the redo transport. The mismatch may include service string, directory specification of the alternate location, or the DB_UNIQUE_NAME attribute.

– The LOG_ARCHIVE_DEST_STATE_n parameter corresponding to the alternate location was not set to ALTERNATE.

– The flash recovery area was being used by the standby database for archived logs, but the redo transport to the standby database still had an ALTERNATE setting for the AlternateLocation property. Data Guard broker logs provide more details on which of the above cases caused the error.

Action: Reenable the primary database to clear the error.

ORA-16816: incorrect database role

Cause: The Data Guard broker detected that the specified database had a different database role than that recorded in the Data Guard broker configuration. This could be the result of a failed switchover or failover operation, or a switchover or failover operation performed with SQL*Plus.

Action: Check the Data Guard broker documentation to see how to recover from failed role change operations, or from role changes that were performed using SQL*Plus for databases managed by Data Guard broker.

ORA-16817: unsynchronized fast-start failover configuration

Cause: The fast-start failover target standby database was not synchronized with the primary database. As a result, a fast-start failover could not happen automatically in case of a primary database failure.

Action: Ensure that the fast-start failover target standby database is running and that the primary database can ship redo data to it. When the standby database has received all of the redo data from the primary database, the primary and standby databases will then be synchronized. The Data Guard configuration may then fail over automatically to the standby database in the event of loss of the primary database.

ORA-16818: fast-start failover suspended

Cause: The primary database was intentionally shutdown. As a result, a fast-start failover could not happen automatically.

Action: Start the primary database. This effectively restores the ability to automatically perform a fast-start failover in the event of a failure of the primary database.

ORA-16819: fast-start failover observer not started

Cause: The observer for fast-start failover was not started. As a result, fast-start failover could not happen in the case of a primary database failure.

Action: Start the fast-start failover observer by using, for example, the DGMGRL START OBSERVER command.

ORA-16820: fast-start failover observer is no longer observing this database

Cause: A previously started observer was no longer actively observing this database. A significant amount of time elapsed since this database last heard from the observer. Possible reasons were:

– The host where the observer was running was not available.

– The network connection between the observer and this database was not available.

– The observer process was terminated unexpectedly.

Action: Check the reason why the observer cannot contact this database. If the problem cannot be corrected, stop the current observer by connecting to the Data Guard configuration and issue the DGMGRL STOP OBSERVER command. Then, restart the observer on another host. Finally, use the DGMGRL START OBSERVER command to start the observer on the other host.

ORA-16821: logical standby database dictionary not yet loaded

Cause: The logical standby database had not loaded the dictionary. This status was detected by the broker health check mechanism. Alternatively, this status may be returned when attempting to switch or fail over to a logical standby database that had not yet loaded its dictionary.

Action: Start SQL Apply on the logical standby database, if it is not already running, and wait for it to reach the APPLYING state.

ORA-16822: new primary database not yet ready for standby database reinstatement

Cause: The new primary database, as a result of a logical standby database failover operation, had not fully completed the failover operation. An attempt to reinstate a disabled standby database could not be completed until failover completed on the new primary database.

Action: Wait until the failover operation has completed on the new primary database. Then retry the reinstate operation.

ORA-16823: redo transport mode is incompatible for current operation

Cause: The redo transport mode of this database was incompatible for this broker operation.

Action: Reset the LogXptMode database property for this database and retry the broker operation.

ORA-16824: multiple warnings, including fast-start failover-related warnings, detected for the database

Cause: The broker detected multiple warnings for the database. At least one of these warnings may have prevented fast-start failover from occurring.

Action: To get a detailed status report, check the status of the database specified using either Enterprise Manager or the DGMGRL CLI SHOW DATABASE command.

ORA-16825: multiple errors or warnings, including fast-start failover-related errors or warnings, detected for the database

Cause: The broker detected multiple errors or warnings for the database. At least one of these errors or warnings may have prevented a fast-start failover from occurring.

Action: To get a detailed status report, check the status of the database specified using either Enterprise Manager or the DGMGRL CLI SHOW DATABASE command.

ORA-16826: apply service state is inconsistent with the DelayMins property

Cause: This warning was caused by one of the following reasons:

– The apply service was started without specifying the real-time apply option or without the NODELAY option when the DelayMins property was set to zero.

– The apply service was started with the real-time apply option or with the NODELAY option when the DelayMins property was set to a value greater than zero.

Action: Reenable the standby database to allow the broker to restart the apply service with the apply options that are consistent with the specified value of the DelayMins property.

ORA-16827: Flashback Database is disabled

Cause: The broker detected that the Flashback Database feature was disabled. With Flashback Database disabled, the broker would not be able to:

– reinstate a database that required reinstatement.

– convert a physical standby database to a snapshot standby database.

– convert a snapshot standby database to a physical standby database. Flashback Database may been disabled manually with the ALTER DATABASE FLASHBACK DATABASE OFF command or automatically by the database in the event of an error.

Action: Check the database alert log to determine whether Flashback Database was disabled due to errors and then correct the problem. If Flashback Database had been manually disabled, reenable Flashback Database with the ALTER DATABASE FLASHBACK DATABASE ON command. If, after enabling Flashback Database, the database still cannot be reinstated or converted, you must re-create the database from a copy of the primary database.

ORA-16828: invalid value specified for REDO_TRANSPORT_USER initialization parameter

Cause: An invalid value was specified for the REDO_TRANSPORT_USER initialization parameter. The length of the user name exceeded 30 characters.

Action: Check the documentation and specify a new value for the REDO_TRANSPORT_USER initialization parameter.

ORA-16829: fast-start failover configuration is lagging

Cause: The fast-start failover target standby database was not within the lag limit specified by the FastStartFailoverLagLimit configuration property. As a result, a fast-start failover could not happen in the event of a primary database failure.

Action: Ensure that the fast-start failover target standby database is running and applying redo data and that the primary database is successfully trasmitting redo data. If this condition persists consider raising the value of the FastStartFailoverLagLimit configuration property.

ORA-16830: primary isolated from fast-start failover partners longer than FastStartFailoverThreshold seconds: shutting down

Cause: The primary database was isolated from both the observer and target standby database for longer than the seconds specified by the FastStartFailoverThreshold property. A fast-start failover probably occurred. If the FastStartFailoverPmyShutdown configuration property was set to TRUE, the broker will shut down the primary database in this situation.

Action: Ensure one instance of this database is running and the database is mounted on that instance so that the broker may reinstate the old primary database.

ORA-16831: operation disallowed on this standby database type

Cause: The Data Guard broker operation was disallowed on the standby database type.

Action: Check the documentation for the correct standby database type and reissue the Data Guard broker command to another standby database that is of the correct standby database type.

ORA-16832: user-configurable fast-start failover initiated: shutting down

Cause: The broker initiated a fast-start failover to the target standby database because a user-configurable condition was detected on the primary database. In addition, the broker shut down the primary database.

Action: Correct the problem on the old primary database that caused the broker to initiate a fast-start failover, then reinstate the old primary database.

ORA-16853: apply lag has exceeded specified threshold

Cause: The current apply lag exceeded the value specified by the ‘ApplyLagThreshold’ database property. It may be caused either by a large transport lag or poor performance of apply services on the standby database.

Action: Check for gaps on the standby database. If no gap is present, tune the apply services.

ORA-16854: apply lag could not be determined

Cause: Apply lag could not be determined because either apply services were not running or there was no connectivity between the redo source and standby database.

Action: Start apply services if they are not running. Also, ensure that there is network connectivity between the redo source and standby databases, and the redo source is sending redo data to the standby.

ORA-16855: transport lag has exceeded specified threshold

Cause: The current transport lag exceeded the value specified by the ‘TransportLagThreshold’ database property. It is caused by either poor network performance between the redo source and the standby databases or a network disconnection.

Action: Check the network connection between the redo source and standby databases. If they are connected, check the network performance between the redo source and the standby databases and tune it if necessary.

ORA-16856: transport lag could not be determined

Cause: Transport lag could not be determined because there was no connectivity between the redo source and standby databases.

Action: Ensure that there is network connectivity between the redo source and standby databases, and the redo source is working properly.

ORA-16857: standby disconnected from redo source for longer than specified threshold

Cause: The amount of time the standby was disconnected from the redo source database exceeded the value specified by the ‘TransportDisconnectedThreshold’ database property. It is caused by no network connectivity between the redo source and the standby databases.

Action: Ensure that there is network connectivity between the redo source and standby databases, and the redo source is working properly.

ORA-16858: last communication time from redo source could not be determined

Cause: The standby database had never been contacted by the redo source.

Action: Ensure that there is network connectivity between the redo source and standby databases, and the redo source is working properly.

ORA-16861: ExternalDestination property requires DB_UNIQUE_NAME attribute

Cause: The value specified for the ExternalDestination property did not contain the DB_UNIQUE_NAME attribute.

Action: Ensure that DB_UNIQUE_NAME is specified as the value for the ExternalDestination property.

ORA-16862: unsupported attribute specified for the ExternalDestination property

Cause: The value specified for the ExternalDestination property contained unsupported attributes.

Action: Ensure that the value specified for the ExternalDestination property does not contain any of these attributes: LOCATION, ALTERNATE, MAX_FAILURE, SYNC, TEMPLATE, MANDATORY, DELAY, NET_TIMEOUT, and VALID_FOR.

ORA-16950: Remote mapped cursors are not supported by this feature.

Cause: This cursor is a remote mapped cursor which could not be processed locally.

Action: Try to process this statement directly on the remote site.

ORA-16951: Too many bind variables supplied for this SQL statement.

Cause: Binding this SQL statement failed because too many bind variables were supplied.

Action: Pass the correct number of bind variables.

ORA-16952: Failed to bind this SQL statement.

Cause: Binding this SQL statement failed.

Action: Check if bind variables for that statement are properly specified.

ORA-16953: Type of SQL statement not supported.

Cause: This type of SQL statement could not be processed.

Action: None

ORA-16954: SQL parse error.

Cause: The specified SQL statement failed to be parsed.

Action: Check if syntax is correct and ensure that this statement can be parsed by the specified user name.

ORA-16955: Unknown error during SQL analyze.

Cause: The specified SQL statement failed to be analyzed.

Action: This is an internal error, please contact Oracle support.

ORA-16956: Only SELECT or DML statements are supported for test execute.

Cause: The specified SQL statement cannot be tested for execute.

Action: None

ORA-16957: SQL Analyze time limit interrupt

Cause: This is an internal error code used indicate that SQL analyze has reached its time limit.

Action: None

ORA-16958: DML statements running parallel are not supported for test execute.

Cause: The specified DML statement cannot be tested for execute because part of it is running parallel.

Action: None

ORA-16959: Statement type has been disabled for SQL Analyze

Cause: The system attempted to analyze a type of statement that was disabled by the current feature.

Action: Try a different feature capable of analyzing this statement type.

ORA-16960: SQL Analyze could not reproduce the desired plan.

Cause: SQL Analyze failed to reproduce a particular plan using an outline.

Action: Check the outline data.

ORA-16961: SQL statement with SQL patch is ignored

Cause: SQL statements with SQL patches are not supported by SQL tuning advisor.

Action: Check the SQL patch information. Rerun SQL repair advisor on that SQL statement for a potential better SQL patch.

ORA-16962: SQL statement attempted to begin an autonomous transaction

Cause: The SQL statement being analyzed attempted to begin an autonomous transaction, which is not supported.

Action: Analyze another statement or remove the autonomous transaction from the current statement.

ORA-16963: The given user or schema is not supported by this feature.

Cause: The SQL statement being analyzed had a parsing user or schema which is not currently supported for SQL Analyze.

Action: Analyze another statement.