Re: Help required with deadlock issue

On Tue, 20 Oct 1998 11:46:14 +0100, "Kevin Berry" <@dircon.co.uk> wrote:

>I am in need of some pointers with a deadlock issue.
>
>The deadlock is occurring within a stored procedure provided by a third
>party software supplier, (they are investigating, but very slowly!)
>
>The procedure doesn't do any work itself, it just submits job to be run by
>the background processes. We have 6 of these background processes running.
>
>Each of the submitted jobs process records within the same base table, but
>never the same record within that table.
>
>Every now and again a deadlock occurs. The following snip-it comes from the
>trace file. The trace suggests that the sessions were not waiting for locks
>to be release on rows.
>
>So that question is, how do I find out what was causing the deadlock.
>
>Any pointers would be appreciated.
>
>Kevin
>
>Oracle7 Server Release 7.3.2.3.0
>on
>Digital UNIX V3.2C (Rev. 148)
>
>*** SESSION ID:(7.1059) 1998.10.16.17.53.37.596
>DEADLOCK DETECTED
>Current SQL statement for this session:
>UPDATE PRD_MVTS SET INCLD_IN_MSH='1' WHERE ROWID = :b1
>----- PL/SQL Call Stack -----
> object line object
> handle number name
> 10fa0d8 349 procedure MERLIVE.MSP_MSTK0360
> 1c15300 1 anonymous block
> 1c15300 1 anonymous block
>The following deadlock is not an ORACLE error. It is a
>deadlock due to user error in the design of an application
>or from issuing incorrect ad-hoc SQL. The following
>information may aid in determining the deadlock:
>Deadlock graph:
> ---------Blocker(s)-------- ---------Waiter(s)------
>---
>Resource Name process session holds waits process session holds
>waits
>TX-00030031-0000324b 8 7 X 13 31
>S
>TX-00030021-00003154 13 31 X 8 7
>S
>Rows waited on:
>Session 31: no row
>Session 7: no row
>
>
>
>
 

>

Session 7 is doing an update but what is session 31 doing ? As soon as you this occurring try to find through v$session who it and through v$sqtext what is has been doing

Jeroen Received on Tue Oct 20 1998 - 00:00:00 CDT