What To Do When Receiving A Signal 11 For One or All Oracle Alerts? (Doc ID 1354644.1)

APPLIES TO:

Oracle Alert - Version 11.5.10.2 to 12.2 [Release 11.5 to 12.2]
Information in this document applies to any platform.
ALECDC 
ALECTC 
ALPPNR
ALRALERT.fmb 
alssmn.lc
aluapp.lc

GOAL

Why does Oracle Alert fail with Signal 11 error and what can be done?

<ALR_TOP>/bin/ALECDC
<ALR_TOP>/bin/ALECTC
<ALR_TOP>/bin/ALPPNR
Program was terminated by signal 11

SOLUTION

ATTENTION!
With the implementation of the 11G Database (and later) Case Sensitivity Project (Bug 10138986) in Release 12.1.X, ALL Alerts may fail with Signal 11 and therefore would need to apply the following:
Patch 13728376 - Alert fails with signal 11 error after password case sensitivity fix
delivering file: aluapp.lc  120.1.12010000.4.

Signal 11 is a generic error message that is caused by lack of Operating System Resources (Memory).
Oracle Alerts has never been known to process large amounts of data.

The following are some methods that have been known to resolve or alleviate generating Signal 11 errors in Oracle Alerts.

* Upgrade to the latest Alert code.
To check the file versions, run
adident Header $ALR_TOP/bin/ALECDC
adident Header $ALR_TOP/bin/ALPPWF  
or
strings $ALR_TOP/bin/ALECDC | grep Header | grep alssmn.lc
strings $ALR_TOP/bin/ALPPWF | grep Header | grep aluapp.lc

To date, the following patches are available:
11.5.10: Patch 5839356 Email body was getting truncated early for a message exceeding 64k (alssmn.lc 115.48)

12.0: Patch 8715092 CC AND BCC RECIPIENTS SHOWN IN TO FIELD IN ALERT MAILS (alssmn.lc 120.7.12000000.21)
12.0: Patch 7592660 RELEASE 12 BUG FOR SIGNAL 11 WITH ALPPWF (alpiwf.lc 120.0.12000000.5)

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)

12.2: Fix included in 12.2.2 and later releases, via unpublished defect 10090649 - TST122: ALECTC IS GETTING FAILED WITH SIGNAL 11 ERROR

* Setup a dedicated concurrent manager for Oracle Alert executables. By default, Alerts run under the Standard manager.
Using System Administrator Responsibility, navigate to Concurrent : Manager > Define
Add new: Alert Concurrent Manager (name may vary; model from Standard manager)
Add specialization rules. Include Program Alert :
ALECDC (Check Periodic Alert)
ALECTC (Check Event Alert)
ALEPPE (Periodic Alert Scheduler)
Save this and now query the Standard manager.
From the specialization rules here, Exclude the same three executables.
Bounce all the concurrent managers.

* Run the Alert during non-peak processing times.

* Evaluate the Select Statement. 
How many records are being retrieved? If the following clause is added to reduce the number of records retrieved, does the Alert still error:
and rownum < 10
How efficient is the SQL? Can it be improved? Use tools like SQLTXPLAIN.SQL for analysis. See "Troubleshooting Oracle Applications Performance Issues" (Doc ID 169935.1)
Are there any non-text characters being selected?
Are there any fields being selected that are of data type Long or Blob? Use the DESCRIBE command to check table columns.

* Is the Alert Action defined as Detail or Summary Level? Try a different Level. If using Summary Level, make sure the Template position is not changed (starting in column 1)
=**= Enter summary template below this line =**=
**
=**= Enter summary template above this line =**=

* Consider using another tool besides Alerts. Write a concurrent report

REFERENCES

NOTE:271367.1 - 11i : Oracle Alert Alert Check Setup Test
NOTE:471672.1 - R12.0.6+ : Oracle Alert Check Alert Setup Test

NOTE:1438919.1 - After Upgrade R12.1.3 All Alerts Are Completing With Signal 11
NOTE:1162153.1:1174735.1 
BUG:13728376 - OEL5.7: ALECDC PROGRAM WAS TERMINATED BY SIGNAL 11

Source: Oracle Metalink