Re: upgrade grid from 11.2.0.3 to 11.2.0.4 PSU question.
- From: Justin Mungal <justin@xxxxxxx>
- To: nmjamaleddin@xxxxxxxxxxxxxxxx
- Date: Thu, 15 May 2014 15:59:46 -0500
I wouldn't suggest you do it either. I've never heard of anyone installing
multiple grid homes, and it's probably not even supported. If this is a
production system, the last thing you want to do is build an unsupported
configuration. Keeping the database available during patching is what RAC
is all about. If you can't tolerate the short amount of downtime a PSU
requires, you should already be running it.
-Justin
On Thu, May 15, 2014 at 3:47 PM, Nabil Jamaleddin <
nmjamaleddin@xxxxxxxxxxxxxxxx> wrote:
> Thanks Martin,
>
>
>
> I still want to try to go forward with this idea. It might be a little
> more complex than just a shutdown, rename the grid home folder and start
> backup. But if I can figure out all that needs to be done, this will be a
> very nice way of pushing out PSU patches. And makes a (if needed) back-out
> a bit easier too.
>
>
>
> Besides looking into the root*.sh scripts, anything else you think might
> be a “show stopper”?
>
>
>
>
>
> *From:* Martin Berger [mailto:martin.a.berger@xxxxxxxxx]
> *Sent:* Thursday, May 15, 2014 3:20 PM
> *To:* nmjamaleddin@xxxxxxxxxxxxxxxx
> *Cc:* Oracle-L oracle-l
> *Subject:* Re: upgrade grid from 11.2.0.3 to 11.2.0.4 PSU question.
>
>
>
>
>
> On Thu, May 15, 2014 at 8:37 PM, Nabil Jamaleddin <
> nmjamaleddin@xxxxxxxxxxxxxxxx> wrote:
>
> Once I am ready to push the new PSU out I
> will shutdown HAS, rename the gird homes and start grid back up.
>
>
> please don't do this.
>
> an upgrade between patch sets might change more than only binaries. it's
> likely (even I have not checked) some internal resources are changed.
>
> If you don't run the proper root*.sh scripts, you might face very strange
> results somewhere in the future.
>
>
>
>
>
>
>
> ------------------------------------------------------------------
> This email is intended solely for the use of the addressee and may
> contain information that is confidential, proprietary, or both.
> If you receive this email in error please immediately notify the
> sender and delete the email.
> ------------------------------------------------------------------
>
>
Other related posts:
