Databases Reference
In-Depth Information
The information provided by the trace file also contains the session, the process, and the SQL
statement that caused the deadlock for each process involved. In the following screenshot
you can observe the
UPDATE
statement executed in
SESSION
2
and the
UPDATE
statement
executed in
SESSION
1
, for our example:
These details are useful in identifying the statements that caused the issue, and you can
change the application accordingly.
When a deadlock occurs it is also logged in the database alert log. In the next screenshot
you can see the line in the alert log that identifies the trace file in which the details about
the issue are saved, in our example
TESTDB_ora_6424.trc
:
