Re: Datapatch while users/applications are connected?

My recent experience 19RU16 to 19RU17

What I did (3 node RAC, EBS apps)

1. Applied RU17+ JVB on node-1, node-2
2. When I started applying RU17 on node-3(last node), opatchauto runs datapatch at the end, locked/hung at SQL> SQL> call dbms_java.grant_permission('SYSTEM', 'java.io.FilePermission', 2 '<<ALL FILES>>', 'read'); indefinitely.
3. Raised SR with Oracle but not workaround
4. Finally, killed the opatchauto session on node-3
5. Applied JVM patch assuming Java related issue may resolve but no luck as PDB on node-3 was shown RESTRICT=YES mode.
6. Stopped DB instances on node-3 . Tried running the datapatch on node-2 instance. To my bad luck, node-2 instance became RESTRICT=YES. Finally, I made a decision on shutting down all nodes(complete shutdown) .
7. Started node-1 instance in upgrade mode and ran the datapatch. Within a couple of min, datapatched completed.

So, never patch RU --> JVM patches together on each node. Complete RU patching on all nodes, then come back and start JVM patching.

Cheers,
Sameer

On Thu, 15 Dec 2022 at 15:09, Amit Grover <amitgrover27_at_gmail.com> wrote:

>
> Give a read to the blogs below by the individuals from the database
> upgrade and Migrations team. We dont do as said in the blogs but have
> started investigating and talking about it, so wanted to share.
>
> -
> https://mikedietrichde.com/2020/01/23/do-you-need-startup-upgrade-for-ojvm/
> -
> https://dohdatabase.com/2022/10/27/can-i-run-datapatch-when-users-are-connected/
>
> Best Regards
> Amit Grover
>
>
> On Wed, Dec 14, 2022 at 4:39 PM Rajesh Aialavajjala <
> r.aialavajjala_at_gmail.com> wrote:
>
>> 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
>>>
>>>

-- 
NOTICE: This email message is for the sole use of the addressee(s) named 
above and may contain confidential and privileged information. Any 
unauthorized review, use, disclosure or distribution of this message or any 
attachments is expressly prohibited. If you are not the intended recipient, 
please contact the sender by reply email and destroy all copies and backups 
of the original message. 

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