If you are using the term "deadlock" correctly, you
should find a trace file in the directory identified by
parameter user_dump_dest.
This should give you the first clues about where the
deadlock is coming from. This will indicate one of
two issues, ORA-00060 which typically will be a code
or design error on the part of the application, not an
error on the part of Oracle, or ORA-04020 which
is more likely to be a coding error in the Oracle kernel
that has been triggered by an "unanticipated" use of
DDL in your application.
--
Regards
Jonathan Lewis
http://jonathanlewis.wordpress.com
Author: Cost Based Oracle: Fundamentals
http://www.jlcomp.demon.co.uk/cbo_book/ind_book.html
The Co-operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html
<h.jalalipoor_at_gmail.com> wrote in message
news:1164177256.919656.49280_at_m7g2000cwm.googlegroups.com...
>I have oracle 9.2.0.3 on HP9000 PA-RISC 64Bit (12GB RAM and 6 CPU).
> database size is about 100GB and active users is about 200 user.
> when a deadlock detected, my database hang for a few minutes, no body
> can`t do any thing even dba. I want to connect as sysdba from SQL*Plus
> but i can`t and SQL*Plus wait until deadlock detection resolved by
> oracle.
> my question is what happen on database when a deadlock detected? is it
> a bug or it is normal?
>
> best regards.
>
Received on Wed Nov 22 2006 - 01:01:02 CST
