Dump

[Former Member]

Hi all expert

i got a dump in prd server. when i was incresing table space size.

i have incresed the size when i check st22 there were dump. as per below menstioned

Runtime Error LIST_NO_PAGETAB

Date and Time 01.09.2009 11:29:22

-

---

-

---

ShrtText

Internal error: System table for list processing is empty.

-

---

-

---

What happened?

The current ABAP program had to be terminated because the

ABAP processor detected an internal system error.

The current ABAP program "RSM04000_ALV" 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

You attempted to manipulate a list for which no directory

of individual pages has been created due, e.g. due to incorrect index.

example, to an incorrect index.

-

---

-

---

How to correct the error

You may able to find an interim solution to the problem

in the SAP note system. If you have access to the note system yourself,

use the following search criteria:

"LIST_NO_PAGETAB" C

"RSM04000_ALV" or "RSM04000_ALV"

"MODUS_LISTE"

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....... "sapgrp"

Network address.......... "192.168.1.202"

Operating system......... "Windows NT"

Release.................. "5.2"

Hardware type............ "4x IA64 Level 3"

Character length......... 8 Bits

Pointer length........... 64 Bits

Work process number...... 2

Short dump setting....... "full"

Database server.......... "ECCPRD02"

Database type............ "ORACLE"

Database name............ "HOP"

Database owner........... "SAPHOP"

Character set............ "English_United State"

SAP kernel............... "640"

Created on............... "Mar 21 2007 22:46:25"

Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"

Database version......... "OCI_920_SHARE "

Patch level.............. "175"

Patch text............... " "

Supported environment....

Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE

10.2.0.."

SAP database version..... "640"

Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"

Memory usage.............

Roll..................... 16128

EM....................... 6265152

Heap..................... 0

Page..................... 90112

MM Used.................. 2267392

MM Free.................. 862192

SAP Release.............. "640"

-

---

-

---

User and Transaction

Client.............. 500

User................ "HIT_BASIS"

Language key........ "E"

Transaction......... "SM04 "

Program............. "RSM04000_ALV"

Screen.............. "SAPMSSY0 0120"

Screen line......... 8

-

---

-

---

Information on where terminated

The termination occurred in the ABAP program "RSM04000_ALV" in "MODUS_LISTE".

The main program was "RSM04000_ALV ".

The termination occurred in line 614 of the source code of the (Include)

program "RSM04000_ALV"

of the source code of program "RSM04000_ALV" (when calling the editor 6140).

-

---

[Former Member · Accepted solution]

Hi ,

|User and Transaction | | Client.............. 500 | | User................ "HIT_BASIS" | | Language key........ "E" | | Transaction......... "SM04 " | | Program............. "RSM04000_ALV" | | Screen.............. "SAPMSSY0 0120" | | Screen line......... 8 | ---------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------------- |Information on where terminated | | The termination occurred in the ABAP program "RSM04000_ALV" in "MODUS_LISTE". | | The main program was "RSM04000_ALV ". | | | | The termination occurred in line 614 of the source code of the (Include) | | program "RSM04000_ALV" | | of the source code of program "RSM04000_ALV" (when calling the editor 6140). | ----------------------------------------------------------------------------------------------------

This dump is not due to extend tablespace rather its clearlt saying that in your Client.............. 500 | | User................ "HIT_BASIS" is the issue.

Kindly check with this user if he is running some reports or debugging program in SM04 as indicated in logs provided by you.

Thanks..

mohit

Edited by: mohit gupta on Sep 2, 2009 7:48 AM

[Former Member]

what is current BASIS SP level ? and I guess, as this dump shows, you have SAP release 640

and as the dump shows, it occurred in tcode SM04, so when you put RSM04000_ALV keyword in Notes Search in marketplace, it shows 3-4 SAP Notes related to this dump and SM04. If we can have a look on those as per your sap release and level ?

[Former Member]

dear anjali

my current BASIS SP level is sapkb64021 and SAP release 640,

but why did i get this dump.

Rajesh

[Former Member]

Reproducing the error might help here to know the reason.

We can monitor the frequency of this dump and check whether the dump occurs only for SM04 or for other tcodes too. and if those 3-4 notes and their related notes help, then we can try out to reproduce the problem with the steps given in the notes in the section 'Symptom' or 'Reason'

It will give us an idea, if those dumps are due to tablespace thing or due to some other reasons

[Former Member]

after this dump i did not get same dump till now

sm04 is used for user checking,

[Former Member]

'after this dump i did not get same dump till now'

ok, good. Means, it's not due to tablespace extend and seems to be specific only to SM04.

So, if you still want to analyze the dump and the reason, you have to some digging as per our ongoing discussion.

[Former Member]

Hi,

According to you dump, you had problem in Work process number...... 2

You can check the log file in \usr\sap\<ins>\DVEBMGS<inst_number>\work\dev_w2

And see what happened