Resolving ORA-16714 / ORA-16792

Problem: In an environment, where Data Guard Broker is configured, parameter MAX_EVENTS_RECORDED is changed using SQL*Plus

ALTER DATABASE STOP LOGICAL STANDBY APPLY;
EXECUTE DBMS_LOGSTDBY.APPLY_SET (‘MAX_EVENTS_RECORDED’, ‘5000’);
ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE;

On the primary database, we see following error

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

Generic error for similar issues is

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

To avoid this problem, we should be setting this parameter by using the DGMGRL

In this specific example,

DGMGRL> EDIT DATABASE “TESTDB” SET PROPERTY LsbyMaxEventsRecorded=5000;

We’ll see something like following in the drcTESTDB1.log

DG 2008-02-27-11:23:08 0 2 0 Dumping property lsbymaxeventsrecorded
DG 2008-02-27-11:23:08 0 2 0 Property type CONFIGURABLE, Value type INT
DG 2008-02-27-11:23:08 0 2 0 Value = 5000
DG 2008-02-27-11:23:08 0 2 0 RSM setLProp: stop Apply engine
DG 2008-02-27-11:23:08 0 2 0 Executing SQL [alter database stop logical standby apply]
DG 2008-02-27-11:23:12 0 2 0 SQL [alter database stop logical standby apply] Executed successfully
DG 2008-02-27-11:23:12 0 2 0 RSM Logical Apply Engine: (rfrlawad) epscn is NULL
DG 2008-02-27-11:23:12 0 2 0 RSM Logical Apply Engine: Wait for apply engine to shutdown..
DG 2008-02-27-11:23:12 0 2 0 RSM Logical Apply Engine: Apply offline already! status=1
DG 2008-02-27-11:23:12 0 2 0 RSM setLProp: executing [begin dbms_logstdby.apply_set (‘MAX_EVENTS_RECORDED’,5000); end;]
DG 2008-02-27-11:23:12 0 2 0 Executing SQL [begin dbms_logstdby.apply_set (‘MAX_EVENTS_RECORDED’,5000); end;]
DG 2008-02-27-11:23:12 0 2 0 SQL [begin dbms_logstdby.apply_set(‘MAX_EVENTS_RECORDED’,5000); end;] Executed successfully
DG 2008-02-27-11:23:12 0 2 0 RSM setLProp: restart Apply engine
DG 2008-02-27-11:23:12 0 2 0 RSM Logical Apply Engine: Starting.. [ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE]
DG 2008-02-27-11:23:12 0 2 0 Executing SQL [ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE]
DG 2008-02-27-11:23:12 0 2 0 SQL [ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE] Executed successfully
DG 2008-02-27-11:23:12 0 2 0 RSM Logical Apply Engine: Started succesfully..

We can crosscheck the parameter values from SYSTEM.LOGSTDBY$PARAMETERS

SQL> SELECT * FROM SYSTEM.LOGSTDBY$PARAMETERS WHERE NAME = ‘MAX_EVENTS_RECORDED’
/


OR

DGMGRL> show database “TESTDB” LsbyMaxEventsRecorded;

LsbyMaxEventsRecorded = ‘5000’

Advertisements
This entry was posted in Oracle Data Guard, Oracle Logical Data Guard and tagged . Bookmark the permalink.

One Response to Resolving ORA-16714 / ORA-16792

  1. After changing some parameter even with dgmgrl CLI tool you can get:
    Warning: ORA-16792: Some configurable property value is inconsistent with the database setting.

    To see which parameter is in incosistent state you can check with following command:
    SHOW RESOURCE ‘resource_name‘ ‘InconsistentProperties’;

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 )

Google+ photo

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

Connecting to %s