Thursday, January 19, 2017

How to use adctrl utility to restart failed worker in patch application

In this example I will demonstrate you how 'adctrl' utility is used for checking the status of workers or restarting workers while applying patches.
1. Open a new terminal window and setup environment to run scripts on Application Tier 
2. Start the adctrl utility
cd $AD_TOP/bin
adctrl
If you don't know what is the directory for $AD_TOP then use the following:
cd /u01/apps/[hostname]/apps/apps_st/appl/ad/12.0.0/bin
adctrl
          It will ask you to provide couple of details such as APPS user DB password, APPL_TOP directory etc.
3. Once you give above information, adctrl utility will start and following menu will appear:
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
4. Use option 6 and then option 2 to restart a failed job
5. Now to to the terminal screen where 'adpatch' utility was running. You will see messages that 'worker                 restarted'. And if you have fixed the error successfully, adctrl will resume the patch application.        

How to see the status of a worker?
At any time you can see the status of all workers run by 'adpatch' utility. To see the status:
1. Follow the steps described above (from step 1 to 3).
2. Choose option 1. All worker statuses (with the jobs they were executing or failed) will be shown on the terminal window.

Assumptions
  • Database is up and running
  • Patch application has started with adpatch utility
  • adpatch has thrown an error in a job with a worker
Environment
  • Oracle E Business Suite R12i
  • RHEL 4.5

No comments:

Post a Comment

IAS Cache initialization failed

 Today I faced an Issue in R12.2 instance. The solution I followed to overcome the issue is very simple, but they are more than one solution...