2 Replies Latest reply: May 8, 2012 10:27 AM by Imran Mahmood RSS

    12.1.1 - upgrade, adoworker in assigned status due to space issue.

    Rajiv N
      Hi All,

      We are in the process of upgrading to 12.1.1 from 11.5.10.2, after the job ran for about 12 hours, it hung due to space issue, I've released some space and check the worker status to be still assigned. Now the question is how to restart this adworker to start from where it hung.
      what's the best approach to restart this job ?

      Many Thanks in advance.
        • 1. Re: 12.1.1 - upgrade, adoworker in assigned status due to space issue.
          Hussein Sawwan-Oracle
          Please see these docs.

          How to Deal with the adpatch Peforrmance issue : Slow, Hang or Crash ? [ID 756063.1]

          Oracle E-Business Suite Patching Procedures
          http://download.oracle.com/docs/cd/B53825_08/current/acrobat/121adpp.pdf

          Oracle Applications Maintenance Procedures
          http://download.oracle.com/docs/cd/B25516_18/current/acrobat/11iadproc.pdf

          Thanks,
          Hussein
          • 2. Re: 12.1.1 - upgrade, adoworker in assigned status due to space issue.
            Imran Mahmood
            I know this thread is pretty old, but I experienced the same issues where a worker went in "ASSIGNED" state and patch was hanging.


            Control
            Worker Code Context Filename Status
            ------ -------- ----------------- -------------------------- --------------
            1 Run AutoPatch R120 pl Wait
            2 Run AutoPatch R120 pl amesicls.ldt Assigned


            I checked the process of adworkers in the backend on the server. And found that the process of workerid=2 is not there at all. It somehow vanished.

            $ ps -fu appscn10 | grep -i workerid=2
            appscn10 20881 20840 0 17:00:48 pts/66 1:56 /gpsscn10/erpapp/appl/ad/12.0.0/bin/adworker workerid=20 caller=adpatch
            appscn10 29347 167 0 09:51:20 pts/80 0:00 grep -i workerid=2
            appscn10 20840 11328 0 17:00:48 pts/66 0:00 /bin/sh -c /gpsscn10/erpapp/appl/ad/12.0.0/bin/adworker workerid=20 caller=adpa
            $

            If you see workerid=2 is not there, you can see workerid=20.

            Then I checked all the adctrl options, where I saw an option - "6. Restart a worker on the current machine". I restarted the worker 2 using option 6 from adctrl.


            Review the messages above, then press [Return] to continue.

            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


            Enter your choice [1] : 6


            You chose 6 - Restart a worker on the current machine.
            Before you enter the worker number below, make sure that there is no
            worker process already running with that worker number.

            Enter the worker number(s)/range(s) or 'all' for all workers,
            or press [Return] to go back to the menu : 2

            Control code changed to 'Startup' for worker 2.
            Review the messages above, then press [Return] to continue.

            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


            Enter your choice [1] :


            Control
            Worker Code Context Filename Status
            ------ -------- ----------------- -------------------------- --------------
            1 Run AutoPatch R120 pl Wait
            2 Startup AutoPatch R120 pl amesicls.ldt Assigned
            3 Run AutoPatch R120 pl Wait


            In backend, now workerid=2 will also appear.

            $ ps -fu appscn10 | grep -i 'workerid=2'
            appscn10 20881 20840 0 17:00:48 pts/66 1:57 /gpsscn10/erpapp/appl/ad/12.0.0/bin/adworker workerid=20 caller=adpatch
            appscn10 20840 11328 0 17:00:48 pts/66 0:00 /bin/sh -c /gpsscn10/erpapp/appl/ad/12.0.0/bin/adworker workerid=20 caller=adpa
            appscn10 18600 11328 0 09:54:10 pts/66 0:00 /bin/sh -c /gpsscn10/erpapp/appl/ad/12.0.0/bin/adworker workerid=2 caller=adpat
            appscn10 18669 18600 1 09:54:11 pts/66 0:07 /gpsscn10/erpapp/appl/ad/12.0.0/bin/adworker workerid=2 caller=adpatch
            appscn10 20553 167 0 09:54:21 pts/80 0:00 grep -i workerid=2



            Then the worker 2 got started at the server level. And control code showed up as "Startup". And then came into "Initial".

            Control
            Worker Code Context Filename Status
            ------ -------- ----------------- -------------------------- --------------
            1 Run AutoPatch R120 pl Wait
            2 Initial AutoPatch R120 pl amesicls.ldt Assigned


            And worker completed the job.

            Control
            Worker Code Context Filename Status
            ------ -------- ----------------- -------------------------- --------------
            1 Run AutoPatch R120 pl Wait
            2 Run AutoPatch R120 pl amesicls.ldt Completed


            Hope it helps.

            Thank you,
            Imran Mahmood.

            Edited by: user12223217 on May 8, 2012 8:25 AM