Oracle Error Messages: 03/30/12

Friday, 30 March 2012

ORA-16955: Unknown error during SQL analyze.

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-16954: SQL parse error.

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-16953: Type of SQL statement not supported.

ORA-16953: Type of SQL statement not supported.

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

Action: none

ORA-16952: Failed to bind this SQL statement.

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-16951: Too many bind variables supplied for this SQL statement.

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-16950: Remote mapped cursors are not supported by this feature.

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-16826: apply service state is inconsistent with the DelayMins property

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

Cause: This warning was caused by one of the following reasons: 1. Apply service was started without specifying the real time apply option or without the NODELAY option while DelayMins is zero. 2. Apply service was started with the real-time apply option or with the NODELAY option while DelayMins is 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-16825: Fast-Start Failover and other errors or warnings detected for the database

ORA-16825: Fast-Start Failover and other errors or warnings detected for the database

Cause: The broker has detected multiple errors or warnings for the database. At least one of the detected errors or warnings may prevent a Fast-Start Failover from occurring.

Action: Check the StatusReport monitorable property of the database specified.

ORA-16824: Fast-Start Failover and other warnings detected for the database

ORA-16824: Fast-Start Failover and other warnings detected for the database

Cause: The broker has detected multiple warnings for the database. At least one of the detected warnings may prevent a Fast-Start Failover from occurring.

Action: Check the StatusReport monitorable property of the database specified.

ORA-16823: redo transport mode is incompatible for current 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-16822: new primary database not yet ready for standby database reinstatement

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

Cause: The new primary database, as a result of a logical failover operation, had not fully completed the failover steps. Subsequent reinstatement operations could not proceed until failover has completed on the new primary database.

Action: Wait until the completion of all failover steps on this new primary database and then retry the reinstate operation.

ORA-16821: logical standby database dictionary not yet loaded

ORA-16821: logical standby database dictionary not yet loaded

Cause: Logical standby apply had not finished loading the dictionary. This warning is flagged by the broker s health check mechanism. This error is also flagged by failover and switchover if the target standby database has not loaded its dictionary.

Action: Start SQL Apply on the logical standby database and wait for it to reach the APPLYING state.

ORA-16820: Fast-Start Failover observer is no longer observing this database

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: available.

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 node. You may use the DGMGRL START OBSERVER command to start the observer on the other node.

ORA-16819: Fast-Start Failover observer not started

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-16818: Fast-Start Failover suspended

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 up the primary database. This effectively restores the ability to automatically do a Fast-Start Failover in the event of a failure of the primary database.

ORA-16817: unsynchronized Fast-Start Failover configuration

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 logs to it. When the standby database has received all of the redo logs from the primary database, the primary and standby databases will then be synchronized. The Data Guard configuration may then failover automatically to the standby database in the event of loss of the primary database.

ORA-16816: incorrect database role

ORA-16816: incorrect database role

Cause: The Data Guard broker detected that this database object had a database role that was different from the recorded database role in the Data Guard Configuration. This could be the result of a failed switchover or failover operation, or an out-of-band switchover or failover operation done to the database.

Action: Manually fix the database to convert it to the appropriate database role, then issue an ENABLE DATABASE command to reenable the database object.

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

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

Cause: The Data Guard broker detected that the redo transport setting for the standby database regarding its AlternateLocation property value is incorrect. The incorrect setting could be one of the following: (1) the AlternateLocation property is empty but the log transport to the standby database has an ALTERNATE setting; (2) the AlternateLocation property is not empty but the log transport to the standby database has no ALTERNATE setting; (3) the AlternateLocation property does 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; (4) the log_archive_dest_state_n parameter corresponding to the alternate location is not set to ALTERNATE; (5) the flash recovery area is being used by the standby database for archived logs, but the redo transport to the standby database still has an ALTERNATE setting for the AlternateLocation. Data Guard broker logs provide more details on which of the above cases causes the error.

Action: Reenable the primary database to clear the error.

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

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

