Vous êtes sur la page 1sur 1

Different Types of Dumps: ABAP, PROGRAM, SYSTEM

ABAP dump ASSIGN_TYPE_CONFLICT while data loading via DTP

This dump is very common with data load based on DTP (Data Transform Process).
You can observe you failed load in DTP Monitor as follows:
ABAP Runtime Errors - Dump analysis
Written by anon

An ABAP program can be terminated during runtime for a number of different reasons. The database table SNAPTID lists all existing runtime errors.
Use transaction ST22 to view the errors.
To allow clearer processing, the runtime errors are divided into categories:

Internal errors

Error in the VM -> can only be reported to SAP using an error message.

Errors in the ABAP runtime

The system was able to roughly determine the area in which the error occurred. Next, clarify whether it was triggered by
an internal error or by a programming error.

Errors in the screen runtime

Errors in the database interface
ABAP programming errors

Errors in the ABAP program, such as a division by zero or a catchable exception that was not caught.

Installation errors

These include, for example, inconsistencies between the kernel and the database. A typical installation error is therefore
the error

Resource bottleneck

Typical example: SYSTEM_NO_ROLL. The application no longer has sufficient memory available.

External errors

The error was caused by a call outside the system.

The code page of the operating system does not match the SAP system language
An incorrect logon attempt occurred when calling outside the SAP system (for example, RFC SDK).

End user errors

These errors include, for example, incorrect end user printer settings.

No error

The program was not terminated due to an error, but rather due to deliberately performed actions.
Example: If an administrator actively cancels a running transaction, the RABAX SYSTEM_CANCELED is thrown. In
cases like this, no error correction is required.

ST runtime errors

The error occurred during a Simple Transformation (ST). The cause is a programming error in the ST program.

Internal ST errors

The error occurred during a Simple Transformation (ST). There is an internal error in the ST VM.

XSLT runtime errors

The error occurred during the execution of an XSLT transformation.

ITS errors

The error occurred in ITS. These are usually HTMLB errors, however the error could also be due, for example, to a
resource error within the ITS



The problems with the dump STORAGE_PARAMETERS_WRONG_SET are mainly related to the general
restrictions of the 32bit OS. You can address up to 4GB of virtual memory. Each process in OS is running in
its own context and can address max. 4GB. The parameters which are related to heap memory' ie
abap/heap_area_dia, abap/heap_area_nondia, abap/heap_area_total are should be set to 2 GB. Common
approaches which we can take for this dump are:
a) Please use in the 'boot.ini' file the switch '/3GB' and restart your whole computer as described in the below
SAP Notes:
SAP Note 552209 - Maximum memory utilization for processes on NT/Win 2000
SAP Note 313347 - Windows NT, 2000, 2003: Editions and memory usage.
b) Another way to avoid this problem is to try to add more criteria to your report/program/transaction so that
there will be fewer entries that need to be retrieved from your database or buffers. This way, the system
would not need to use up much resource to complete the transaction. The query may have been quite big
already and the load cannot be accommodated. So please do add more criteria or options so that there will
less data to fetch.
c) To decrease the value of the parameters: rdisp/ROLL_SHM, rdisp/PG_SHM
d) Migrate to 64-bit OS (as per SAP Note 931024 and SAP Note 996600)