Databases Reference
In-Depth Information
10. Show the parameter
USER_DUMP_DEST
:
SHOW PARAMETER USER_DUMP_DEST
11. Use OS commands to see the trace file and the alert log in which the deadlock
is recorded:
HOST
cd /u01/app/diag/rdbms/testdb/TESTDB/trace/
ls -ltr TESTDB_ora*.trc
more < TESTDB_ora_5997.trc
tail alert_TESTDB.log
exit
How it works...
In steps 2 and 4 we update two different rows in the
CUSTOMERS
table from two different
sessions. As we can see in the following screenshots, the transactions are not locked due
to this operation:
In step 5 we try to update, in
SESSION
1
, the same row updated above in
SESSION
2
. The
transaction in
SESSION
2
is still active, so the
SESSION
1
will wait until the
SESSION
2
transaction ends, as shown in the following screenshot:
