ABAP/4 processor: DBIF_DSQL2_SQL_ERROR ... help me out

[Former Member]

Hello ppl ,

below are the details of the problem i am facing , looking forward to some answers ... thanks in advance ...

Runtime Errors DBIF_DSQL2_SQL_ERROR

Except. CX_SY_NATIVE_SQL_ERROR

Date and Time 13.10.2008 11:15:23

Short dump has not been completely stored (too big)

The error "-60" occurred in the current database connection "LCA".

What can you do?

Note down which actions and inputs caused the error.

To process the problem further, contact you SAP system

administrator.

Using Transaction ST22 for ABAP Dump Analysis, you can look

at and manage termination messages, and you can also

keep them for a long time.

How to correct the error

Database error text........: "POS(1) Work rolled back: tExcept 18757 in

APS_ORDER_GET_"

Database error code........: "-60"

Triggering SQL statement...: "EXECUTE PROCEDURE "APS_ORDER_GET_DATA""

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"

"/SAPAPO/SAPLOM_PLANNING" or "/SAPAPO/LOM_PLANNINGU07"

"/SAPAPO/OM_ORDER_GET_DATA"

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

"/SAPAPO/OM_ORDER_GET_DATA" "(FUNCTION)", or its possible occurrence must be declared in the

RAISING clause of the procedure.

To prevent the exception, note the following:

Information on where terminated

Termination occurred in the ABAP program "/SAPAPO/SAPLOM_PLANNING" - in

"/SAPAPO/OM_ORDER_GET_DATA".

The main program was "/SAPAPO/BACKGROUND_SCHEDULING ".

In the source code you have the termination point in line 201

of the (Include) program "/SAPAPO/LOM_PLANNINGU07".

The program "/SAPAPO/SAPLOM_PLANNING" was started as a background job.

Job Name....... "BI_PROCESS_ABAP"

Job Initiator.. "KPPNKS432623"

Job Number..... 10324500

The termination is caused because exception "CX_SY_NATIVE_SQL_ERROR" occurred

in

procedure "/SAPAPO/OM_ORDER_GET_DATA" "(FUNCTION)", but it was neither handled

locally nor declared

in the RAISING clause of its signature.

The procedure is in program "/SAPAPO/SAPLOM_PLANNING "; its source code begins

in line

1 of the (Include program "/SAPAPO/LOM_PLANNINGU07 ".

[Former Member]

hi Vinay Jain,

When do you get this error? The error you get is a low level database error, the trigger can be many.

I got the same error when consistency checks for the LC was performed. After a lot of effort we found that this happens when two different connections access the database & tries to update at the same time.

SAP Global support suggested (for my problem) to restart the system (with the LC) & run the Consistency check (OM17), this resolved my issue. You can also follow the same, might help you too.

[Former Member]

Hi Vinay,

Please check OSS Note 1035034 - error DBIF_DSQL2_SQL_ERROR in /SAPAPO/TS_PAREA_INITIALIZE.

"

You launch /SAPAPO/TS_PAREA_INITIALIZE in order to initialize the planning area.

The number of CVCs is huge and the process ends with the error DBIF_DSQL2_SQL_ERROR.

This problem might be related to memory shortage (heap memory)."

If it is not suitable to your sitaution, please check other oss note with same error.

Manish

[Former Member]

thanks this was helpful .. but the problem is still not solved ... we have updated the kernel and applying scm patch 14 ... it could be a memory shortage .. lets see ... will keep this thread updated .

[Former Member]

What version of SCM you are using ?

This bgd job failure could be during consistency check of resources. Check your system parameters settings.