Why does the Broker change my log_archive_dest parameters
edited Feb 25, 2013 10:44AM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 2 commentsAnswered ✓
We are testing adding the Data Guard Broker to our current Data Guard Environment. All hot standby databases are physical standby’s.
Our current environment consists of our primary database in our main data center, a local hot standby in our main data center, and a remote hot standby in an offsite data center. Our test environment looks like the following.
DBA1 – primary database
DBA1HA – local hot standby database
DBA1HA2 – remote hot standby database
We are currently using a manual process to switchover the primary database (DBA1) with the remote hot standby (DBA1HA2). Although this seems to work fine we would like to make the process easier using the data guard broker. Less steps then our current manual process.
0