Professional Documents
Culture Documents
Communication
27.09.2017 08:49:10 CET - Problem Description: Ashutosh Tiwari (S0017236070)
Hello team,
Short Text
SQL error "SQL code: 60" occurred while accessing table "VEKP".
What happened?
Database error text: "SQL message: ORA-00060: deadlock detected while waiting
for resource"
Note # 2027810 was suppose to resolve this issue but we still have
Regards
Ashutosh Tiwari
1. Cannot be replicated
Please be informed that after analysis I am routing your incident to BC-DB-ORA component for further
investigation.
Best Regards,
Zsombor Danka
SAP Product Support
Dear Customer,
Please be informed that your incident is currently under processing by BC-DB-ORA (Oracle) Team.
For further analysis regarding the encountered ORA-00060 deadlock error, please also provide us
the following additional information:
- detailed information about encountered issue and exact steps executed so far
- the Oracle alert log
- the corresponding trace files for ORA-00060/deadlock error (derived from Oracle alert log
that will provide further details)
- the SM21 system log
- the ST22 runtime error log if more
Please also check carefully the folllowing SAP knowledge base article and SAP Note:
1872040 - Handling ORA-00060 error - application deadlock issue
84348 - Oracle deadlocks, ORA-00060
Best regards,
Bíborka Gréta Tóth
SAP Product Support
-------------------------------------------------
SAP Oracle WIKI: http://wiki.scn.sap.com/wiki/display/ORA/Oracle
Do you Facebook or Twitter? Please visit our SAP Product Support sites
where you'll get all the latest updates on our products!
https://www.facebook.com/SapProductSupport
https://twitter.com/SAPSupportHelp
*****************************************************************************************
Have you heard about our Expert Chat?
Please check out the following links and find out on how to start benefiting from our
Brand New Support Channel:
https://blogs.sap.com/2016/06/14/get-faster-answers-to-your-support-questions-with-chat/
2213344 - Starting an Expert Chat with SAP Support [video]
2392095 - Technical requirements to create a successful Expert Chat Session with SAP Product Support
*****************************************************************************************
Hello,
Regards
Ashutosh Tiwari
Thank you for the information provided so far. I have checked the provided logfiles and I found
deadlock graph below:
***********************************************************************************************************
Deadlock graph:
-------------Blocker(s)------------ -------------Waiter(s)-------------
Resource Name process session holds waits process session holds waits
TX-001D001B-006D856B... 463 843 X 46 1243 S
TX-01020003-003CAD40... 46 1243 X 463 843 X
...
----- Information for the OTHER waiting sessions -----
Session 1243:
application name: SAPLZLE_TEXTS_ODN, hash value=232805421
current SQL:
UPDATE "STXH" SET "TDTITLE"=:A0,"TDFRELES"=:A1,"TDFUSER"=:A2,"TDFDATE"=:A3,
"TDFTIME"=:A4,"TDLRELES"=:A5,"TDLUSER"=:A6,"TDLDATE"=:A7,"TDLTIME"=:A8,
"TDVERSION"=:A9,"TDSTYLE"=:A10,"TDFORM"=:A11,"TDHYPHENAT"=:A12,
"TDTRANSTAT"=:A13,"TDOSPRAS"=:A14,"TDMACODE1"=:A15,"TDMACODE2"=:A16,
"TDTXTLINES"=:A17,"TDREF"=:A18,"TDREFOBJ"=:A19,"TDREFNAME"=:A20,
"TDREFID"=:A21,"TDTEXTTYPE"=:A22,"TDCOMPRESS"=:A23,"TDOCLASS"=:A24,
"MAGEW"=:A6,"TARAG"=:A7,"GEWEI"=:A8,"BTVOL"=:A9,"NTVOL"=:A10,"MAVOL"=:A11,
"TAVOL"=:A12, "VOLEH"=:A13,"ANZGL"=:A14,"ERNAM"=:A15,"ERDAT"=:A16,
"ERUHR"=:A17,"AENAM"=:A18,"AEDAT"=:A19,"AEZET"=:A20,"SORTL"=:A21,
"VEGR1"=:A22,"VEGR2"=:A23,"VEGR3"=:A24,"VEGR4"=:A25,"VEGR5"=:A26,
"VHILM"=:A27,"LAENG"=:A28,"BREIT"=:A29,"HOEHE"=:A30,"MEABM"=:A31,
"ERLKZ"=:A32,"GEWTO"=:A33,"VOLTO"=:A34,"MEINS"=:A35,"VOLEH_MAX"=:A36.....
***********************************************************************************************
This indeed indicates deadlock on tables "STXH" and"VEKP" as per SAP Note 84348. From
database point of view, in most cases shared lock is caused by INITRANS/MAXTRANS setting
for the object is too small and it can not handle the number of concurrent transactions.
As per SAP Note #84348 if deadlock occurs when jobs are being executed in parallel (usual
data loads), the INITRANS value should be set to maximum number of parallel running jobs.
Otherwise, 20 is an appropriate value. Also if value for MAXTRANS is other than 255, increase
this value to at least adjusted INITRANS value. Also the new parameters only affect new blocks
Contacts
Ashutosh Tiwari
REPORTER CET +41-779705974 ashutosh.tiwari@richemont.com
(S0017236070)
Attachments
File File
File Name Description Created By Created On
Type Size
KBA/SAP Notes
Changed
Changed On Changed By Action Old Value New Value
At
09:41:29
SAP Component BC-ABA BC-DB-ORA
CET
09:41:29 Memo/Text
SAP Info for Customer
CET changed
09:56:31
SAP Status Sent to SAP Customer Action
CET
09:56:31 Memo/Text
SAP Reply
CET changed
Monday 11:37:02
SAP Status Sent to SAP Customer Action
09.10.2017 CET
11:37:02 Memo/Text
SAP Reply
CET changed