Syed Saad Ali

Oracle ACE Pro

Oracle Solution Architect

Oracle E-Business Suite

Oracle Cloud Infrastructure

Oracle Fusion Middleware

Oracle Database Administration

Oracle Weblogic Administration

Syed Saad Ali

Oracle ACE Pro

Oracle Solution Architect

Oracle E-Business Suite

Oracle Cloud Infrastructure

Oracle Fusion Middleware

Oracle Database Administration

Oracle Weblogic Administration

Blog Post

The worker should not have status Running or Restarted

May 22, 2023 APPS DBA
The worker should not have status Running or Restarted

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

ERROR:

R12.2 ADOP:

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

Telling workers to quit…
All workers have quit.
Connecting to APPS……Connected successfully.
AutoPatch error:

Error running SQL and EXEC commands in parallel

CAUSE:

  1. The adpatch or adop process was terminated abruptly at the OS level while the patch was being applied.
  2. The database was either shut down or terminated unexpectedly.
  3. Error encountered when tried to re-start adop patch.

SOLUTION:

Step 1: Launch Adctrl and check the status of the workers. Are the workers currently running or have they been started?

Select the following options in Adctrl: 
   Option 1 to Show Worker Status then
   Option 4 to Tell manager that a worker failed its job

Step 2. Restart the ADOP patch from the following given OPTIONS.

  • If you wish to restart a failed patch from the beginning, specify the following option
adop phase=apply patches=<Patch_Number> restart=no abandon=yes
  • If you wish to restart a failed patch from where it left off, simply specify the following option

adop phase=apply patches=<Patch_Number> restart=yes abandon=no

Related Posts
Write a comment