on 03-13-2007 8:33 AM
when i try to create a new program, I get runtime error and it says start_call_sick
details: database inconsistency : start transaction SICK.
TRIGGER LOCATION OF RUNTIME
PROGRAM: SAPMSYST
INCLUDE : SAPMSYST
ROW 1.763
MODULE TYEP MODULE PAI
MODULE NAME D020_SNC_CHECK_EXTID
AND IT ALSO SAYS: KHA ( SYSTEM ID ) : SYSTEM RESTARTED
WORK PROCESS RESTARTED
SESSION TERMINATED.
ANY IDEA HOW TO SOLVE THIS ERROR?????
ITS ECC 5.0 WITH ORACEL DATABASE AND WIN 2K3 SP1 OS.
WAITING FOR REPLY
CHEERS
kHALIL
POINTS WILL BE AWARDED.
What kernel patch are you using? Try the latest patch.
Don´t write in CAPITALS, this means, that you are shouting at people.
--
Markus
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
good suggestions
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Khalil,
The program SAPMSYST is not correct in the buffers. SICK will only tell you if the work process distribution is OK - you have dialog, batch, update, etc, work processes. The error is severe enough that the work process restarts - you can check SM50 to see the work processes and their individual error logs.
The D010xxx tables contain program definitions as per a SGEN run - these represent the unpacked views of the ABAP programs. What you may want to do first is see if from ST22 when looking at the short dump, if you have a button that allows you to regenerate the program - like running SGEN on one program.
You may also want to review what changes have been made to the system to get you here - SAPMSYST is a rather central program. The core issue of the problem may be that the SAPMSYST has been changed in the database but not in the buffer (Program buffer - see ST02). When you run the program, it checks to see if the same version that's in the buffer is in the database as well. It is finding 2 different versions of the SAPMSYST program, so you see the shortdump.
Hope this helps.
Tim
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
what does Transaction SICK tell you in the output?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
here is the detailed error that i am getting during se38 new prog creation.
how to solve this error?
Runtime Errors LOAD_FORMAT_ERROR
Date and Time 14.03.2007 13:14:04
-
-
ShrtText |
Format error when loading ABAP/4 program "SAPLSUGI". |
-
-
What happened? |
The current ABAP program had to be terminated because the |
ABAP processor detected an internal system error. |
The current ABAP program "SAPLSXSF" had to be terminated because the ABAP |
processor discovered an invalid system state. |
-
-
Error analysis |
The generated (load) version of the ABAP/4 program "SAPLSUGI" contains a |
format error. Possible causes are as follows: |
1) The line of table D010L with the key PROG = "SAPLSUGI" has |
been changed, either with ABAP/4 Native SQL or by other means. |
Since the system flagged the load version of program "SAPLSUGI" as invalid, |
restarting the program causes |
it to be regenerated. |
2) The tables D010L or D010LINF have been destroyed in the database |
and must therefore recreated. |
-
-
Trigger Location of Runtime Error |
Program SAPLSXSF |
Module type (FUNCTION) |
Module Name CHECK_EXIST_LIMU_FUNC |
-
User | Count |
---|---|
80 | |
24 | |
11 | |
9 | |
7 | |
6 | |
5 | |
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.