ORA-16714: the value of property is inconsistent with the database setting

If you see this ORA-16714 error when checking ODG configuration, check the primary & standby database in DGMGRL and it will show you which property is having the issue.

DGMGRL> show configuration;

Configuration - DG_PROD

  Protection Mode: MaxPerformance
  Members:
  PROD1 - Primary database
    Warning: ORA-16792: configurable property value is inconsistent with database setting

    PROD2 - Physical standby database
      Warning: ORA-16792: configurable property value is inconsistent with database setting

Fast-Start Failover: DISABLED

Configuration Status:
WARNING   (status updated 30 seconds ago)

For example, when I checked mine, I got the same error for both primary and standby databases.

      Warning: ORA-16714: the value of property StandbyArchiveLocation is inconsistent with the database setting
      Warning: ORA-16714: the value of property AlternateLocation is inconsistent with the database setting
DGMGRL> show database verbose "PROD1"

Database - PROD1

  Role:               PRIMARY
  Intended State:     TRANSPORT-ON
  Instance(s):
    PROD
      Warning: ORA-16714: the value of property StandbyArchiveLocation is inconsistent with the database setting
      Warning: ORA-16714: the value of property AlternateLocation is inconsistent with the database setting

  Properties:
    DGConnectIdentifier             = 'PROD1'
    ObserverConnectIdentifier       = ''
    LogXptMode                      = 'ASYNC'
    RedoRoutes                      = ''
    DelayMins                       = '0'
    Binding                         = 'optional'
    MaxFailure                      = '0'
    MaxConnections                  = '1'
    ReopenSecs                      = '300'
    NetTimeout                      = '30'
    RedoCompression                 = 'DISABLE'
    LogShipping                     = 'ON'
    PreferredApplyInstance          = ''
    ApplyInstanceTimeout            = '0'
    ApplyLagThreshold               = '0'
    TransportLagThreshold           = '0'
    TransportDisconnectedThreshold  = '30'
    ApplyParallel                   = 'AUTO'
    StandbyFileManagement           = 'auto'
    ArchiveLagTarget                = '0'
    LogArchiveMaxProcesses          = '4'
    LogArchiveMinSucceedDest        = '1'
    DbFileNameConvert               = ''
    LogFileNameConvert              = ''
    FastStartFailoverTarget         = ''
    InconsistentProperties          = '(monitor)'
    InconsistentLogXptProps         = '(monitor)'
    SendQEntries                    = '(monitor)'
    LogXptStatus                    = '(monitor)'
    RecvQEntries                    = '(monitor)'
    StaticConnectIdentifier         = '(DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=IPC_KEY))(CONNECT_DATA=(SERVICE_NAME=PROD1_DGMGRL)(INSTANCE_NAME=PROD)(SERVER=DEDICATED)))'
    StandbyArchiveLocation          = '/ora_archivelog1/archivelog/'
    AlternateLocation               = ''
    LogArchiveTrace                 = '0'
    LogArchiveFormat                = 'arch_%t_%s_%r.arc'
    TopWaitEvents                   = '(monitor)'

Database Status:
WARNING
DGMGRL> show database verbose "PROD2";

Database - PROD2

  Role:               PHYSICAL STANDBY
  Intended State:     APPLY-ON
  Transport Lag:      0 seconds (computed 0 seconds ago)
  Apply Lag:          0 seconds (computed 0 seconds ago)
  Average Apply Rate: 1.71 MByte/s
  Active Apply Rate:  1.52 MByte/s
  Maximum Apply Rate: 96.09 MByte/s
  Real Time Query:    OFF
  Instance(s):
    PROD
      Warning: ORA-16714: the value of property StandbyArchiveLocation is inconsistent with the database setting
      Warning: ORA-16714: the value of property AlternateLocation is inconsistent with the database setting

  Properties:
    DGConnectIdentifier             = 'PROD2'
    ObserverConnectIdentifier       = ''
    LogXptMode                      = 'ASYNC'
    RedoRoutes                      = ''
    DelayMins                       = '0'
    Binding                         = 'optional'
    MaxFailure                      = '0'
    MaxConnections                  = '1'
    ReopenSecs                      = '300'
    NetTimeout                      = '30'
    RedoCompression                 = 'DISABLE'
    LogShipping                     = 'ON'
    PreferredApplyInstance          = ''
    ApplyInstanceTimeout            = '0'
    ApplyLagThreshold               = '0'
    TransportLagThreshold           = '0'
    TransportDisconnectedThreshold  = '30'
    ApplyParallel                   = 'AUTO'
    StandbyFileManagement           = 'AUTO'
    ArchiveLagTarget                = '0'
    LogArchiveMaxProcesses          = '4'
    LogArchiveMinSucceedDest        = '1'
    DbFileNameConvert               = ''
    LogFileNameConvert              = ''
    FastStartFailoverTarget         = ''
    InconsistentProperties          = '(monitor)'
    InconsistentLogXptProps         = '(monitor)'
    SendQEntries                    = '(monitor)'
    LogXptStatus                    = '(monitor)'
    RecvQEntries                    = '(monitor)'
    StaticConnectIdentifier         = '(DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=IPC_KEY))(CONNECT_DATA=(SERVICE_NAME=PROD2_DGMGRL)(INSTANCE_NAME=PROD)(SERVER=DEDICATED)))'
    StandbyArchiveLocation          = '/ora_archivelog1/archivelog/'
    AlternateLocation               = ''
    LogArchiveTrace                 = '0'
    LogArchiveFormat                = 'arch_%t_%s_%r.arc'
    TopWaitEvents                   = '(monitor)'

Database Status:
WARNING

StandbyArchiveLocation corresponds to LOCATION attribute of the LOG_ARCHIVE_DEST_n initialization parameter of the standby database with VALID_FOR compatible with (STANDBY_ROLE, STANDBY_LOGFILE) DESTINATION column of the V$ARCHIVE_DEST view of the standby database

AlternateLocation corresponds to the LOCATION attribute for the LOG_ARCHIVE_DEST_n initialization parameter that represents an alternate destination of the local destination that matches the configurable database property StandbyArchiveLocation nn the standby database.

In my case, I didn’t find anything wrong with the parameter log_archive_dest_xx. So I disabled the configuration and enabled it again. The problem is gone after that.

My best guess someone touched the parameter and caused the inconsistent state temporarily. The broker could not recover from it and had to disable/enable the configuration to clear the state.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s