R12.2.4 Upgrade Patches 17919161,21900859 taking very long time

Hi,

I am now applying R12.2.4 upgrade patch 17919161 and 21900859 as per doc. id 1617458.1

adop phase=apply apply_mode=downtime patches=17919161,21900859 merge=yes

I started the patch on 16/11/2017 at 11:45 a.m. but still it is not completed. I checked the adop.log and alert_PROD1 but no error. I checked thru adctrl and it showed number of jobs with status Running.

It is more than 28 hours. Appreciate providing solution.

Thanks.

[ErmanArslansOracleBlog]

Check and see what the adworker's are doing..
Also do db level//session level checks if the worker's are still running some sqls..

Please find an attached document showing status of adworkers. Appreciate to provide script to see db level/session level status of adworkers running any sql.

Thanks.ADWorker_Status.docx

[ErmanArslansOracleBlog]

There is no script like that.
You can write one or use toad or similar to identify.
But, your workers are running working on xdf files.
Check their logs first.
Check worker 2's log for instance..
According to the log, go to db and check.
Maybe the processes that is executed by workers are just in hang status in the apps node.

So, first see the worker logs and decide what to do next.

Attached is the adwoek002.log and adworkadwork005.log005.logadwork002.log

[ErmanArslansOracleBlog]

workers seems to be failed.

You have the java errors there ->

  Calling /DB/EBS/APPS/fs1/EBSapps/comn/util/jdk/jre/bin/java ...
Exception in thread "main" java.sql.SQLRecoverableException: IO Error: Socket read timed out
        at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:489)
        at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:678)
        at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:234)
        at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:34)
        at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:567)
        at java.sql.DriverManager.getConnection(DriverManager.java:571)
        at java.sql.DriverManager.getConnection(DriverManager.java:215)
        at oracle.apps.ad.worker.AdJavaWorker.getAppsConnection(AdJavaWorker.java:1050)
        at oracle.apps.ad.worker.AdJavaWorker.main(AdJavaWorker.java:278)
Caused by: oracle.net.ns.NetException: Socket read timed out
        at oracle.net.ns.Packet.receive(Packet.java:349)
        at oracle.net.ns.NSProtocol.connect(NSProtocol.java:310)
        at oracle.jdbc.driver.T4CConnection.connect(T4CConnection.java:1229)
        at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:326)
        ... 8 more

[ErmanArslansOracleBlog]

AD Controller (adctrl) Manages parallel workers in AD Administration and AutoPatch.

You source "patch env". and use adctrl. (adctrl should be used from the patch env)

Read this -> https://docs.oracle.com/cd/E26401_01/doc.122/e22954/T202991T530135.htm (read the subtitle : Terminating a Hanging Worker Process)

After you terminate the process from the OS. Your adwork will be failed.
Then you can follow subtitle named "Restarting a Failed Worker" in the same document.