Replacing Data Guard Primary with New Hardware/Host Without DG Standby Failover?
edited Jul 17, 2012 3:02AM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 6 commentsAnswered
Hi,I have a very large database using 11.2.0.3 on Linux x86-64, using standalone Grid/ASM over a dedicated SAN.
This database has a remote physical standby using DataGuard, in the same configuration.
We need to replace the hardware (Host and SAN) under the primary.
The application group does not want to switchover to the standby because of application latency issues; given the most critical ops are batch oriented on this database, they prefer facing hours of downtime if planned.
The database is large enough that a rebuild of either the primary or the standby from RMAN disk backup will take about 5 days, transfer of the full backup and archives between the DG data centers is slow and would add a couple days as well.
This database has a remote physical standby using DataGuard, in the same configuration.
We need to replace the hardware (Host and SAN) under the primary.
The application group does not want to switchover to the standby because of application latency issues; given the most critical ops are batch oriented on this database, they prefer facing hours of downtime if planned.
The database is large enough that a rebuild of either the primary or the standby from RMAN disk backup will take about 5 days, transfer of the full backup and archives between the DG data centers is slow and would add a couple days as well.
0