CPU JULY2012 - 10.2.0.5 to standby target
edited Aug 1, 2012 6:54AM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 4 commentsAnswered
Greetings -
We are planning a migration of a (PeopleSoft) database from 10.2.0.3 --> 10.2.0.5.
Leadership will embrace CPU patching, but note id's 437276.1 & 278641.1 fail to address the possiblity.
I would prefer to have CPUJuly2012 in place on Standby. As we are migrating, primary will go away.
So question is, will this function or fail (and has it been attempted) ??
Server 1 Primary 10.2.0.3 - no cpu's
Server 2 Standby 10.2.0.5 - July 2012 cpu's.
or must I go with:
Server 1 Primary 10.2.0.3 - no cpu's
Server 2 Standby 10.2.0.5 - no cpu's
after successful switch over, shutdown 2 (New) Primary. Apply July2012 CPU.
Please advise...
TIA
Doug
0