Re: cpu patch with physical standby

And if downtime isn't a big issue, you can just patch the binaries on the
standby, let it get caught up, then patch the binaries and run catcpu on the
primary.  The changes made by catcpu will then propagate over to the standby
through the normal apply process.

--
Jason Heinrich


On Tue, Jul 27, 2010 at 10:46 AM, Matthew Zito <mzito@xxxxxxxxxxx> wrote:

>
> From chatting with our field engineers, what we worked out with Oracle
> backline engineering is that the order doesn't really matter - because
> you're not "officially" patched until you have done *both* the data
> dictionary update and the application of the CPUs.  So you could really
> do them in either order, it just depends on what gets done first.
>
> I would say, if you wanted to minimize downtime, patch just the binaries
> on the standby, do a switchover to the standby, run catcpu and whatnot
> on the standby, since that's an online operation, bring down the
> now-standby/formerly-primary instance and patch the binaries, and then
> switch back.
>
> Matt
>
> -----Original Message-----
> From: oracle-l-bounce@xxxxxxxxxxxxx
> [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Ray Stell
> Sent: Tuesday, July 27, 2010 9:36 AM
> To: oracle-l@xxxxxxxxxxxxx
> Subject: cpu patch with physical standby
>
> 813445.1 says to apply cpu to primary first.
> 278641.1 says to apply cpu to standby first.
> Maybe it doesn't matter.  Thoughts?
> --
> http://www.freelists.org/webpage/oracle-l
>
>
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>

Other related posts: