Databases Reference
In-Depth Information
It is the user's responsibility to rollback the whole transaction involved in the deadlock, as we
do in step 7. The output is as follows:
In step 8 we also rollback the transaction in
SESSION
2
, to leave the data unchanged (but this
is not mandatory; as we can see in the previous screenshot, the transaction in
SESSION
2
is
not locked and no errors are signaled, so we can continue our work).
In step 9 we connect a third session to the database and in step 10 we query the parameter
USER_DUMP_DEST
, which shows us the path in which trace files and the alert log are written. In
our example database the location is
/u01/app/diag/rdbms/testdb/TESTDB/trace/
.
In step 11 we move to that directory using OS commands and list the trace files contained,
sorted by date in reverse order. The result of this operation is shown in the next screenshot:
