on 03-23-2009 12:36 PM
Hi Basis Gurus,
Refering to SAP Note and our analysis.We did a oracle patch upgrade from 9.2.0.7 to 9.2.0.8 in BW 3.5 DEV,QAS and Production system and the oracle patch upgrade was completed sucessfully without any error in all three system.
Now in ST22 we are getting SYSTEM_CORE_DUMPED
Below i have attached the dump error BW 3.5 of Production system.These dumps we are getting in our DEV and QAS also.In SAP Note of oracle patch upgrade they have not mentioned anything on this problem.
Runtime Errors SYSTEM_CORE_DUMPED
Date and Time 23.03.2009 12:03:05
ShrtText
Process terminated by signal 11.
What happened?
The current ABAP program had to be terminated because the
ABAP processor detected an internal system error.
The current ABAP program "????????????????????????????????????????" had to be
terminated because the ABAP
processor discovered an invalid system state.
What can you do?
Make a note of the actions and input which caused the error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
Error analysis
An SAP System process was terminated by an operating system signal.
-
Possible reasons for this are:
1. Internal SAP System error.
2. Process was terminated externally (by the system administrator).
-
-
Last error logged in SAP kernel
-
Component............ "Taskhandler"
Place................ "SAP-Server sappw4as01_PW4_16 on host vus650pa (wp 23)"
Version.............. 1
Error code........... 11
Error text........... "ThSigHandler: signal"
Description.......... " "
System call.......... " "
Module............... "thxxhead.c"
Line................. 9893
How to correct the error
The SAP System work directory (e.g. /usr/sap/c11/D00/work ) often
contains a file called 'core'.
Save this file under another name.
If you cannot solve the problem yourself and you wish to send
an error message to SAP, include the following documents:
1. A printout of the problem description (short dump)
To obtain this, select in the current display "System->List->
Save->Local File (unconverted)".
2. A suitable printout of the system log
To obtain this, call the system log through transaction SM21.
Limit the time interval to 10 minutes before and 5 minutes
after the short dump. In the display, then select the function
"System->List->Save->Local File (unconverted)".
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, select the Editor function "Further Utilities->
Upload/Download->Download".
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
System environment
SAP Release.............. "640"
Application server....... "sappw4as01-db"
Network address.......... "144.135.64.20"
Operating system......... "SunOS"
Release.................. "5.9"
Hardware type............ "sun4u"
Character length......... 8 Bits
Pointer length........... 64 Bits
Work process number...... 23
Short dump setting....... "full"
Database server.......... "vus650pc"
Database type............ "ORACLE"
Database name............ "PW4"
Database owner........... "SAPPW4"
Character set............ "en_US"
SAP kernel............... "640"
Created on............... "Aug 17 2008 21:34:33"
Created in............... "SunOS 5.8 Generic_117350-38 sun4u"
Database version......... "OCI_920 "
Patch level.............. "247"
Patch text............... " "
Supported environment....
Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
10.2.0.."
SAP database version..... "640"
Operating system......... "SunOS 5.8, SunOS 5.9, SunOS 5.10"
Memory usage.............
Roll..................... 696832
EM....................... 0
Heap..................... 0
Page..................... 0
MM Used.................. 613208
MM Free.................. 63784
SAP Release.............. "640"
User and Transaction
Client.............. 000
User................ "SAPSYS"
Language key........ "E"
Transaction......... " "
Program............. "????????????????????????????????????????"
Screen.............. " "
Screen line......... 0
Information on where terminated
The program "????????????????????????????????????????" was started as a
background job.
Job name........ "SAP_COLLECTOR_FOR_NONE_R3_STAT"
Job initiator... "DDIC"
Job number...... 11030906
Contents of system fields
Name Val.
SY-SUBRC 0
SY-INDEX 0
SY-TABIX 0
SY-DBCNT 0
SY-FDPOS 0
SY-LSIND 0
SY-PAGNO 0
SY-LINNO 1
SY-COLNO 1
SY-PFKEY
SY-UCOMM
SY-TITLE ABAP Job Control, ABAP Job Runtime Environment
SY-MSGTY
SY-MSGID
SY-MSGNO 000
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
Internal notes
The termination occurred in the function "ab_CoreInfo" of the SAP
Basis System, specifically in line 7103 of the module
"//bas/640_REL/src/krn/runt/abrabax.c#44".
The internal operation just processed is " ".
The internal session was started at 20090323120305.
Stack trace of 'core'.
Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
[0] DoStack2 ( 0x10481f890, 0xffffffff7fff3420, 0x1004a69a0, 0x3e8, 0x1028bbbd8, 0x1028bbbd8 ), at
[1] CTrcStack2 ( 0x10481f890, 0x0, 0x800, 0x2, 0xffffffff7c1442c8, 0x1028bbbd8 ), at 0x1004a6538
[2] __1cQrabax_CStackSave6F_v_ ( 0x0, 0x10481f890, 0x103103a18, 0x0, 0x1, 0xffffffff7fff3884 ), at
[3] ab_rabax ( 0x2926000, 0x103103000, 0x0, 0x2, 0x102926000, 0x8010912a ), at 0x100a58e10
[4] ab_CoreInfo ( 0xb, 0x1800, 0x101f049d5, 0xffffffff7fff3fac, 0x102adc4a4, 0x103103a38 ), at 0x1
[5] ThrCoreInfo ( 0xb, 0xb, 0x102cbb000, 0x2cbb000, 0x100000000, 0x1 ), at 0x10046263c
[6] ThIErrHandle ( 0x102926374, 0x4, 0x10292636c, 0x102d19a88, 0xb, 0x10290b5e4 ), at 0x10029843c
[7] SigIGenAction ( 0x1, 0x275ec00, 0x10275eec0, 0xb, 0x102926398, 0x10292636c ), at 0x101d639dc
[8] __sighndlr ( 0xb, 0xffffffff7fff5d40, 0xffffffff7fff5a60, 0x101d630fc, 0x0, 0x0 ), at 0xffffff
[9] call_user_handler ( 0xffffffff7b900000, 0xffffffff7fff5d40, 0xffffffff7fff5a60, 0x0, 0x0, 0x0
[10] sigacthandler ( 0xb, 0xffffffff7fff5d40, 0xffffffff7fff5a60, 0xffffffff735b33d0, 0xffffffff73
[11] ttcdrv ( 0x0, 0x10adf8fd8, 0x10adfb308, 0x10adee500, 0x0, 0xffffffff73b9c228 ), at 0xffffffff
[12] nioqwa ( 0x10adf90e8, 0x0, 0xffffffff735b3440, 0x10adfb308, 0x10adf9004, 0x0 ), at 0xffffffff
[13] upirtrc ( 0x1c808, 0x0, 0xffffffff73462600, 0x10adfb308, 0x0, 0x0 ), at 0xffffffff7327af60
[14] kpurcsc ( 0x10adf6b78, 0xffffffff7fffbe4a, 0x0, 0x10adfb308, 0x10adfc260, 0xffffffff735b69e0
[15] kpuexecv8 ( 0x10adf6b78, 0x10b2f35d0, 0x10b2f3650, 0x40004c00, 0x4e, 0x10adfb308 ), at 0xffff
[16] kpuexec ( 0x10adf6b78, 0x10b2f35d0, 0x10adf7238, 0x1, 0x10adf8fd8, 0x0 ), at 0xffffffff731eb9
[17] OCIStmtExecute ( 0x10adf6b78, 0x10b2f35d0, 0x10adf7238, 0x1, 0x0, 0x0 ), at 0xffffffff7325811
[18] oci_execute_stmt ( 0x0, 0x10b2f35d0, 0xffffffff7435ef10, 0x0, 0xffffffff743f3a38, 0xffffffff7
[19] stmt_fetch ( 0x10ad9db78, 0x10ada5328, 0x1, 0xd, 0x0, 0x1 ), at 0xffffffff74104108
[20] exec_fetch ( 0x10ad9db78, 0x1, 0x10339caf0, 0x1, 0x0, 0xffffffff740f5758 ), at 0xffffffff740f
[21] DbSlRead ( 0x0, 0x10ada52b0, 0x10339caf0, 0x1, 0x0, 0x0 ), at 0xffffffff740f0ba8
[22] dbsl_read ( 0x10339ca68, 0x10339c9e0, 0x10339caf0, 0x100000000, 0x1, 0x101380f90 ), at 0x1014
[23] dbsl_call ( 0x10339ca98, 0x0, 0x3, 0x0, 0x74, 0x0 ), at 0x101381008
[24] dbsl_exec ( 0x10339ca98, 0x0, 0x103378548, 0x3, 0x0, 0x103378548 ), at 0x101380f14
[25] select_single ( 0x10339ca98, 0x100000000, 0x1, 0x339c800, 0x0, 0x0 ), at 0x10137d224
[26] tran_rtab ( 0x103378548, 0x0, 0xffffffff7fffc888, 0x0, 0xfffe, 0x0 ), at 0x1012af4cc
[27] rtab_exec ( 0x103378548, 0xfffffffffffffffd, 0xffffffff7fffc888, 0xffffffff7fffc888, 0x0, 0x0
[28] db_xrtab0 ( 0xffffffff7fffc8bc, 0x0, 0xffffffff7fffc8a0, 0xffffffff7fffc888, 0xffffffffffffff
[29] rstss01__select_from_TST01 ( 0xffffffff7fffd350, 0x0, 0xffffffffffffffff, 0x102655c00, 0xffff
[30] rstsos__obj_stat ( 0xffffffff7fffd350, 0xffffffffffffffff, 0x14, 0x2dfe400, 0xffffffff7fffca7
[31] rstsow_open_write ( 0xffffffff7fffd350, 0x104b49078, 0xffffffffffffffff, 0x4000, 0x0, 0x0 ),
[32] TlgOw ( 0xffffffff7fffd61c, 0xffffffff6a00faed, 0x104b49078, 0x1, 0xffffffff7fffd3d8, 0x26264
[33] BtcTlgOw ( 0x102de84e0, 0xffffffff7fffd6e4, 0xffffffff6a00faed, 0x104b49078, 0xffffffff7fffd6
[34] BtcLgOw ( 0x0, 0xffffffff6a00faed, 0x104844400, 0x4844400, 0x100000000, 0xffffffff7fffd6e4 ),
[35] BtcEnvPrep ( 0xffffffff6a00fa68, 0x1, 0x440a800, 0x104844400, 0xffffffff6a00fa88, 0xffffffff6
[36] BtcJobStart ( 0x100000000, 0x4844400, 0x0, 0x0, 0x2926000, 0x20 ), at 0x101692994
[37] dynpen00 ( 0x102926000, 0x2928000, 0xc, 0x4350, 0x2926000, 0x1 ), at 0x100530060
[38] TskhLoop ( 0x7, 0x7, 0x34, 0xd, 0x1, 0x100000000 ), at 0x100279cd0
[39] tskhstart ( 0x100000000, 0x265800, 0x100265800, 0x1, 0x0, 0xffffffff704071f8 ), at 0x100265d1
[40] DpMain ( 0x2eeb000, 0x290a000, 0x100000000, 0x1, 0x0, 0x0 ), at 0x100186870
List of ABAP programs affected
Index Ty. Program Group Date Time Size Lang.
0 Prg SAPMSSY2 0 02.03.2006 15:33:44 248832 E
Directory of Application Tables
Name Date Time Lngth
Val.
Program SAPMSSY2
SYST . . : : 00002404
\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0
Our system details is as follows
BW 3.5
Sun Solaris 64 bit
Oracle 9.2.0.8 is the current version
kernel patch level is 247 (Kernel patch upgrade was done recently before the oracle patch upgrade)
Please help me in fixing this problem.
I hope this dump is not due to oracle patch upgrade.
Regards,
Anil.
Hi Markus,
Thanks for your reply
The System_Core_Dump comes from ALEREMOTE, DDIC, SAPSYS user in client 000 and 011
Below i have mentioned the details dev_w0 and dev_w0.old trace file
dev_w0 trace file details
Sun Mar 22 17:09:28 2009
M hostaddrlist return 0
A
A Sun Mar 22 17:09:29 2009
A *** ERROR => RFC ======> Could not open file rfcexec.sec
[abrfcio.c 7849]
M hostaddrlist return 0
A *** ERROR => RFC ======> Could not open file rfcexec.sec
[abrfcio.c 7849]
M hostaddrlist return 0
M hostaddrlist return 0
A
A Sun Mar 22 17:09:30 2009
A *** ERROR => RFC ======> Could not open file rfcexec.sec
[abrfcio.c 7849]
M hostaddrlist return 0
X Sun Mar 22 17:36:42 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Sun Mar 22 17:36:48 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Sun Mar 22 17:39:40 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Sun Mar 22 17:40:30 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X Sun Mar 22 18:02:36 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Sun Mar 22 18:03:40 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Sun Mar 22 18:03:56 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Sun Mar 22 18:04:03 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Sun Mar 22 18:04:10 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Sun Mar 22 18:04:18 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Sun Mar 22 18:04:30 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Sun Mar 22 18:04:40 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Sun Mar 22 18:05:16 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Sun Mar 22 18:05:23 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X Sun Mar 22 18:05:30 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Sun Mar 22 18:05:40 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Sun Mar 22 18:05:47 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Sun Mar 22 18:06:30 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Sun Mar 22 18:06:36 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Sun Mar 22 18:06:43 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Sun Mar 22 18:07:23 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Sun Mar 22 18:07:30 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Sun Mar 22 18:07:40 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Sun Mar 22 18:08:30 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Sun Mar 22 18:08:36 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Sun Mar 22 18:08:43 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Sun Mar 22 18:08:52 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Sun Mar 22 18:08:58 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Sun Mar 22 18:09:04 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Sun Mar 22 18:09:10 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Sun Mar 22 18:09:30 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
M
A Mon Mar 23 05:16:06 2009
A *** ERROR => RFC ======> Could not open file rfcexec.sec
[abrfcio.c 7849]
M hostaddrlist return 0
M hostaddrlist return 0
M
M Mon Mar 23 05:16:07 2009
M hostaddrlist return 0
M hostaddrlist return 0
A *** ERROR => RFC ======> Could not open file rfcexec.sec
[abrfcio.c 7849]
M hostaddrlist return 0
A Mon Mar 23 07:37:36 2009
A *** ERROR => RFC ======> connection closed (no data)
[abrfcio.c 7849]
A
A Mon Mar 23 07:37:39 2009
A *** ERROR => RFC ======> connection closed (no data)
[abrfcio.c 7849]
A
A Mon Mar 23 07:37:42 2009
A *** ERROR => RFC ======> connection closed (no data)
[abrfcio.c 7849]
X
X Mon Mar 23 08:03:36 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Mon Mar 23 08:03:45 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Mon Mar 23 08:03:54 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Mon Mar 23 08:04:45 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Mon Mar 23 08:04:54 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
C
dev_w0.old trace file details
M Thu Mar 19 18:48:11 2009
M hostaddrlist return 0
A *** ERROR => RFC ======> Could not open file rfcexec.sec
[abrfcio.c 7849]
M hostaddrlist return 0
M
M Thu Mar 19 18:48:12 2009
M hostaddrlist return 0
A *** ERROR => RFC ======> Could not open file rfcexec.sec
M Thu Mar 19 18:50:24 2009
M hostaddrlist return 0
A *** ERROR => RFC ======> Could not open file rfcexec.sec
[abrfcio.c 7849]
M hostaddrlist return 0
M
M Thu Mar 19 18:50:25 2009
M hostaddrlist return 0
M hostaddrlist return 0
A *** ERROR => RFC ======> Could not open file rfcexec.sec
[abrfcio.c 7849]
M hostaddrlist return 0
M hostaddrlist return 0
M
M Thu Mar 19 18:50:26 2009
M hostaddrlist return 0
M hostaddrlist return 0
A
A Thu Mar 19 18:50:27 2009
A *** ERROR => RFC ======> Could not open file rfcexec.sec
[abrfcio.c 7849]
M hostaddrlist return 0
M Thu Mar 19 18:52:53 2009
M hostaddrlist return 0
A *** ERROR => RFC ======> Could not open file rfcexec.sec
[abrfcio.c 7849]
M hostaddrlist return 0
M hostaddrlist return 0
M
M Thu Mar 19 18:52:54 2009
M hostaddrlist return 0
M hostaddrlist return 0
M
M Thu Mar 19 18:52:55 2009
M hostaddrlist return 0
A *** ERROR => RFC ======> Could not open file rfcexec.sec
[abrfcio.c 7849]
M hostaddrlist return 0
X
X Thu Mar 19 19:31:08 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Thu Mar 19 19:31:20 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Thu Mar 19 19:31:34 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Thu Mar 19 19:31:46 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Thu Mar 19 19:32:01 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Thu Mar 19 19:32:08 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Thu Mar 19 19:48:41 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Thu Mar 19 19:48:47 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Thu Mar 19 19:48:53 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Thu Mar 19 19:49:00 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Thu Mar 19 19:49:06 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
M
M Thu Mar 19 19:53:33 2009
M ThIUsrDel: th_rollback_usrdelentry = 1
X
X Thu Mar 19 20:09:21 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Thu Mar 19 20:09:35 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Thu Mar 19 20:10:04 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Thu Mar 19 20:10:13 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Thu Mar 19 20:10:21 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Thu Mar 19 20:10:35 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X Thu Mar 19 20:11:04 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Thu Mar 19 20:11:10 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Thu Mar 19 20:11:21 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Thu Mar 19 20:11:35 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Thu Mar 19 20:12:04 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Thu Mar 19 20:12:12 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Thu Mar 19 20:12:21 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Thu Mar 19 20:12:35 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Thu Mar 19 20:13:07 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Thu Mar 19 20:13:13 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Thu Mar 19 20:13:21 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Thu Mar 19 20:13:35 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
X Thu Mar 19 20:13:44 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
X
Please help me
Regards,
Anil.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
> X Sun Mar 22 17:36:42 2009
> X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2220]
The posted dev_w* doesn't show the dump. They show a documented problem with the kernel, see
Note 1239685 - Core in extended memory (EM) management
That error can be ignored or avoided by updating to a later kernel version (dw_246* or greater).
The network error in the oracle trace is because the workprocess died.
Please post a dev_w* containing a SYSTEM_CORE_DUMP.
Markus
Hi Basis Gurus,
We raised OSS message and SAP replied saying that to apply dw_276-20000221.sar disp+work package(SAP Note 1239685).
This kernel patch we applied in our DEV BW 3.5 system.
But still we are facing the same System_Core_Dumped problem after applying dw_276-20000221.sar disp+work package
Please help me in resolving this issue.
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 Prashant,
Our issue is not yet resolved.
I am in touch with SAP and reading some SAP Basis forum for this issue to get resolved.
I suggest you to post your trace file details and log file details.so that for further analysis.
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 Markus,
As per the Note 1239685 - Core in extended memory (EM) management.Today we applied dw_276(disp+work package) in Development BW 3.5 system.We will have to wait and watch.
Hi Michael,
We refered all the SAP Note before oracle patch upgrade and this dump problem was not there in the SAP Note.
Can you please be more clear on your previuos message as i didnt understand about it.
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 Markus,
Thanks for your reply
tomorrow i will post dev_w* as soon as i reach office.
But just wanted to know that is oracle patch upgrade is the cause for this system_core_dumped.This is beacuse we did oracle patch upgrade in other system lke 4.6,4.7,ECC etc.We didnt face this problem in those system.But why only this is happening in BW 3.5 DEV,QAS and Production system.
Regards,
Anil.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
fortunatly, the short dump already contains the stack where the violation occured. The relevant part is the following:
ttcdrv
nioqwa
upirtrc
kpurcsc
kpuexecv8
These are functions of the Oracle client libraries that are processed after the request left the SAP kernel (DBSL). In most cases, there is a problem in the client installation that is causing these errors. Since you are still using Oracle 9, you should check whether the client installation in /oracle/client/92x_64 really is just a softlink against the ORACLE_HOME.
At any case, include the output of the command
ldd /sapmnt/<SID>/exe/dboraslib.<platform specific extension>
and the output of the 'env' command executed as <sid>adm in your post.
Best Regards,
Michael
Hi Anil,
Your inputs wil be of great help to me. We updagred the Oracle database to our BI Production system and encountered the same problem what you faced " SYSTEM_CORE_DUMPED ". Can you please let me know how you have resolved the issue. Right know we have process chain failures with this mesage.
Can you please provide some input which could speed up the resolution.
Thanks in Advance,
Prashanth Kommareddy
Hi Markus,
One more thing i would like to tell you that when i was investigating today in /oracle/PW4/saptrace/usertrace i could find some details.Please find it below
vus650pc:pw4adm 72% pg pw4_ora_27392.trc
Dump file /oracle/PW4/saptrace/usertrace/pw4_ora_27392.trc
Oracle9i Enterprise Edition Release 9.2.0.8.0 - 64bit Production
With the Partitioning option
JServer Release 9.2.0.8.0 - Production
ORACLE_HOME = /oracle/PW4/920_64
System name: SunOS
Node name: vus650pc
Release: 5.9
Version: Generic_122300-12
Machine: sun4u
Instance name: PW4
Redo thread mounted by this instance: 1
Oracle process number: 46
Unix process pid: 27392, image: oracle@vus650pc (TNS V1-V3)
2009-03-22 21:38:01.178
SESSION ID:(49.18) 2009-03-22 21:38:01.169
opitsk: network error occurred while two-task session with mso trying to send break; error code = 12152
The above trc file details is of 22 March 2009 after i completed my oracle patch upgrade on Production system.
Please let me know the cause of *opitsk: network error occurred while two-task session with mso trying to send break; error code = 12152*
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 Markus,
Thanks for your reply
Infact we have upgraded the kernel recently on DEV,QAS and Production BW 3.5 system to 247
We downloaded the Database Independent and Oracle kernel files from SAP KERNEL 6.40 64-BIT->Solaris on SPARC 64 bit
We than extracted SAPEXE_247-20000221.SAR and SAPEXEDB_247-20000223.SAR kernel files and completed kernel upgrade successfully on all three systems.
On the other hand i think this could be a new problem in BW 3.5 system.SAP might ask us to upgrade it to 10.2.
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 Markus,
Thanks for your reply
I will send you the details of dev_w0,dev_w0.old tomorrow when i drop into office.
But please let me know is this system_core_dump is appearing because of oracle patch upgrade or beacuse of some other reason.
Actually we have followed SAP Note for oracle patch upgrade
One more thing i would like to tell is that we have other application like 4.6, 4.7, ECC 6.0 etc..Here we have also done the oracle patch upgrade from 9.2.0.7 to 9.2.0.8.But we never got this dump there.
This dump we are only getting in our BW 3.5 system
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 Anil,
> I will send you the details of dev_w0,dev_w0.old tomorrow when i drop into office.
Ok.
> But please let me know is this system_core_dump is appearing because of oracle patch upgrade or beacuse of some other reason.
According to the C-Stack you posted the error is occuring in a function called in the dboraslib.so, that's why I was asking if you updated the client also.
Since the database is up and running it's not a problem of the database server but more a problem of the application (SAP kernel, database interface, database client).
Please also check if you have the latest version of dboraslib.so (lib_dbsl) installed.
And also note: Oracle 9.2 is out of support already, if this is a new problem SAP may tell you to upgrade to a supported release (10.2).
Markus
Hi Basis Gurus,
Can anyone help me please in fixing this issue.
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 Markus,
I have installed Note 1017418 - Installing Oracle 9208 Client software on UNIX which we have applied in our system.
Please find the CPU Patch and Opatch details which we have applied in our system
vus650pc:orapw4 93% opatch lsinventory
Oracle Interim Patch Installer version 1.0.0.0.55
Copyright (c) 2006 Oracle Corporation. All Rights Reserved..
We recommend you refer to the OPatch documentation under
OPatch/docs for usage reference. We also recommend using
the latest OPatch version. For the latest OPatch version
and other support related issues, please refer to document
293369.1 which is viewable from metalink.oracle.com
Oracle Home = /oracle/PW4/920_64
Location of Oracle Universal Installer components = /oracle/PW4/920_64/oui
Location of OraInstaller.jar = "/oracle/PW4/920_64/oui/jlib"
Oracle Universal Installer shared library = /oracle/PW4/920_64/oui/lib/solaris/liboraInstaller.so
Location of Oracle Inventory Pointer = /var/opt/oracle/oraInst.loc
Location of Oracle Inventory = /oracle/PW4/920_64/inventory
Path to Java = /oracle/PW4/920_64/jre/1.4.2/bin/java
Log file = /oracle/PW4/920_64/.patch_storage/<patch ID>/*.log
Creating log file "/oracle/PW4/920_64/.patch_storage/LsInventory__03-22-2009_17-04-13.log"
Result:
Installed Patch List:
=====================
1) Patch 6646842 applied on Mon Mar 23 07:35:46 EST 2009
[ Base Bug(s): 5933477 2701372 6404861 6350567 5491035 4115449 6055396 5901910 5369855 6619946 6117049 5527732 6453643 5964709 6057120 5558878 6395038 6053580 6020552 5490859 5345437 5703297 5514908 6042409 6079599 6646842 5965170 5726053 5188321 5744161 5901875 6066116 6639973 6647071 6613049 6375910 6079582 6120177 6444045 4683638 ]
2) Patch 3755693 applied on Mon Mar 23 06:37:33 EST 2009
[ Base Bug(s): 3755693 ]
3) Patch 4660718 applied on Mon Mar 23 05:41:02 EST 2009
[ Base Bug(s): 4660718 ]
4) Patch 5057695 applied on Mon Mar 23 04:42:57 EST 2009
[ Base Bug(s): 5057695 ]
5) Patch 5345999 applied on Mon Mar 23 03:44:15 EST 2009
[ Base Bug(s): 5345999 ]
6) Patch 5386204 applied on Mon Mar 23 02:45:28 EST 2009
[ Base Bug(s): 5386204 ]
7) Patch 5530958 applied on Mon Mar 23 01:47:50 EST 2009
[ Base Bug(s): 5530958 ]
😎 Patch 5616968 applied on Mon Mar 23 00:49:00 EST 2009
[ Base Bug(s): 5508574 ]
9) Patch 5660451 applied on Sun Mar 22 23:52:02 EST 2009
[ Base Bug(s): 5660451 ]
10) Patch 5711002 applied on Sun Mar 22 22:53:10 EST 2009
[ Base Bug(s): 5442919 ]
11) Patch 5728380 applied on Sun Mar 22 21:54:10 EST 2009
[ Base Bug(s): 5728380 ]
12) Patch 5842790 applied on Sun Mar 22 20:55:18 EST 2009
[ Base Bug(s): 5842790 ]
13) Patch 5977665 applied on Sun Mar 22 19:56:29 EST 2009
[ Base Bug(s): 3639130 3521347 4541524 5129407 5977665 5172444 5562159 5140931 4483286 ]
14) Patch 5985053 applied on Sun Mar 22 18:58:47 EST 2009
[ Base Bug(s): 2965960 5985053 5530583 ]
15) Patch 6826661 applied on Sun Mar 22 18:03:55 EST 2009
[ Base Bug(s): 6826661 ]
OPatch succeeded.
vus650pc:orapw4 94%
I really dont know what is wrong.
Infact we have refered SAP Note and did all the analysis before starting oracle patch upgrade.
Please help us.
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 Markhus,
The database version is now 9.2.0.8.
We have also raised a OSS message to SAP.
Infact we are not sure why we are getting this dump after refering to SAP Note.
Please help us.
Regards,
Anil.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Did you also update the database client to 9.2.0.8?
Markus
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Raise an OSS to SAP as soon as possible.
Regards,
Subhash
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.