Symptom
-
Deadlock situation is found on SM50 or SM66 transactions, showing work processes accessing NRIV table.
-
To find out which object is involved in the deadlock situation, follow this path:
- T-code AL11
- DIR_HOME option
- Click on 'Search for Character Strings in the Displayed Files (Shift) + F1
- Search for 'get from object' (that is part of the work process trace file)
Errors like M *** WARNING => ThNoGet: get from object (cli/obj/subobj/range = <clnt>/<object> / <subobject> /<range>) returned rc 15 are going to be shown.
- Work process trace file (dev_wX) shows:
M *** ERROR => ThINoAddNum: overflow [thxxnum.c 4266]
M {root-id=2C768A5D42941EEA91DA3F1B4F913C8D}_{conn-id=00000000000000000000000000000000}_12345
M ThINoResetLocEntry: reset entry <clnt>/<object> / <subobject> /<range>
M ThNoGet2: Return number range rc 15
M *** WARNING => ThNoGet: get from object (cli/obj/subobj/range = <clnt>/<object> / <subobject> /<range>) returned rc 15
Involved Number Range object shown on the trace(<object>) has defined Main Memory buffering; and it’s set as No Rolling (meaning that “No rolling” flag on SNUM configuration is marked).
- Work process trace file (dev_wX) may also show:
I *** WARNING => MtxLock 0x5f568e8f00ab3 NOBUFENT owner=ABAP_WP_XX deadlock ? [mtxxx.c 645]
Read more...
Environment
SAP NetWeaver system
Product
SAP NetWeaver all versions
Keywords
ThINoAddNum, ThINoAddNum: overflow, rc 15,
EMMA_CASE, EMMA_RUNID
, KBA , BC-SRV-NUM , Number Range Management , BC-CST-NU , Number Range Buffer , How To
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.
SAP Knowledge Base Article - Preview