Symptom
SAP liveCache procedure call fails with DBIF_DSQL2_SQL_ERROR runtime error.
(To check complete runtime error use transaction ST22)
Category Installation error
Runtime Errors DBIF_DSQL2_SQL_ERROR
Except. CX_SY_NATIVE_SQL_ERROR
Date and Time 07.03.2018 07:34:30
Short Text
SQL error 600 occurred while executing Native SQL.
What happened?
Error 600 has occurred on the current database connection "LCA".
Database error text: POS(1) Work rolled back: BAD_ALLOCATION in SAPTS_UPDATE_
Triggering SQL statement: "EXECUTE PROCEDURE SAPTS_UPDATE_TIMESERIES"
[...]
System environment
SAP Release..... 750
SAP Basis level 0007
Application server... appserver100
Network address...... 192.168.0.100
Operating system... Linux
Release.............. 2.6.32-696.18.7.el6.
Hardware type....... x86_64
Character length..... 16 Bits
Pointer length........ 64 Bits
Work process number... 18
Shortdump setting. full
Corresponding work process trace dev_w18 of affected application server:
C Wed Mar 7 07:34:30:542 2018
C *** ERROR => execute() of C_0019, #rec=0, rc=1, rcSQL=600
[dbsdbsql.cpp 2062]
C {root-id=005056B668B71EE888BA2E3FEB8A280C}_{conn-id=00000000000000000000000000000000}_0
C *** ERROR => EXECUTE C_0019 on connection 2, rc=600
[dbslsdb.cpp 9942]
C SQLCODE : 600
C SQLERRTEXT : POS(1) Work rolled back: BAD_ALLOCATION in SAPTS_UPDATE_
C sc_p=7f68fd8e9408,no=19,idc_p=(nil),con=2,act=1,slen=59,smax=256,#vars=5,stmt=7f68fe7cdd10,table=SAPTS_UPDATE_TIMESERIES
C CALL SAPTS_UPDATE_TIMESERIES ( ? , ? , ? , ? , ? ) ;
B ***LOG BY2=> sql error 600 performing EXE [dbds 301]
B ***LOG BY0=> POS(1) Work rolled back: BAD_ALLOCATION in SAPTS_UPDATE_ [dbds 301]
In this example the runtime error DBIF_DSQL2_SQL_ERROR occurred during the execution of the liveCache procedure SAPTS_UPDATE_TIMESERIES.
Please note that the name of the liveCache procedure call can be different.
Read more...
Environment
SCM systems with MaxDB based liveCache.
Product
Keywords
[ここに キーワード を入力してください...] , KBA , BC-DB-LCA , liveCache Applications , BC-DB-LVC , liveCache , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.