Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com
http://www.free-online-exams.com
Whatever listed below is from my own experience for cases and issues I faced while I am working as an Apps DBA .
It does not nessassary to apply on all cases just it will give you a hint or clu to where you should focus.
While I was trying to reapply a patch using adpatch after my old session got disconnected inproperly ( This includes you close your session by mistake, your PC reboots , network issues),
I ran the adpatch again and select "YES" for continue from previous run so it will resume from the last point befire it got terminated by using the *.rf9 files in $APPL_TOP/admin/$sid/restart
Thats would be in an ideal situation,however sometimes it fails throwing the following error:
"AutoPatch error:
The worker should not have status 'Running' or 'Restarted' at this point.
Telling workers to quit...
All workers have quit.
AutoPatch error:
adfrjp(): Error running jobs in workers"
What is caused it is an "inconsistency between fnd_install_processes, ad_deferred_jobs and .rf9 files".
What to do next is to use adctrl utility and select option "1. Show worker status" ==> Show Running
it you try to quit the worker by hitting option "3. Tell worker to quit" , you will get "Control code already set to 'Quit' for worker xxx".
Here what you going to do to get on the top of this issue:
Hit on option "4. Tell manager that a worker failed its job" from the adctrl utility and type the worker id you saw above to change his status from "Running" to "Failed"
Then tell this gentelman worker to restart his failed job by hitting "2. Tell worker to restart a failed job"
and hopefully will get your issue resolved and it will proceed with your adpatch
No comments:
Post a Comment