Cause: The Data Guard broker detected that an incorrect redo transport setting for a standby database s AlternateLocation property. The incorrect setting could be one of the following: one of the following: (1) the AlternateLocation property is empty but the log transport to the standby database has an ALTERNATE setting; (2) the AlternateLocation property is not empty but the log transport to the standby database has no ALTERNATE setting; (3) the AlternateLocation property does 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; (4) the log_archive_dest_state_n parameter corresponding to the alternate location is not set to ALTERNATE; (5) the flash recovery area is being used by the standby database for archived logs, but the redo transport to the standby database still has an ALTERNATE setting for the AlternateLocation. Data Guard broker logs provide more details on which of the above cases causes the error.

Action: Reenable the primary database to clear the error.

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

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

Cause: Log apply services are not running on the apply instance the Data Guard Broker expects them to be running upon.

Action: Reenable the standby database to clear the error.

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

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

Cause: Log apply services are not running on the apply instance the Data Guard Broker expects them to be running upon.

Action: Reenable the standby database to clear the error.

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

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

Cause: The broker has not registered an apply instance for a standby database.

Action: Reenable the standby database to clear the error.

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

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

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

Action: Check the StatusReport monitorable property of the database specified.

ORA-16809: multiple warnings detected for the database

ORA-16809: multiple warnings detected for the database

Cause: The broker has detected multiple warnings for the database.

Action: Check the StatusReport monitorable property of the database specified.

ORA-16808: unable to resolve the full path name

ORA-16808: unable to resolve the full path name

Cause: An attempt to resolve the full path name from a string failed.

Action: Check the Data Guard broker log for the full error stack. This likely the result of an operating system error.

ORA-16807: unable to change database protection mode

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 Oracle alert log and Data Guard broker log for more information.

ORA-16806: supplemental logging is not turned on

ORA-16806: supplemental logging is not turned on

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

Action: Check 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-16805: change of LogXptMode property violates overall protection mode

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

Cause: The standby database resource guard rejected the attempt to change the LogXptMode configuration property for the standby database. The rejection was necessary to avoid violating the overall protection mode for the configuration.

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, you will be able to change the LogXptMode configuration property for the standby database.

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

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

Cause: Data Guard broker health check detected that one or more configuration properties in the broker s configuration metadata have invalid values. The property values have been changed while broker management of the database is 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-16803: unable to query a database table or fixed view

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 open or mounted.

Action: Check Data Guard broker log for more details.

ORA-16802: downgrading redo transport mode from SYNC disallowed

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 or ARCH when the configuration was in Maximum Protection or Maximum Availability mode and the primary database was a RAC database. This is not allowed, even if there are other standby databases with log transport modes set to SYNC to support the data protection mode.

Action: You can do one of the following if you need to downgrade the redo transport mode of the standby database: (1) Shut down all instances of the primary database and restart one instance with initialization parameter CLUSTER_DATABASE set to FALSE. Downgrade the redo transport mode, shutdown the instance, and restart all instances with CLUSTER_DATABASE set to TRUE. (2) Downgrade the protection mode to Maximum Performance mode first. Then downgrade the redo transport mode, then upgrade the protection mode again (which involves a shutdown and restart of the primary database). Note that the above only works when there exists at least one more standby database in the configuration that has the log transport mode set to SYNC.

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

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 altering initialization parameters directly instead of altering property values using Data Guard broker.

Action: Query property the InconsistentLogXptProps 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 configuration property settings to be propagated to to the initialization parameters.

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

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

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

Action: Reset the database state to turn on redo transport again if necessary.

ORA-16799: Redo Apply is offline

ORA-16799: Redo Apply is offline

Cause: Either the Data Guard broker metadata indicates that Redo Apply is turned off, or the recovery process, MRP0, is not running. In either of the cases, Redo Apply-related properties cannot be set.

Action: Turn on Redo Apply through Data Guard broker and reissue the command to set a Redo Apply-related property.

