on 06-06-2012 8:17 AM
Hi,
We have our archiving job failing daily on PI with a system_core_dumped dump.
We've recently jumped to DB2 FP5 & kernel 7.20 patch 215.
Dump details:
Process terminated by signal 11.
Error in the SAP kernel
The current ABAP program "CL_ARFA_SCENARIO==============CP" had to be
terminated because the
ABAP processor detected an internal system error.
The termination occurred during generation of the ABAP/4 program
"CL_ARFA_SCENARIO==============CP".
-
The termination occurred in line 6
of the source code of program "CL_ARFA_SCENARIO==============CI" (when calling
the editor 60).
Line where the error occured:
for IF_ARFA_POFACT_CALLBACK~TYP_REQUEST_ID
Even if i double click this line, the work process terminates with Signal 11.
Please help..
Thank you.
Saba.
Hello Saba,
Have you checked SAP Notes first ?
I executed a search on service.sap.com/notes with the following criteria "CL_ARFA_SCENARIO"
Note 1680695 - Syntax-check dump for CL_ARFA_SCENARIO and CL_ARFA_READPLUGI
Note 1065417 - Deleting/changing archiving scenarios causes inconsistencies
Many times, its easier to search SAP Notes and quickly find solutions.
Hope that helps.
Regards,
Siddhesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Kindly go through the following link....
http://scn.sap.com/thread/1734502
http://scn.sap.com/thread/426975
May be it will help you to solve your problem....
And try applying the new kernel patch level also.
Regards,
Anil
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Thanks for the reply !
We're already on the latest kernel..
The wp trace says exactly what's in the dump.
The Active Calls is as below:
Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
=> 64 bit R/3 Kernel
=> 64 bit AIX Kernel
=> Heap limit = unlimited
=> Stack limit = unlimited
=> Core limit = unlimited
=> File size limit = unlimited
=> Heap address = 0x1165f38a0
=> Stack address = 0xffffffffffe0250
=> Stack low = 0xffffffffffda520
=> Stack high = 0xffffffffffff8a0
=> Stack Trace:
#scPerformPoolFromToPass2__FP3ENVUiT27HD_BOOLP7SC_INFO() at 0x1005df5c8
#scBlkCompleteDerive__FPC3ENVP7SC_INFO() at 0x1005e2ee8
#sc_nested_intf_find__FP3ENVPCUsT2P7SC_INFO() at 0x10126c428
#sc_intf_attr_find__FP7SC_INFO8VAR_KINDP3ENVPCUsT47HD_BOOLT28CL_STATET6PP3ENVT1() at 0x10059c320
#sc_calicr_pass2__FPUsT1PC10SC_CONTEXTP7SC_INFO() at 0x10126ae9c
#completeSymbOp2__FP3ENVUiT27HD_BOOLP7SC_INFO() at 0x1005e035c
#scPerformPoolFromToPass2__FP3ENVUiT27HD_BOOLP7SC_INFO() at 0x1005df5b0
#scBlkCompleteDerive__FPC3ENVP7SC_INFO() at 0x1005e2ee8
#cls_type_find_1__FP7SC_INFOP3ENVPCUsUi8CL_STATEPP3ENVT1() at 0x1005d0b48
#simple_type_find_1__FPCUs9TYPE_MODEPP3ENVP7SC_INFO() at 0x1005cb19c
#sc_complex_type_find__FPCUs9TYPE_MODEP7SC_INFO() at 0x1005c9f98
#sc_ctypid_do__FPCUs9TYPE_MODEUiP7SC_INFO() at 0x1005c8cec
#completeSymbOp2__FP3ENVUiT27HD_BOOLP7SC_INFO() at 0x1005df930
#scPerformPoolFromToPass2__FP3ENVUiT27HD_BOOLP7SC_INFO() at 0x1005df5b0
#scTypeComplete__FPC7sc_typeP7SC_INFO() at 0x1005e2b34
#sc_ctypst_pass2__FP7AR_HEADP7SC_INFO() at 0x1009dd96c
#sc_ctypcr_pass2__FP7sc_typeP7SC_INFO() at 0x1005c30f0
#completeSymbOp2__FP3ENVUiT27HD_BOOLP7SC_INFO() at 0x1005dfcfc
#performPoolPass2__FP3ENVP7SC_INFO() at 0x1005df13c
#scPerformPass2__FP7SC_INFO() at 0x1005df06c
#sc_pass2() at 0x100589b84
#Unknown at 0x1014e9298
#sc_expan__FUi() at 0x1012ba0b0
#parse__FP5LEVEL() at 0x101242650
#checkStatement__FiPP4STMTP5LEVELPP3ENVN41() at 0x10123b878
#sc_check() at 0x101239444
#scProcessText__FUi() at 0x1012390ec
#checkStatement__FiPP4STMTP5LEVELPP3ENVN41() at 0x10123ba54
Pls. help..
Thank you.
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.