Sep 9, 2016

on Leave a Comment

How to handle error during adpatch


You should know what's a patch doing.


My colleague asked me to take a look of an error he encountered during applying the patch 22644544 (Oracle E-Business Suite Release 12.1.3+ Recommended Patch Collection 5 [RPC5]).  The errors message are:

ORA-33272: Analytic workspace APPS.ODPCODE cannot be opened.
ORA-33288: Another user has incompatible access to analytic workspace

Okay. My colleague searched Metalink and cannot find any way to solve it.  The patching was now hanging in the middle. 

"Should I create a TAR now ?"

"Do you know what this ODPCODE actually doing?" I asked him.

"I don't know.  It seems to be something we're not using".  He replied.

"So, here is the solution". I started up "adctrl", and enter the my favourite number "8" -- a hidden menu item -- skip an error process.

                    AD Controller Menu
     ---------------------------------------------------
     1.    Show worker status
     2.    Tell worker to restart a failed job
     3.    Tell worker to quit
     4.    Tell manager that a worker failed its job
     5.    Tell manager that a worker acknowledges quit
     6.    Restart a worker on the current machine
     7.    Exit

Enter your choice [1] : 8
Enter the worker number(s)/range(s) or 'all' for all workers,
or press [Return] to go back to the menu : 1
Status changed to 'Skip & restart' for worker 1.
Review the messages above, then press [Return] to continue.

In the adpatch console, the actions was resumes immediately and lines flies after lines.
"Hey bro, carry one you patching."

0 comments: