Oracle Database Errors or Warnings from Error ORA-16792 to ORA-16801

SQLServerF1

ORA-16792: configurable property value is inconsistent with database setting
Cause: The values of one or more configurable 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 InconsistentProperties property 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 configurable property settings to be propagated to the initialization parameters.
ORA-16793: logical standby database guard is off
Cause: The logical standby database guard was 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-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 command to turn off the guard and verify that Data Guard health check error or warning is cleared.

ORA-16795: the standby database needs to be re-created
Cause: A switchover or failover operation caused this database to require re-creation. The database was marked for re-creation because it was not 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. Once enabled, it is possible to connect to that standby database and manage it with the broker. 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-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 Oracle Net service name specified in DGMGRL CREATE CONFIGURATION or ADD DATABASE command was not one that provides access to the database being added.

– There were no instances running for the database being added.

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 Oracle Net service name provides access to the running instance. Also check the broker log file for additional information. Then, reissue the CREATE CONFIGURATION or ADD DATABASE command.
ORA-16797: database is not using a server parameter file
Cause: The database was not using a server parameter file or the broker was unable to access the server parameter file.
Action: Issue the CREATE SPFILE=’..’ FROM PFILE=’…'” command to create a server parameter file and then restart the database to use it.

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 the Data Guard broker log and the Oracle alert logs to see more details on the reason for the failure.
ORA-16799: Redo Apply is not running
Cause: Either the Data Guard broker metadata indicates that Redo Apply was turned off, or the recovery process, MRP0, was not running. As a result, Redo Apply-related properties could not be set.
Action: Turn on Redo Apply through Data Guard broker and reissue the command to set a Redo Apply-related property.
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.

Above are list of Oracle Database Errors or Warnings from Error ORA-16792 to ORA-16801 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.

Thanks,
SQLServerF1 Team
Information about Oracle Database Error Messages or Warning Messages on Windows and Linux Operating Systems.

 

Leave a Reply

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