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

Home -> Community -> Usenet -> c.d.o.server -> Re: how to determine cause of deadlock

Re: how to determine cause of deadlock

From: Howard J. Rogers <howardjr_at_www.com>
Date: 2000/07/20
Message-ID: <3976bccf$1@news.iprimus.com.au>#1/1

Nick Yeast <nospam_at_bigfoot.com> wrote in message news:lpdbnsg4irlbna7g9mm9f65me4v27uo5h7_at_4ax.com...
> On Tue, 18 Jul 2000 18:15:37 -0500, "Yong" <yhuang_at_slb.com> wrote:
>
> >Gdas,
> >
> >Glad to know you solved your problem.
> >
> >Steve Adams' site has quite a few Q&A's discussing deadlocks. I read all
 of
> >them on there because last Saturday we had 4 deadlocks in udump file (we
> >used to 1 every two weeks on average). It seems increasing INITTRANS is a
> >solution to *some* cases. I guess a deadlock caused by two transactions
> >locking each other (as shown in your udump file snippet posted on 07/13)
 can
> >be solved by increasing INITTRANS. Another kind of lock, self-deadlock,
 is
> >probably more difficult. I have that problem once in a while. For
 debugging,
> >I need to set events 4020 on it, according to Steve Adams' suggestion.
>
> Please excuse me breaking in... Could you post the URL to the Steve
> Adams site? I'm a new DBA trying to gather online sources of wisdom.
>
> Many thanks in advance!
>

An excellent source of wisdom indeed: www.ixora.com.au

Regards
HJR
> --------
> Nick Yeast
> replace 'nospam' with 'club11'
Received on Thu Jul 20 2000 - 00:00:00 CDT

Original text of this message

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