To find the component double click on the package name. The next winodws shows some additional information about the program
Enter the name of the application and select the field "Attributes" You can find the component via transaction SE38. If this is an SAP application you have to open an support ticket on the component which is responsible for this application. In our example the application "SAPLSBAL_DB_INTERNAL" generate the deadlock. To find the application which generate the deadlock you have to take a look on "client details" in the trace. In our case this is an application generated deadlock.
Current SQL Statement for this session (sql_id=774fy14dwxfya) -Īt first you should take a closer look in the deadlock graph and check the column "holds waits". If an 'X' is displayed instead at this point in the graph, it is NOT an Oracle deadlock. End of information for the OTHER waiting sessions. O/S info: user: adm, term:, ospid: 17034Īpplication name: SAPLSBAL_DB_INTERNAL, hash value=1574545675 Pid: 35 O/S info: user: oraprl, term: UNKNOWN, ospid: 16552 Information for the OTHER waiting sessions. Session 2213: obj - rowid = 001C9D47 - AAHJ1HAIFAAAl9SAAF Session 6428: obj - rowid = 001C9D47 - AAHJ1HANDAAA3fbAAH Resource Name process session holds waits process session holds waits The following information may aid in determining the deadlock: It is a deadlock due to user error in the design of an application or from issuing incorrect ad-hoc SQL. The following deadlock is not an ORACLE error. In our example the following deadlock trace was generated To analyze this file the following note is really helpful 84348 - Oracle deadlocks, ORA-00060
More info in file /oracle//saptrace/diag/rdbms/sm0//trace/_ora_c. The next step is to analyze the oracle alert.logįrom the alert.log you get the information that you can find more information in the created trace file(called deadlock trace) See line Mon Apr 10 16:36:27 2014 ORA-00060: Deadlock detected. The idea behind this topic is to gave you an short guide to analyze an ORA 00060 error, to find the relevant information in the ST22 dump and analyte the oracle alert.log and most important the oracle deadlock trace file.Īn dump was generated in ST22, database error text contains "ORA-00060: deadlock detected while waiting for resource"įrom the header of the dump you got the information that the deadlock have he following timestamp: 16:36:27
#Ora 00060 deadlock detected while waiting for resource how to#
This page gave an overview how to analyze an oracle deadlock.
0 kommentar(er)
