Dear Erman,
We are upgrading from R12.1.3 to R12.2.10. [applcrp@sssterpdev1 patch]$ adop phase=apply apply_mode=downtime patches=30399999,33678475 merge=yes abandon=yes We are applying RUP 10, It is failed at asndelff.sql with no data found. According to below note id,we are trying to skip the worker but the patch session didnt move furthur, Enter your choice [1] : 1 Control Worker Code Context Filename Status ------ -------- ----------------- -------------------------- -------------- 1 Done AutoPatch R120 Wait 2 Done AutoPatch R120 Wait 3 Done AutoPatch R120 asndelff.sql Skip & restart 4 Done AutoPatch R120 Wait 12.2.10 RUP 30399999 Is Failing On Asndelff.sql (Doc ID 2786903.1) Please guide. Thanks, Satish |
Administrator
|
Error stack is similar right?
--- ERROR at line 1: ORA-20001: ORA-06501: PL/SQL: program error ORA-06512: at "APPS.FND_SET", line 249 ORA-01403: no data found ORA-06512: at line 8 --> If you are trying to skip the work, then I guess ASN is not installed. Because that MOS note tells you that you can skip the worker if ASN is not installed and not going to be used. However; you are telling me that skipping the worker doesn't solve the issue.. We need to check the logs to give further recommendations on this, but! there is also a patch there, in that MOS note.. As a last resort, you may try that patch.(even though ASN is not going to be used in your environment) -- Because there is a bug and there is a patch for it -> patch 29628578:R12.ASN.C. |
In reply to this post by satish
Dear Erman,
We are not using it. Applying patch with wait_on_failed_job=yes as below.Now we are able to skip the worker. But not sure whether it is correct or wrong. [applcrp@sssterpdev1 patch]$ adop phase=apply apply_mode=downtime patches=30399999,33678475 merge=yes restart=yes wait_on_failed_job=yes Enter your choice [1] : 1 Control Worker Code Context Filename Status ------ -------- ----------------- -------------------------- -------------- 1 Run AutoPatch R120 MSDODPCODE.sql FAILED 2 Run AutoPatch R120 Wait 3 Run AutoPatch R120 Wait 4 Run AutoPatch R120 Wait 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] : 8 Enter the worker number(s)/range(s) or 'all' for all workers, or press [Return] to go back to the menu : 1 Status changed to 'Skip & restart' for worker 1. 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] : 1 Control Worker Code Context Filename Status ------ -------- ----------------- -------------------------- -------------- 1 Run AutoPatch R120 ARXLASD.ldt Running 2 Run AutoPatch R120 APXLAAAD.ldt Assigned 3 Run AutoPatch R120 APXLASET.ldt Assigned 4 Run AutoPatch R120 ARXLAAAD.ldt Assigned Review the messages above, then press [Return] to continue. Thanks, Satish |
Administrator
|
Okay. Good.
wait_on_failed_job=yes allows you to manipulate failed jobs (PLSQL only) via the adctrl utility. So you did okay. As MOS note "12.2.10 RUP 30399999 Is Failing On Asndelff.sql (Doc ID 2786903.1)" suggests, if you don't use ASN (Oracle Sales), you can skip that failed worker. You can review your adop patch log file and see that failed execution is skipped and you can also check whether the remaining tasks are assigned and completed properly or not. |
Free forum by Nabble | Edit this page |