Dump in TCOD /SAPAPO/SDP94 ... any Idea ?

[Ganimede-Dignan]

Hi forum,

have you got any idea about this dump ?

Regards.

Runtime Errors DBIF_DSQL2_SQL_ERROR

Exception CX_SY_NATIVE_SQL_ERROR

Date and Time 13.03.2008 11:30:34

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_RIW"

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_TIMESERIESU86"

"/SAPAPO/OM_TS_DATA_SET_RIW"

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

declared in the

RAISING clause of the procedure.

To prevent the exception, note the following:

System environment

SAP-Release 700

Application server... "server"

Network address...... "10.1.1.111"

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

Database type..... "ORACLE"

Database name..... "NSD"

Database user ID.. "SAPSR3"

Char.set.... "C"

SAP kernel....... 700

created (date)... "Jan 29 2007 00:36:16"

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

Database version. "OCI_10201_SHARE (10.2.0.1.0) "

Patch level. 95

Patch text.. " "

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

SAP database version. 700

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

Memory consumption

Roll.... 16192

EM...... 37708560

Heap.... 0

Page.... 114688

MM Used. 26913728

MM Free. 6600800

User and Transaction

Client.............. 100

User................ "MYUSER"

Language key........ "I"

Transaction......... "/SAPAPO/SDP "

Transactions ID..... " "

Program............. "/SAPAPO/SAPLOM_TIMESERIES"

Screen.............. "/SAPAPO/SAPMMSDP 0100"

Screen line......... 42

Information on where terminated

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

"/SAPAPO/OM_TS_DATA_SET_RIW".

The main program was "/SAPAPO/SAPMMSDP ".

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

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

The termination is caused because exception "CX_SY_NATIVE_SQL_ERROR" occurred

in

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

locally nor declared

in the RAISING clause of its signature.

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

begins in line

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

[keiji_mishima · Accepted solution]

Hi Ganimede Dignan

Regarding on your short dump, it occur during DB access (live Cache access).

<If you look at FM /SAPAPO/OM_TS_DATA_SET_RIW,

you can see COM routin SAPTS_SET_DATA_RIW . This indicate liveCache access>.

Normally kind of your dump occur due to memory shortage of you liveCache heap area.

So I recommend you to contact your liveCache administrater and check parameter setting of OMS_HEAP_LIMIT and historical heap consumption.

(If your liveCache administrater check livecache kernel log like knldiagerr, he or she will see error message of heap shortage).

I hope this information help you.

Best Regards

Keiji

[Ganimede-Dignan · Accepted solution]

Hi,

>So I recommend you to contact your liveCache administrater and check parameter setting of >OMS_HEAP_LIMIT and historical heap consumption.

>(If your liveCache administrater check livecache kernel log like knldiagerr, he or she will see error >message of heap shortage).

OMS_HEAP_LIMIT was 1GB now I've change to 4 GB ... and it should be ok now, we check also with user, we are in early step of a SCM project.

Regards.

Ganimede Dignan.

[Former Member]

It's a SAP GUI problem. You must install the SAP GUI - SCM add on.

Do not consider this message.

Edited by: Marcelo Tescari on Mar 24, 2008 12:30 PM

[Ganimede-Dignan]

Hi,

all users have got full sapgui installation... and it happends in 6.40 and 7.10 SAPgui.

Thank you for your post.

Regards.

Ganimede Dignan.

[Former Member]

Please try to run inconsistency check programs

It looks like that you are having some livecache error

[Ganimede-Dignan]

>Please try to run inconsistency check programs

>

>It looks like that you are having some livecache error

Excuse me, I'm SCM newbie... where can I find docu about it ? or other indication about it ?

Regards.

[somnath_manna]

Goto txn code /SAPAPO/MSDP_ADMIN

Select your planning area associated with the planning book you are trying to access.

See if the Planning Area is Green or Red. Assuming its green

Double click on the planning area, goto Menubar Extras >> Consistency Checks >> Time Series (if its DP Planning Area) / Initialised Planning Versions (if its SNP).

In next screen the planning area is automatically picked up - enter the Planning Version (mostly it would be 000) select Options - Repair, Check liveCache Anchor, Check SNP Master Data (if SNP Planning Area) and Execute.

After successful execution you go back to /SAPAPO/SDP94 txn.

If still there is a problem check with your BASIS team if liveCache connection LCA is up and running.

Somnath

[Ganimede-Dignan]

Hi,

no problem from check....

>If still there is a problem check with your BASIS team if liveCache connection LCA is up and running.

>Somnath

From LC10 LCA is up and running.

The problem occur only with some selection not for all material.

Regards.

[Former Member]

Hi

SQL 600 errors usually occur with data problems in my experience, also that routine it is failing on is writing data to livecache time series.

I would run /sapapo/om17 consistency checks for livecache and tick both "Product-Location Combinations" and "DP Time Series" boxes. This should check for inconsistencies in Livecache anchors etc.

Regards

Ian

[Ganimede-Dignan]

Hi,

the dump happends after 03:30 PM ... not all days, the system reastart each night due a off-line backup.

Does it should happen due a small buffer into istance profile ?

Regards.

Ganimede DIgnan.

[Former Member]

Hi

Do you know if you have the user parameters /SAPAPO/TS_QUEUE_UPD and /SAPAPO/TS_AUTO_UPD enabled in your system so that master data queues are not updated on planning loads. See Note 928972 for further information:

[928972 - Don't check master data changes in SNP interactive planning|https://service.sap.com/sap/support/notes/928972]

This stops the checks on the master data and can cause dumps if the livecache master data is inconsistent as a result. It improves performance considerably but has side effects.

Regards

Ian

[Ganimede-Dignan]

No one user has got this parameters setted.

Regards.