Re: opatch performance

From: Tharmarajah, Sam <sambavan.tharmarajah_at_usask.ca>
Date: Mon, 21 Oct 2024 04:21:13 +0000
Message-ID: <A457B25B-17C3-4600-A2CB-A0099477F304_at_usask.ca>



We run the opatch cleanup as part of our pre-patch run and it immensely helps when it comes to following opatch run waits. The first run is always the long one.

On Oct 20, 2024, at 10:14 PM, dimensional.dba <dmarc-noreply_at_freelists.org> wrote:


CAUTION: External to USask. Verify sender and use caution with links and attachments. Forward suspicious emails to phishing_at_usask.ca

I have ran into the same problems as you have seen and as the note Qaiser pointed out you need to perform inactive patch cleanup, then things are quick again.

From: oracle-l-bounce_at_freelists.org <oracle-l-bounce_at_freelists.org> On Behalf Of Mladen Gogala Sent: Sunday, October 20, 2024 6:57 PM
To: ORACLE-L <oracle-l_at_freelists.org> Subject: opatch performance

I have upgraded my databases today. I know I am lazy and that the DBRU came out on Tuesday, 10/15/2024, but that's OK. Laziness is a virtue in the IT world. However, this list is not about my mom's mistakes in my upbringing or my psychological traits, it's about Oracle. My databases are running on VirtualBox VMs, several of them. I noticed that on Oracle 19c, opatch took more than 1:30 hours just to check the requirements. After the requirements were checked, the rest went fine, but one hour thirty minutes just to check the requirements? Here is a sample:

bash-4.2$ time $ORACLE_HOME/OPatch/opatch apply Oracle Interim Patch Installer version 12.2.0.1.44 Copyright (c) 2024, Oracle Corporation. All rights reserved.

Oracle Home       : /opt/oracle/product/19c/dbhome_1
Central Inventory : /opt/oracle/oraInventory
   from           : /opt/oracle/product/19c/dbhome_1/oraInst.loc
OPatch version    : 12.2.0.1.44
OUI version       : 12.2.0.7.0
Log file location : /opt/oracle/product/19c/dbhome_1/cfgtoollogs/opatch/opatch2024-10-20_21-18-07PM_1.log

Verifying environment and performing prerequisite checks... ^C
OPatch failed with error code 130

real 35m58.373s
user 36m58.117s
sys 0m6.585s

This is not the whole thing, I broke it after 35 min with '^C". Does anyone have any explanation or will I have to spend an evening doing "strace"?
--

Mladen Gogala
Database Consultant
https://dbwhisperer.wordpress.com<https://dbwhisperer.wordpress.com/>
-- http://www.freelists.org/webpage/oracle-l
--

http://www.freelists.org/webpage/oracle-l Received on Mon Oct 21 2024 - 06:21:13 CEST

Original text of this message