on 08-24-2010 7:31 AM
Hi Experts,
We recieve this error every day for a particular procedure APS_ORDER_CREATE.
I checked on various forums & the solution offered was to increase the heap size .
But i think my error is occuring because of different reason.
i checked the trace file lcapo_com_trace_01.txt & this what it shows.
#!!# OmsCancelled: DbpError exception in APS_ORDER_CREATE ##########*
0x00000005 # COM build 70009.3 CL 401527 (7.0_REL) on AIX RS6000 5.1
0x00000005 OMS_Session.cpp:3644 no. = -102 errorKind = 0 (SQL statement cancelled @
0x00000005 ), OID = OID 2147483647.0 [0], cancelled by program = true , provoked by test kernel = false, curre@
0x00000005 nt OMS version I}cvbCfi2W7X08002je89W exists.
0x00000005 ### return code entry ###
0x00000005 errorcode = -1000102
What is an OMS version ? some kind of view produced by a SCM application
Also on SDN i found out :
Consistent Views and OMS versions
An APO/SCM application can create a so-called OMS version (f.e. when transactional simulations are used). Contrary to a Consistent View an OMS version can exist after the end of a transaction and can be used by the APO/SCM application further on. An OMS version may exist far beyond the end of a transaction. Only one transaction can work with the OMS version at the same time.
is it happening because of above reason?
Is their any solution for this?
Regards,
Ameya Joshi
Hello ,
102 error in liveCache means that workprocess on SAP side was canceled so in order to find reason (and solution) for error
102 you need to look in the worprocess trace (dev_w*) and find out why it was canceled
Regards
Ivan
Edited by: Ivan Levrinc on Aug 25, 2010 11:04 AM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ivan,
I checked in the WP trace , it suggests that user requested cancel of current operation, thats whay the error is occuring i guess
M ThAlarmHandler (1)
M ThAlarmHandler: set CONTROL_TIMEOUT/DP_CONTROL_JAVA_EXIT and break sql
C User requested cancel of current SQL statement on connection 1
C CANCEL of the current statement was sent successfully
B db_sqlbreak() = 0
M program canceled
M reason = max run time exceeded
M user = BWALEREMOTE
M client = 100
M terminal =
M report = /SAPAPO/SAPLOM_PLANNING
M ThAlarmHandler: return from signal handler
C
C Wed Sep 1 03:09:13 2010
C *** ERROR => execute() of C_0677, #rec=0, rc=1, rcSQL=600 (POS(1) Work rolled back: OmsCancelled: DbpError -102 err)
[dbsdbsql.cpp 1679]
C *** ERROR => EXECUTE on connection 1, rc=600 (POS(1) Work rolled back: OmsCancelled: DbpError -102 err)
[dbdssdb.cpp 2173]
C sc_p=0x114684188,no=677,idc_p=(nil),con=1,act=1,slen=121,smax=256,#vars=0,stmt=0x114ed5c90,table= "APS_ORDER_CREATE"
C CALL USER."APS_ORDER_CREATE" ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, \
C ?, ?, ?, ?, ?, ?, ? );
C *** ERROR => dbdssdb: SQL Error 600, Message: POS(1) Work rolled back: OmsCancelled: DbpError -102 err
[dbdssdb.cpp 2403]
B ***LOG BY2=> sql error 600 performing EXE [dbds#2 @ 364] [dbds 0364 ]
B ***LOG BY0=> POS(1) Work rolled back: OmsCancelled: DbpError -102 err [dbds#2 @ 364] [dbds 0364 ]
Thanks Ivan , i was going to adivse my collegue to increase the heap memory.
But any how what this actual explanation of this error?
Regards,
Ameya
Edited by: Ameya Joshi on Sep 1, 2010 12:00 PM
Hello Ameya Joshi,
1. As you saw in the dev log the liveCache application was canceled due u201Cmax run time exceededu201D.
2. The liveCache application could run long time due the performance issues in liveCache or APO database or Network issues or application scenario problems or inconsistencies on the system or u2026
=>
I recommend to create the SAP message if you need further assistance on this issue.
Thank you and best regards, Natalia Khlopina
User | Count |
---|---|
88 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.