SYSTEM_CORE_DUMPED

[Former Member]

Hi All,

We recently upgraded kernel on our ECC6.0 DEV system to 700 Sup.Pkg lvl. 254,

After Upgraded we got some dump in system SYSTEM_CORE_DUMPED :

Short text

Process terminated by signal " ".

What happened?

Error in the SAP kernel.

The current ABAP "SAPMSSY30" program had to be terminated because the

ABAP processor detected an internal system error.

Last error logged in SAP kernel

Component............ "Taskhandler"

Place................ "SAP-Server host name(wp 8)"

Version.............. 1

Error code........... 11

Error text........... "ThSigHandler: signal"

Description.......... " "

System call.......... " "

Module............... "thxxhead.c"

Line................. 10852

The error reported by the operating system is:

Error number..... " "

Error text....... " "

How to correct the error

The R/3 System work directory (e.g. /usr/sap/c11/D00/work ) often

contains a file called 'core'.

Information on where terminated

Termination occurred in the ABAP program "SAPMSSY30" - in "SYSTEM-EXIT".

The main program was "SAPMSSY30 ".

In the source code you have the termination point in line 0

of the (Include) program " ".

Internal notes

The termination was triggered in function "ab_CoreInfo"

of the SAP kernel, in line 7371 of the module

"//bas/700_REL/src/krn/runt/abrabax.c#37".

The internal operation just processed is " ".

Internal mode was started at 20101207075643.

Stack trace of 'core'.

After 4,5 dumps we are not getting this dump but we are trying to find out root cause of this dump.

Please suggest so that we can stop this dump to generate in QAS system after kernel Upgrade.

Shivam

[markus_doehr2]

- open ST22

- click on the left side on "analysis section" (bottom)

- post the stack trace

Markus

[Former Member]

Hi Markus,

Stack Trace says:

(0) 0x4000000001b50ef0 CTrcStack + 0x1b0 at dptstack.c:227 [dw.sapCTV_DVEBMGS70]

(1) 0x400000000298ddc0 Z16rabaxCStackSavev + 0x1c0 at abrabax.c:7257 [dw.sapCTV_DVEBMGS70]

(2) 0x4000000002988720 ab_rabax + 0x3b40 at abrabax.c:1268 [dw.sapCTV_DVEBMGS70]

(3) 0x40000000029b03d0 ab_CoreInfo + 0x1b0 at abrabax.c:7374 [dw.sapCTV_DVEBMGS70]

(4) 0x4000000001af7210 ThrCoreInfo + 0x30 at thxxab.c:6578 [dw.sapCTV_DVEBMGS70]

(5) 0x40000000017b9c90 ThIErrHandle + 0x24a0 at thxxhead.c:11080 [dw.sapCTV_DVEBMGS70]

(6) 0x4000000001747890 ThErrHandle + 0x30 at thxxhead.c:10566 [dw.sapCTV_DVEBMGS70]

(7) 0x400000000188b690 ThSigHandler + 0xb0 at thxxtool3.c:3540 [dw.sapCTV_DVEBMGS70]

(8) 0x40000000050508d0 SigIGenAction + 0x810 at sigux.c:1190 [dw.sapCTV_DVEBMGS70]

(9) 0xe0000001908828e0 Signal 11 (SIGSEGV) delivered

(10) 0x4000000001d09720 dyLoadAndInitDynpro + 0x1a0 at dyrdyp.c:272 [dw.sapCTV_DVEBMGS70]

(11) 0x4000000001d09550 dyLoadAndInitMainDynpro + 0x30 at dyrdyp.c:110 [dw.sapCTV_DVEBMGS70]

(12) 0x4000000001c66540 dyShowLastRabax + 0x2d0 at dynpabsv.c:5858 [dw.sapCTV_DVEBMGS70]

(13) 0x4000000002da3b60 Z35TpdaPostMortemSlavereceiveMessagesv + 0x340 at abtpdmess.c:3763 [dw.

(14) 0x4000000002da3420 ab_TpdaStopDynp + 0x80 at abtpdmess.c:1957 [dw.sapCTV_DVEBMGS70]

(15) 0x4000000001c25740 dynpen00 + 0x4040 at dymain.c:1799 [dw.sapCTV_DVEBMGS70]

(16) 0x4000000001788c30 Thdynpen00 + 0x520 at thxxhead.c:4957 [dw.sapCTV_DVEBMGS70]

(17) 0x4000000001751a00 TskhLoop + 0x5110 at thxxhead.c:4645 [dw.sapCTV_DVEBMGS70]

(18) 0x4000000001747560 ThStart + 0x460 at thxxhead.c:1207 [dw.sapCTV_DVEBMGS70]

(19) 0x40000000015e1260 DpMain + 0x5f0 at dpxxdisp.c:1128 [dw.sapCTV_DVEBMGS70]

(20) 0x40000000015dc860 main + 0x60 at thxxanf.c:84 [dw.sapCTV_DVEBMGS70]

(21) 0xc000000000033910 main_opd_entry + 0x50 [/usr/lib/hpux64/dld.so]

Please suggest.

Shivam

[markus_doehr2]

> (15) 0x4000000001c25740 dynpen00 + 0x4040 at dymain.c:1799 [dw.sapCTV_DVEBMGS70]

According to

Note 1296222 - frequent workprocess dumps after kernel upgrade

this access violation in dynpen00 is fixed with kernels as of 271.

Markus

[Former Member]

Hi Markus,

We are already on Kernel 700 level 254 and as per note correction has been delievered in patch 193.

So still should we go for tha paramter rdisp/ss_enforce_rollout setting in our system.

Shivam

[Former Member]

You sure that you are on 254? As per note the parameter rdisp/ss_enforce_rollout is not required to set if you are on 7.00: 193 patch.

[Former Member]

Hi ,

Please take a look at note 1121904 for some details. When the systen isrunning short of memory and also the paging space is getting full, a signal 33 is sent to all processes in the system. Processes can react on

this signal to free up memory.

If not enough memory is releseased, the oprating system is starting

to stop processes ( and with this freeing up memory ) to ensure

correct that the OS still can run.

you can get the log from dev_w0 ,dev_W1,etc ...

Regards

Sathies

[Former Member]

As you told that this has been reported after kernel upgrade then you better try to check for those system which is on old kernel.. also this dump is only "REQUEST" specific which is generated only due to specific function ex- this will never generate while running SM50, what I mean check with user what task is generating this dump and after you notice that this is due to new kernel upgrade then better open up SAP message.

Regards,

Salim

[Former Member]

Any specific program or tcode you are getting this dump?

Have you upgraded the kernel on DEV as well, any issues?