Reg:SCM APO DUMP DBIF_DSQL2_SQL_ERROR

[Former Member]

Hi,

this is suresh.Could you suggest me applicable note

Runtime Errors DBIF_DSQL2_SQL_ERROR

Exception CX_SY_NATIVE_SQL_ERROR

-

---

Short text

An SQL error occurred when executing Native SQL.

-

---

-

---

What happened?

The error 600 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: BAD_ALLOCATION in

SAPTS_SET_DAT"

Database error code........: 600

Triggering SQL statement...: "EXECUTE PROCEDURE SAPTS_SET_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_TIMESERIES" or "/SAPAPO/LOM_TIMESERIESU90"

"/SAPAPO/OM_TS_DATA_SET"

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_TS_DATA_SET" "(FUNCTION)", or its possible occurrence must be

declared in the

RAISING clause of the procedure.

| To prevent the exception, note the following:

[former_member187488]

Hello,

The job has aborted with DBIF_DSQL2_SQL_ERROR because the maximum retention time in liveCache (MAX_RETENTION_TIME) has been overstepped. This means that the job has run for over many hours (as defined in MAX_RETENTION_TIME) without a COMMIT in liveCache. Such long running transactions can create a lot of history data in liveCache and theirruntime is therefore limited by the liveCache parameter MAX_RETENTION_TIME.

Please try to make your job smaller if possible.

Best Regards,

Ada

[former_member209769]

Hi Suresh,

-> What action/job, etc is triggering this dump?

-> In ST22, you would have the section "where triggered". Pls copy paste that information also.

Thanks - Pawan