Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> Re: Deadlock problem

Re: Deadlock problem

From: Sandeep Dubey <dubey.sandeep_at_gmail.com>
Date: Mon, 8 May 2006 13:45:45 -0400
Message-ID: <bf2f74740605081045u2c1d60f5sbddc2a6f7e2392f9@mail.gmail.com>


Alessandro,

In a J2EE environment it is correct to let the app server control the transaction and stored proc to do all database DMLs. So you wont see any commit or rollback inside the stored proc.

You need to get the SQL that are causing deadlock. One could be where you are updating a key column(s) refered by a child table. Other can be when you are not doing updates in the same order in two different stored procs. e.g. one procedure is updating parent first and then child table an dother one is updating child table first and then parent table on same set of parent and child table.

Also make sure that you have indexes on the FKs if they are being updated.

Sandeep

--
http://www.freelists.org/webpage/oracle-l
Received on Mon May 08 2006 - 12:45:45 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US