on 08-10-2011 4:24 AM
Hi,
We are using SCM - 5.10 Live cache 7.704, ECC-6.0
While we are running consistency check program, We are getting the following dump,
DBIF_DSQL2_SQL_ERROR
Exception CX_SY_NATIVE_SQL_ERROR
Date and Time 07/31/2011 06:40:12
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_CLEAN_O"
Database error code........: 600
Triggering SQL statement...: "EXECUTE PROCEDURE SAPTS_CLEAN_OBJECTS"
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_TIMESERIESU32"
"/SAPAPO/OM_TS_OBJECTS_CLEAN"
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_OBJECTS_CLEAN" "(FUNCTION)", or its possible occurrence must be
declared in the
RAISING clause of the procedure.
To prevent the exception, note the following:
Kindly suggest.
Hello,
The error means that the LiveCache ran out of Heap memory, which is a memory area for LiveCache commom routines usage.
Frequent heap shortages accross all application scenarios indicate that the liveCache database instance generally does not possess enough physical memory to perform the required tasks. Consult note 337445 to find out more about liveCache storage management and how to configure a liveCache correctly, especially the data cache and the liveCache parameter OmsMaxHeapSize (formerly OMS_HEAP_LIMIT).
In some cases it simply might be necessary to add more physical memory (RAM) to the liveCache server. You can also opt to trade liveCache performance for memory by reducing the size of liveCache's data cache.
It could also be caused by memory leaks, which in most cases can be reduced by applying a newer LiveCache patch or regularly bounce the livecache server.
Best Regards,
Ada
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Could you please tell what is memory leak and what live cache patch needs to be applied to resolve this issue, we are having values of OmsMaxHeapSize.
The Physical main memory = 15.7 GB
Current Value (OmsMaxHeapSize)= 2097152 KB..We are running Live cache in which application server is present
Kindly suggest if the value of heap limit is increased , whether other values will be affected.?
Thanks,
Vijayashree.R
Hi Rajendran Vijayashree ,
please consult note 337445 to find out more about liveCache storage management and how to configure a liveCache correctly, especially the data cache and the liveCache parameter OmsMaxHeapSize (formerly OMS_HEAP_LIMIT).
I hope this helps.
Regards,
Tibor
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
13 | |
4 | |
3 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.