Session 137: obj - rowid = 00003AA0 - AAADqgAAAAAAAAAAAA Resource Name process session holds waits process session holds waits Information may aid in determining the deadlock: It is aĭeadlock due to user error in the design of an application The following deadlock is not an ORACLE error. Windows thread id: 5596, image: ORACLE.EXE (SHAD) With the Partitioning, OLAP, Data Mining and Real Application Testing options Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production Trace file E:\ORACLE\DEST\diag\rdbms\clientdev2\clientdev2\trace\clientdev2_ora_c The trace file's top portion is shown below:
But, is there are any DD views which has the information still? So, how do we find out? Now of course the DB is restarted. I cannot find any SQL which references the tables or columns in our application. If I know the SQL which caused the deadlock, then I know which procedures or even ad-hoc SQL I executed in SQL*Developer caused it. Problem is, looking at the trace file, I cannot find out which SQL caused the deadlock. When we requested the DBA to restart the DB, he sent us a trace file which says there was a deadlock. when you press execute for a procedure, the processing will continue for 1/2 hour, but without giving any result.
The procedures which took only a few seconds to run day-before yesterday, was not completing yesterday. It was difficult to work using SQL*Developer. 1.7K Training / Learning / Certification.165.3K Java EE (Java Enterprise Edition).7.9K Oracle Database Express Edition (XE).3.8K Java and JavaScript in the Database.
0 kommentar(er)
