| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Usenet -> c.d.o.server -> Re: how to determine cause of deadlock
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!
 |
 |