Stand alone Primary and RAC Data Guard
edited Aug 3, 2012 6:14PM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 2 commentsAnswered
Aim: (i) Upgrade the AAAAA which is a 2 node RAC DB from 11.2.0.1 to 11.2.0.3
(ii) Reconfigure the 2 node RAC (associated with the DB upgraded) which is having configuration issues, because the technical teams felt upgrading the DB in it is little riskier (with non standard build).
Solution/Game plan proposed after analysing multiple plans;
1) Use a standalone server available, build a standalone data guard (physical server) for the 2 node RAC primary.
2) On the day of cutover-1, enable flashback and switchover the RAC to the physical standby which is a standalone server.
3) De configure the standby setup (Defer the log_archive_2 & other DG related parameters) and delete the DG related setting, and drop the flashback.
(ii) Reconfigure the 2 node RAC (associated with the DB upgraded) which is having configuration issues, because the technical teams felt upgrading the DB in it is little riskier (with non standard build).
Solution/Game plan proposed after analysing multiple plans;
1) Use a standalone server available, build a standalone data guard (physical server) for the 2 node RAC primary.
2) On the day of cutover-1, enable flashback and switchover the RAC to the physical standby which is a standalone server.
3) De configure the standby setup (Defer the log_archive_2 & other DG related parameters) and delete the DG related setting, and drop the flashback.
0