Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

DBIF_DSQL2_SQL_ERROR Dump error generating

HI All,

Can some one tell me how can i solve this Below abap dump error,

Database error text........: "SQL0150N The target fullselect, view, typed

table, materialized query table, or staging table in the INSERT, DELETE,

UPDATE, or MERGE statement is a target for which the requested operation is

not permitted. SQLSTATE=42807"

Database error code........: "-150"

Triggering SQL statement...: "insert into "AQDB" ( "MANDT", "RELID", "SRTFD",

"SRTF2", "LOEKZ", "SPERR", "AEDAT", "USERA", "PGMID", "BEGDT", "ENDDT",

"CLUSTR", "CLUSTD" ) values ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ,

? )"

Internal call code.........: "[DBDS/NEW DSQL]"

Please check the entries in the system log (Transaction SM21).

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following

keywords:

"DBIF_DSQL2_SQL_ERROR" "CX_SY_NATIVE_SQL_ERROR"

"SAPLAQNF" or "RSAQIEXN"

"NEXT_NUMBER"

If you cannot solve the problem yourself and want to send an error

notification to SAP, include the following information:

1. The description of the current problem (short dump)

To save the description, choose "System->List->Save->Local File

(Unconverted)".

2. Corresponding system log

Display the system log by calling transaction SM21.

Restrict the time interval to 10 minutes before and five minutes

after the short dump. Then choose "System->List->Save->Local File

(Unconverted)".

3. If the problem occurs in a problem of your own or a modified SAP

program: The source code of the program

In the editor, choose "Utilities->More

Utilities->Upload/Download->Download".

4. Details about the conditions under which the error occurred or which

actions and input led to the error.

The exception must either be prevented, caught within proedure

"NEXT_NUMBER" "(FORM)", or its possible occurrence must be declared in the

RAISING clause of the procedure.

To prevent the exception, note the following:

what could be the reason please help me

System environment

SAP-Release 700

Application server... "wpd-tech-sys"

Network address...... "192.168.2.218"

Operating system..... "Windows NT"

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

Hardware type........ "2x AMD64 Level"

Character length.... 16 Bits

Pointer length....... 64 Bits

Work process number.. 0

Shortdump setting.... "full"

Database server... "wpd-tech-sys"

Database type..... "DB6"

Database name..... "POC"

Database user ID.. "SAPPOC"

Char.set.... "C"

SAP kernel....... 700

created (date)... "Jan 24 2008 01:15:15"

create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"

Database version. "DB6_81 "

Patch level. 144

Patch text.. " "

Database............. "DB6 08.02., DB6 09."

SAP database version. 700

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

NT 6.0"

Memory consumption

Roll.... 16192

EM...... 8379680

Heap.... 0

Page.... 65536

MM Used. 2454880

MM Free. 1732336

Thnx & Regards

Zam

Edited by: zamu on Nov 6, 2008 9:38 AM

Former Member

Helpful Answer

by
Not what you were looking for? View more on this topic or Ask a question