Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.server -> need help about deadlock by insert statements
I have difficulties on understanding the following phenomenon.
Each time I encountered deadlock situation in my site, the the trace files in the udump dest usually indicate that the SQL statment that causes the deadlock is an insert statement.
As far as I understand most of the deadlocks are related to improper design of concurrent update transactions. There a lot of workarounds to deal with such fault. But all these deadlock matters that I know are mostly related on updates transaction. And I wonder why an "insert" statement in my site will also cause a deadlock.
Would it be the problem on the insert statement or would it be the problem on Oracle? (Of course, everyone who have read such kind of deadlock trace file would know Oracle will simply blame it is the application design fault. But I doubt that it is the case.)
The Oracle version that I am using is 7.3.2.3.0 on SunOS. Any advice/help would be high apprepriated. Thank you. Received on Thu Aug 20 1998 - 02:19:52 CDT
![]() |
![]() |