You may encounter ALECTC signal 11 while EBS is executing the concurrent programs triggered by Oracle Alerts.
This was happen to me in my last EBS R12-Exadata migration.
The root document to follow was What To Do When Receiving A Signal 11 For One or All Oracle Alerts? (Doc ID 1354644.1)
The solution was applying the following patches.
Note that, even if it was not related with the password case sensitivity, it was useful to apply the patch for that bug as well.
12.1: Patch 13728376 - Alert fails with signal 11 error after password case sensitivity fix (aluapp.lc 120.1.12010000.4)
12.1: Patch 9908378 - RELEASE 12 BUG FOR SIGNAL 11 WITH ALPPWF (alppwf.lc 120.0.12010000.3)
12.1: Patch 9817770 POST-R12.ATG_PF.B.DELTA.3 CONSOLIDATED PATCH (alssmn.lc 120.22.12010000.9)
This was happen to me in my last EBS R12-Exadata migration.
The root document to follow was What To Do When Receiving A Signal 11 For One or All Oracle Alerts? (Doc ID 1354644.1)
The solution was applying the following patches.
Note that, even if it was not related with the password case sensitivity, it was useful to apply the patch for that bug as well.
12.1: Patch 13728376 - Alert fails with signal 11 error after password case sensitivity fix (aluapp.lc 120.1.12010000.4)
12.1: Patch 9908378 - RELEASE 12 BUG FOR SIGNAL 11 WITH ALPPWF (alppwf.lc 120.0.12010000.3)
12.1: Patch 9817770 POST-R12.ATG_PF.B.DELTA.3 CONSOLIDATED PATCH (alssmn.lc 120.22.12010000.9)
No comments :
Post a Comment
If you will ask a question, please don't comment here..
For your questions, please create an issue into my forum.
Forum Link: http://ermanarslan.blogspot.com.tr/p/forum.html
Register and create an issue in the related category.
I will support you from there.