ORA-16798: unable to complete terminal recovery on the standby database

ORA-16798: unable to complete terminal recovery on the standby database

Cause: Terminal recovery on the standby database failed during the failover operation.

Action: Check Data Guard broker log and alert logs to see more details on the reason of the failure.

ORA-16797: database is not using a server parameter file

ORA-16797: database is not using a server parameter file

Cause: The database is not using a server parameter file or the resource guard was unable to access the server parameter file.

Action: Issue CREATE SPFILE= .. FROM PFILE= ... command to create a server parameter file and then restart the database to use it.

ORA-16796: one or more properties could not be imported from the database

ORA-16796: one or more properties could not be imported from the database

Cause: The broker was unable to import property values for the database being added to the broker configuration. This error indicates: - the net-service-name specified in DGMGRL s CREATE CONFIGURATION or ADD DATABASE command is not one that provides access to the database being added, or

Action: Remove the database from the configuration using the REMOVE CONFIGURATION or REMOVE DATABASE command. Make sure that the database to be added has at least one instance running and that the net-service-name provides access to the running instance. Then reissue the CREATE CONFIGURATION or ADD DATABASE command.

ORA-16795: database resource guard detects that database re-creation is required

ORA-16795: database resource guard detects that database re-creation is required

Cause: In the act of failover or switchover, the database resource guard may have detected that re-creation of the database is necessary. This occurs when the database resource guard recognizes a situation in which the database in question cannot be a viable standby database for the new primary database. Until this error status is resolved for this database, information about this database and the broker configuration to which it belongs is unavailable to a broker client that is connected to this database. Therefore, all commands directed by that client to this database cannot be completed.

Action: Re-create (or flash back) the standby database. Connect to the primary database in the broker configuration and reenable broker management of that database. At this point you may connect to that standby database and resume issuing client commands. Alternatively, many client commands that cannot be completed at the standby database when in this error state can be completed successfully when issued to the primary database. In this case, simply reconnect to the primary database and retry the command.

ORA-16794: database guard is on for primary database

ORA-16794: database guard is on for primary database

Cause: The database guard was turned on for the primary database.

Action: Issue the ALTER DATABASE GUARD NONE to turn off the guard and verify that Data Guard health check error or warning is cleared.

ORA-16793: logical standby database guard is unexpectedly off

ORA-16793: logical standby database guard is unexpectedly off

Cause: The logical standby database guard was unexpectedly turned off.

Action: Issue the ALTER DATABASE GUARD ALL command to turn the guard on and verify that Data Guard health check error or warning is cleared.

ORA-16792: configuration property value is inconsistent with database setting

ORA-16792: configuration property value is inconsistent with database setting

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

Action: Query property the InconsistentProperties on the 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 configuration property settings to be propagated to to the initialization parameters.

ORA-16791: unable to check the existence of the standby redo logs

ORA-16791: unable to check the existence of the standby redo logs

Cause: The database may not be mounted, or the query of V$STANDBY_LOG failed.

Action: Bring the database to the mounted state and then query V$STANDBY_ LOG to see if the problem has been corrected. Then retry the operation.

ORA-16790: the value of the configurable property is invalid

ORA-16790: the value of the configurable property is invalid

Cause: User entered an invalid property value.

Action: Reset the property to a correct value.

ORA-16789: missing standby redo logs

ORA-16789: missing standby redo logs

Cause: Standby redo logs are missing and are needed for SYNC and ASYNC log transport modes.

Action: Check the Data Guard documentation to see how to create standby redo logs.

ORA-16788: unable to set one or more database configuration property values

ORA-16788: unable to set one or more database configuration property values

Cause: This situation occurs when the database resource guard attempted to set database configuration property values into the database by issuing ALTER SYSTEM or ALTER DATABASE commands. Typical causes of this error are: a) The values of redo transport-related properties have syntax errors; b) The Value of LogArchiveTrace is out of range; c) Database initialization parameter STANDBY_ FILE_MANAGEMENT cannot be set to AUTO because the database compatability is not set to 9.0.0.0.0 or higher.

