Contact Premier Online Trainings Today

Oracle Apps DBA - AutoPatch error The worker should not have status Running or Restarted at this point

Date Added: 26 Nov.2019 Date Updated: 19 Jan.2020 Oracle Apps DBA Full Blog

AutoPatch error The worker should not have status Running or Restarted at this point

ADOP Patch Session got terminated abnormally due to network issue or patch hung or lost connectivity after that we are facing the error when restart adop patch.

 

Error:-

AutoPatch error: The worker should not have status 'Running' or 'Restarted' at this point.


Corrective Action:-

In R12.1.x, we need to use adctrl to check worker running or failed.

                 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

Select option as below:-

 1.    Show worker status ---> to show worker status

 4.    Tell manager that a worker failed its job 

 2.    Tell worker to restart a failed job

When applying patch using adpatch , Select option Yes When it prompts for

'Do you wish to Continue with Previous adpatch Session'


In R12.2.x, Use restart and abandon parameters to restart the patch session from where it failed.

$adop phase=apply patches=123456 restart=yes abandon=no