on ‎2010 Sep 27 6:35 PM
Hello Gurus,
We have updated the SAP Kernel to SAP ERP ECC 6.0, our system is Windows 2003 and SQL Server, we had installed SAP Kernel release 172 and updated it to 254, after the update in Tx ST22 some dumps are show: SYSTEM_CORE_DUMPED
this is the full dump log:
Errores tiempo ejec. SYSTEM_CORE_DUMPED
Fecha y hora 26.09.2010 10:12:44
-
-
-
-
Texto breve |
Process terminated by signal 0. |
-
-
-
-
¿Qué ha sucedido? |
Error in the SAP kernel. |
The current ABAP "SAPLMR1M" program had to be terminated because the |
ABAP processor detected an internal system error. |
-
-
-
-
¿Qué puede hacer? |
Note which actions and input led to the error. |
For further help in handling the problem, contact your SAP administrator |
. |
You can use the ABAP dump analysis transaction ST22 to view and manage |
termination messages, in particular for long term reference. |
-
-
-
-
Anál.errores |
An R/3 System process was terminated by an operating system signal. |
- |
Possible reasons for this are: |
1. Internal system error. |
2. Process was terminated externally (by the system administrator). |
- |
Last error logged in SAP kernel |
Component............ "Taskhandler" |
Place................ "SAP-Server BOGPRDNW_PRD_00 on host BOGPRDNW (wp 3)" |
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....... " " |
-
-
-
-
Entorno sistema |
SAP-Release 700 |
Application server... "BOGPRDNW" |
Network address...... "192.168.135.166" |
Operating system..... "Windows NT" |
Release.............. "5.2" |
Hardware type........ "8x AMD64 Level" |
Character length.... 16 Bits |
Pointer length....... 64 Bits |
Work process number.. 3 |
Shortdump setting.... "full" |
Database server... "BOGPRDNW" |
Database type..... "MSSQL" |
Database name..... "PRD" |
Database user ID.. "prd" |
Char.set.... "C" |
SAP kernel....... 700 |
created (date)... "May 3 2010 22:46:28" |
create on........ "NT 5.2 3790 Service Pack 2 x86 MS VC++ 14.00" |
Database version. "SQL_Server_8.00 " |
Patch level. 254 |
Patch text.. " " |
Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194" |
SAP database version. 700 |
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows |
NT 6.0, Windows NT 6.1" |
Memory consumption |
Roll.... 16192 |
EM...... 20949200 |
Heap.... 0 |
Page.... 172032 |
MM Used. 16454816 |
MM Free. 301248 |
-
-
-
-
Usuario y transacción |
Client.............. 400 |
User................ "ANDMORENO" |
Language key........ "S" |
Transaction......... "MIRO " |
Transactions ID..... "107FC9DF052EF120BA8700237D65A060" |
Program............. "SAPLMR1M" |
Screen.............. "SAPLMR1M 6250" |
Screen line......... 0 |
-
-
-
-
Info posición de cancelación |
Termination occurred in the ABAP program "SAPLMR1M" - in "SYSTEM-EXIT". |
The main program was "SAPLMR1M ". |
In the source code you have the termination point in line 0 |
of the (Include) program " ". |
-
-
-
-
Notas internas |
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 20100926100222. |
Stack trace of 'core'. |
-
-
How we can fix this error?? this dump is generated in Tx such MIRO or MIGO
thanks
HEPC
Request clarification before answering.
Hello All,
Thanks for your answers and help. The solution was, additional to update the kernel (254) we applied the last disp+work, enq and ENSERVER packages. The kernel level now is 272. Perhaps is the solution but SAP have not published any note about that.
HEPC
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 5 | |
| 5 | |
| 4 | |
| 4 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.