Signal 11- Error in oracle apps reports

Signal 11- Error in oracle apps reports

One of the most common error messages we see in Oracle E-business suite reports is à signal 11 error in oracle apps reports

This is non-self-explanatory message and hence takes loads of time and research required. Many a-times the report might work for couple of records but huge data may fail.

Listing below my observations and analysis:

1)     Issue with Formula columns/ functions within the report builder.

a.      Data type issue

b.     Un-handled exceptions in report triggers à Report triggers having incorrect select queries or variable assignments which are not handled in exception block.

2)     There is no provision for handling exceptions in main query block in Oracle report,  so if main block query has some issue,  it will result in signal 11 error Mostly,  the reason main query block fails is because of :

a.      Exact fetch returns more than one requested number of rows :  select sub-query in main query block returning multiple rows or user defined function throwing exception.

b.     Numeric or value error: TO_NUMBER function on alphanumeric column or joining two different data type columns.

3)     Referenced package not valid.

4)     Signal 11 error is occurs due to memory issues. For ex a formula column or placeholder column is returning infinite values then this error may occur.

5)     Very complex SQL statements with many Group By columns (which may not all be required)

6)     Parameter mismatches

7)     The reports were FTPed incorrectly (ASCII instead of binary)

8)     A 'Numeric or Value error' on some procedure code (although this may also cause a Signal 4error). Typically this is because you have a field or variable which is too small to hold a value passed to it, which often happens when you are summing values

Other than the query/ code related issues, in some cases it may be due to some instance issues. For me, this was quite rare.

1)     Not enough disk space in $APPL_TOP/out directory where the concurrent manager creates the report output files.

2)     Lack of storage space in table spaces, rollback segments etc

3)     Incorrect OS permission’s

4)     Issue could be because of Environment variables were not setup.

Please follow the note 1337095.1 on metal ink.

 More Info:

"Unaligned memory access" is a message coming back from the UNIX operating systems letting you know that an Oracle executable has tried to access memory incorrectly. It's not a problem with UNIX but is part of the operating system's mechanism of protecting itself from crashing.