HOME > > Adpatch Error: Unable to find job when reading existing jobs

Adpatch Error: Unable to find job when reading existing jobs

Anup - Thursday, December 17, 2009

Last night, when I was applying patch on EBS by using “adpatch” utility. Suddenly, the adpatch terminal was close accidentally by me.


Next time, when I was trying to restart adpatch utility with previous session. The adpatch utility through error:


Unable to find job when reading existing jobs

No job in manager's jobs_ready list with: product = username = filename = arguments =

Telling workers to quit...


The cause of the error was “closed session when applying Patch or AutoInstall Session. At this point adworker may be in a W (Wait) status or F (Failed) status”.


I have resolved this error:


  1. Determine the last job that was supposed to run.
  2. Grep from all the adworker log files to confirm that the last job has been compeleted successfully by one of the adworkers.
  3. Update fnd_install_processes with control code and status both = 'W' for the worker that this driver is assigned.
  4. Restart adpatch with previous session.


Reference: Meta Link Note: 257505.1

Sara Reid said...

I've already been aware of this document as i had already a SR opened for the 'no jobs found' error. I couldn't follow the instructions given in the doc you mentioned as i couldn't run the jobs assigned to the affected workers successfully, so these jobs would have been skipped.

2gb micro sd karte

Unknown said...

Thank you very much for the instuction. It saved me 24 hours of patching again from the beginning.
Thanks
Saravanan Ramesh

Contact me

Get in Touch

Need to get touch with me? Please fill out the form with your enquiry.

Name
Anup Srivastav
Address
Lucknow - Utter Pradesh
Email
myindiandba@gmail.com
Message me