cancel
Showing results for 
Search instead for 
Did you mean: 

ABAP RUN TIME ERROR

Former Member
0 Kudos

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.

Accepted Solutions (1)

Accepted Solutions (1)

markus_doehr2
Active Contributor
0 Kudos

What kernel patch are you using? Try the latest patch.

Don´t write in CAPITALS, this means, that you are shouting at people.

--

Markus

Former Member
0 Kudos

can you please tell me how to install latest kernel?

waiting

Khalil

markus_doehr2
Active Contributor
0 Kudos

Check Note 19466 - Downloading SAP kernel patches - there you will find the place to download and how to install them.

--

Markus

Former Member
0 Kudos

unfortunately i don't have the access to sap service market place. hence i can not download 19466 document.

is there any other place where i can download this document?

Cheers

Khalil.

markus_doehr2
Active Contributor
0 Kudos

Notes and kernel patches are available on the service marketplace only - you need access there to get the notes as well as the patches itself.

No other download location...

--

Markus

Answers (3)

Answers (3)

Former Member
0 Kudos

good suggestions

Former Member
0 Kudos

Hi,

Iam new to this forum can u tell me how you solved the issue

former_member204746
Active Contributor
0 Kudos

simply follow Tim Hild's answer above, he clearly explains what to do.

Former Member
0 Kudos

Hi,

First what i have to do

I have to run ST22 when can i get D010L AND D010LINF tables

former_member204746
Active Contributor
0 Kudos

pradeep, please open a new topic/thread

Former Member
0 Kudos

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

Former Member
0 Kudos

what does Transaction SICK tell you in the output?

Former Member
0 Kudos

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

-


Former Member
0 Kudos

when I run transaction 'sick' it does not give me any error. and says " no error reported "

cheers

Khalil

former_member204746
Active Contributor
0 Kudos

table D010L contains ABAP LOADS.

try running SGEN and see if this fixes your issue.

good luck.

Former Member
0 Kudos

hi,

Can you let me know, how you solved ABAP_RUNTIME_ERROR and also how to solve table d010l and d010linf destroyed can be solved.

Thanks

Pradeep