Environment: 12.1.0.2 EE 64-bit on RHEL 5.11 64bit
Primary DB: DGUARD1
Phys Standby: DGUARD2
Hi,
I'm trying to configure the DG broker with a physical standby configured. However I'm encountering an issue where the Broker keeps setting the state of LOG_ARCHIVE_DEST_STATE_2 to RESET. Even if I change it through the DGMGRL command line using 'edit database dguard1 set state='TRANSPORT-ON', it will show the command being successfully executed, however the parameter value still remains at 'RESET'. I can manually change it through the SQL*Plus command line to 'enable', however if I do other changes within the Broker environment it changes it back to 'RESET'
Below is a snippet from the alert log showing what happens when I set DG_BROKER_START=TRUE and DMON starts up:
ALTER SYSTEM SET dg_broker_start=TRUE SCOPE=BOTH;
Starting background process DMON
Mon Aug 24 15:33:25 2015
DMON started with pid=7, OS id=7597
Mon Aug 24 15:33:28 2015
Starting Data Guard Broker (DMON)
Starting background process INSV
Mon Aug 24 15:33:28 2015
INSV started with pid=26, OS id=7599
Starting background process NSV1
Mon Aug 24 15:33:31 2015
NSV1 started with pid=27, OS id=7700
Starting background process RSM0
Mon Aug 24 15:33:34 2015
RSM0 started with pid=28, OS id=7712
Mon Aug 24 15:33:38 2015
ALTER SYSTEM SET log_archive_dest_state_2='RESET' SCOPE=BOTH;
Mon Aug 24 15:33:38 2015
ALTER SYSTEM SET log_archive_trace=0 SCOPE=BOTH SID='DGUARD1';
Mon Aug 24 15:33:38 2015
ALTER SYSTEM SET log_archive_format='%t_%s_%r.dbf' SCOPE=SPFILE SID='DGUARD1';
And here's the configuration as shown in DGMGRL:
DGMGRL> show database verbose dguard1
Database - dguard1
Role: PRIMARY
Intended State: TRANSPORT-ON
Instance(s):
When I do an 'edit database dguard1 set state='TRANSPORT-ON;', in the alert log I see a log switch happen, but no change to the log_archive_dest_state_2 parameter.
I may be missing / misunderstanding / overlooking something, any help in the right direction would be much appreciated!