How to resolve ORA-16792
(Doc ID 966472.1)
Last updated on FEBRUARY 14, 2022
Applies to:Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 10.2.0.1 to 220.127.116.11 [Release 10.2 to 12.1]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
** checked for relevance '23-Nov-2015' **
NOTE: In the images and/or the document content below, the user information and environment data used represents
fictitious data from the Oracle sample schema(s), Public Documentation delivered with an Oracle database product or
other training material. Any similarity to actual environments, actual persons, living or dead, is purely coincidental and
not intended in any manner.
For the purposes of this document, the following fictitious environment is used as an example to describe the procedure:
Primary: DB Name: DGA24L
Standby: DB Unique Name: DGA24LPS
If the setting of dataguard related parameter is different between database and the broker, when doing the show configuration within DGMGRL, the following error will appear:
Protection Mode: MaxPerformance
Fast-Start Failover: DISABLED
DGA24L - Primary database
DGA24LPS - Physical standby database
Current status for "DGA24L":
Warning: ORA-16608: one or more databases have warnings
When showing the database in verbose:
Intended State: ONLINE
LogXptMode = 'ARCH'
Dependency = ''
DelayMins = '0'
Binding = 'OPTIONAL'
StatusReport = '(monitor)'
InconsistentProperties = '(monitor)'
InconsistentLogXptProps = '(monitor)'
AlternateLocation = ''
LogArchiveTrace = '513'
LogArchiveFormat = '%t_%s_%r.dbf'
LsbyMaxSga = '0'
LsbyMaxServers = '0'
LatestLog = '(monitor)'
TopWaitEvents = '(monitor)'
Current status for "DGA24L":
Warning: ORA-16792: configuration property value is inconsistent with database setting
16792, 0000, "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.
There can also be ORA-16714 reported which has the same Cause and Fix:
ORA-16714: the value of property string is inconsistent with the database setting
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document