Re: Datapatch while users/applications are connected?

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.

On Wed, Dec 14, 2022 at 6:46 PM Chris Taylor < christopherdtaylor1994_at_gmail.com> wrote:

> I've got a guy telling me its perfectly fine to run datapatch on a
> database while users & applications have reconnected. (In this example,
> patching from 19.14 to 19.17)
>
> How many of you guys do that?
>
> I understand from reading about it that you _can_ do that. I don't
> understand _why_ you would do that?
>
> What if datapatch runs into an exception?
>
> Is it not risky to allow users and applications into the database before
> the all the steps are finished?
>
> I'm wondering if I'm missing something here I guess?
>
> Thanks,
> Chris
>
>

-- 
Ilmar Kerm

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