 |
|
Data Guard: archive log target fix
Oracle Tips by Burleson Consulting |
Question:
I have implemented Data Guard
successfully and I have set the archive_log_target = 600
(10 minutes) and everything seems fine, except I get the follow
error on the data guard screen in Grid Control
ORA-16792: configuration property
value is inconsistent with database setting
It seems to function fine, but if
I press the “Verify Configuration” button in Grid Control on the
Data Guard screen, it goes though the verification process, sets
the archive_log_target to zero, and clears the ORA-16792
error.
I set the value like this.
alter system set
archive_log_target = 600;
I tried using this command
alter system set
archive_log_target = 600 scope=spfile;
and the message said “system
altered” but the value was still zero. The value also sets
itself back to zero during a shutdown/restart when I do nightly
backups.
Answer:
First, make sure that you have
the
Oracle Data Guard book,
and review the scripts. On the data guard verification
wizard in OEM Grid control, there is a "Broker Managed" option
and a database option for fixing the problem.
I'd been using the
Broker option, so I used the other one which I believe wrote the
value to the init.ora file, and un-setting the broker option
seems to have fixed the archive_log_target problem
 |
If you like Oracle tuning, see the book "Oracle
Tuning: The Definitive Reference", with 950 pages of tuning tips and
scripts.
You can buy it direct from the publisher for 30%-off and get
instant access to the code depot of Oracle tuning scripts. |