In these kinds of situations, you should check the Apps tier OS process, see what it is doing.
Also, it is important to check the db tier as well.
You should find the db session id of that worker and see what it is waiting for. (current wait event)..
Ther can some locks left, there can be a latch wait etc..
For a deeper diag, you should review the sql or command that the worker is executing. You should review the code in it and try the predict what can be the cause accordingly.
I have to apply another patch while application must keep running. Should I :
- start another cycle adop from prepare phase and apply the patch
- or apply it in "hotpatch" mode
I have to apply another patch while application must keep running. Should I :
- start another cycle adop from prepare phase and apply the patch
- or apply it in "hotpatch" mode
Regards,
Latifa
If you reply to this email, your message will be added to the discussion below:
I reapplied a patch and that patch runs successfuly.
However when I ask the table ad_bugs, the created_date and LAST_UPDATE_DATE, they remains with the old date of its application ? How can ?
It is not supported update those table manually.
Create an SR, and get approval from Oracle. Then you can run your update, or Oracle may send you a datafix.
As for hotpatching and/or downtime patching-> you just should not use hotpatch and downtime options unless it is written in readme files or it is written in Oracle Support documents (specifically written for your patch)
Now I am fixed :) Thank yoy for your advise.
I will wait until customer can stop application. then I'll apply my patch (because the reade me doesn't ask to apply it in hotpatch mode) in a regular mode, I mean: prepare, apply, finalize, cutover and cleanup.