Action: Check the Data Guard broker log to see which property has the problem and reset the property correctly.

ORA-16786: resource guard cannot access Data Guard broker metadata

ORA-16786: resource guard cannot access Data Guard broker metadata

Cause: The Data Guard broker configuration files did not exist or for some other reason the resource guard could not access the Data Guard broker configuration metadata.

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

ORA-16785: the database is not in ARCHIVELOG mode

ORA-16785: the database is not in ARCHIVELOG mode

Cause: The database is in NOARCHIVELOG mode, when it is either a primary database or a standby database that is being switched over to be a primary database.

Action: Reset the database to ARCHIVELOG mode by issuing ALTER DATABASE ARCHIVELOG command.

ORA-16784: the database name in Dependency property is incorrect

ORA-16784: the database name in Dependency property is incorrect

Cause: The database name, which should be the value of the DB_UNIQUE_ NAME initialization parameter, specified in property Dependency is incorrect.

Action: Reset the Dependency property to the correct name of the database.

ORA-16783: instance string not open for read and write access

ORA-16783: instance string not open for read and write access

Cause: The instance was left in a mounted mode and was not open for read and write access.

Action: Open the instance manually or by reenabling the database through the Data Guard broker.

ORA-16782: instance not open for read and write access

ORA-16782: instance not open for read and write access

Cause: An instance was left in a mounted mode and was not open for read and write access.

Action: Query the StatusReport property for more details. Open the instance manually or by reenabling the database through the Data Guard broker.

ORA-16781: the status of redo transport service for a database is unknown

ORA-16781: the status of redo transport service for a database is unknown

Cause: The redo transport service status to a standby database could not be determined.

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

ORA-16780: a database has exhausted its archived redo log storage quota

ORA-16780: a database has exhausted its archived redo log storage quota

Cause: A database has exhausted its quota for storing archived redo logs.

Action: Check the Data Guard broker log to see which database has the problem. Remove some archived logs at the standby database or increase its quota.

ORA-16779: the destination parameter of a database is set incorrectly

ORA-16779: the destination parameter of a database is set incorrectly

Cause: The destination was defined in the LOG_ARCHIVE_DEST_n server parameter file with incorrect syntax. The Data Guard broker failed to update the destination when the redo transport was turned on.

Action: Check the Data Guard broker log to see which database has the problem. Fix the syntax error in the server parameter file or remove the entry from the server parameter file. Check if the syntax of the redo transport-related properties are correct.

ORA-16778: redo transport error for one or more databases

ORA-16778: redo transport error for one or more databases

Cause: The redo transport service was unable to send redo data to one or more standby databases.

Action: Check the Data Guard broker log and Oracle alert log for more details. Query the LogXptStatus property to see the errors.

ORA-16777: unable to find the destination entry of a standby database in V$ARCHIVE_DEST

ORA-16777: unable to find the destination entry of a standby database in V$ARCHIVE_DEST

Cause: Either a destination was manually deleted or no entry was available for Data Guard.

Action: Check the Data Guard broker log and the Oracle alert log for more details. The redo transport service may need to be reset.

ORA-16776: health check of the redo transport service failed

ORA-16776: health check of the redo transport service failed

Cause: Due to some internal failure, the database resource guard could not complete the health check of the redo transport service.

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

ORA-16775: target standby database in broker operation has potential data loss

ORA-16775: target standby database in broker operation has potential data loss

Cause: The target standby database in the broker operation did not have all the redo logs from the primary database. The switchover or protection mode upgrade to maximum protection could not be performed.

Action: Query the SendQEntries monitorable property on the primary database to see which redo logs are missing. Confirm that the redo transport service on the primary database is functioning correctly by checking its status using the StatusReport monitorable property. Perform log switches on the primary database in order to activate the redo log gap fetching mechanism. Once all redo logs are available on the target standby database, reissue the broker command.