Re: Datapatch while users/applications are connected?

Chris,

The following MOS documents discuss "conditional" rolling patching in a RAC environment w/o the need to "startup upgrade" prior to invoking datapatch ...you might wish to see if these are applicable to your DB version and / or compatible w/ your business requirements.

18c : Datapatch New Features And Changes from 12.1 (Doc ID 2420120.1) RAC Rolling Install Process for the "Oracle JavaVM Component Database PSU/RU" (OJVM PSU/RU) Patches (Doc ID 2217053.1) Transparent rolling updates of OJVM components - Oracle Database 21c (Doc ID 2802019.1)

I am not advocating or suggesting that this approach be adopted as a best practice - just wished to make mention of the enhancements that have been made to datapatch...

Thanks,

--Rajesh

On Wed, Dec 14, 2022 at 6:52 PM Mladen Gogala <gogala.mladen_at_gmail.com> wrote:

> On 12/14/22 13:52, Ilmar Kerm wrote:
>
> RAC is patched in rolling fashion, so nothing should be down for users in
> any point in time. This includes datapatch.
> Even with single instance - if no/minimal downtime is desired, there
> really is no other option.
> Monitor datapatch execution like any other database session - it has
> happened for me a few times that for example long running DBMS_SCHEDULER
> jobs lock the package while datapatch wants to replace the package - so
> datapatch will start waiting for a lock.
>
> How will you run "opatch" on the running instance? If my memory serves me
> right, it is necessary to run "opatch" before "datapatch". On a single
> instance, it is necessary to bring the instance down. There is no rolling
> upgrade of a single instance DB.
>
> --
> Mladen Gogala
> Database Consultant
> Tel: (347) 321-1217https://dbwhisperer.wordpress.com
>
>

--
http://www.freelists.org/webpage/oracle-l