When we run the Validate Mass Allocation Program of Oracle GL, it aborts with the following message (log file) >> glavcl() 16-JUL-2007 17:28:29 /caggp1/sftw/oraapp/11.0/g lprod/gl/1 1.0.28/bin /GLAVAL Program was terminated by signal 11 Cause: The program completed execution - in particular it was terminated by signal 11. Action: If the program completed normally, no action is required.
Action: If the program completed with a statu It runs fine in TEST and QA Environments. We are only facing this in Production. When checked in Metalink, most of them advice to go in for a patch. Can anyone list me out the cause and the possible solutions for the same? There could be more than one reason for your program to give signal error. But this is usually linked to a memory issue.
1) you can check the os limits of memory given to your program as a first step like using ulimit command in unix. 2) run the same program but with a different set of input parameters to see whether a change in memory requirement lets the program run or still it gives the same error. 3) worst case, the.o files required while generating the executable which are generated by ARU database as part of the patch creation could be corrupted. The only way we can identify this issue is when we face them otherwise we assume everything will be ok. Hollywood movie download in hindi. 4) may be our program was not tested properly with a large amount of data in TEST and QA environments. If we can reproduce this issue after we clone prod instance to TEST, then it could be a CODE bug also:) These signal bugs take a bit of time to get solved because of their nature.
Bitmap Reports Fail Due to Signal 11 and/or hanging after Patchset 19: Emsg:Was Terminated By Signal 11 (Doc ID 759456.1) PDF Reports Fail With Program Was Terminated By Signal 11 (Doc ID 396336.1) LOG:: --. SYSTEM_CORE_DUMPED Process terminated by signal 11. This question is. What happened? The current ABAP program had to be terminated because the.