My Oracle Support Banner

GLAMAS Mass Allocation Program Erroring With Signal 11 Error (Doc ID 2972038.1)

Last updated on SEPTEMBER 06, 2023

Applies to:

Oracle General Ledger - Version 12.0.0 and later
Information in this document applies to any platform.

Symptoms

One Mass Allocation (MA) batch that has been running with success in the past is now ending in error with the following error seen in the concurrent request debug (Profile GL: Debug mode set to Yes) log file:

AMAS0018: glacje() - Fetched 20000 flex records

flexfield to be searched = XXX.XXXXX.XXXX.000.00.0000.000.00000   

SEGMENT1 = XXX
SEGMENT2 = XXXXX
SEGMENT3 = XXXX
SEGMENT4 = 000
SEGMENT5 = 00
SEGMENT6 = 0000
SEGMENT7 = 000
SEGMENT8 = 00000

Creating flexfield for XXX.XXXXX.XXXX.000.00.0000.000.00000
/xx01/oracle/OA12/fs1/apps/appl/gl/12.0.0/bin/GLAMAS
Program was terminated by signal 11

Note: Values in the above log snippet, XXX and 000, are provided as segment values for the sample structure, your values and flexfield structure will be different and specific to your configuration.


STEPS: 
--------
1. Using a General Ledger Responsibility
2. Navigate to Journals -> Generate -> Allocation
3. Query the Mass Allocation batch in question... submit if for the period needed MMM-YY.
4. Review the concurrent request and see that it has ended in error.


Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.