How to resolve ORA-16792

(Doc ID 966472.1)

Last updated on OCTOBER 12, 2016

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.1 to 12.1.0.2 [Release 10.2 to 12.1]
Information in this document applies to any platform.
***Checked for relevance on 30-SEPT-2012***
***Checked for relevance on 5-Aug-2014***
** checked for relevance '23-Nov-2015' **

Goal

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:

DGMGRL> show configuration;

Configuration
Name: DGA24L
Enabled: YES
Protection Mode: MaxPerformance
Fast-Start Failover: DISABLED
Databases:
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:

DGMGRL> show database verbose 'DGA24L';

Database
Name: DGA24L
Role: PRIMARY
Enabled: YES
Intended State: ONLINE
Instance(s):
DGA24L

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

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms