Re: Help required with deadlock issue

jeroen wrote in message <362cd5da.13342591_at_news.euronet.nl>...

>
>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

Session 13 is doing the same thing as session 7.

There are no users on the system when this job is running.

The routine archives data, and works like this

A procedure searches table A looking for groups of records that need archiving, each group is identified by a key value in one of the columns, there are currently over 100 key values.

For each key value found the procedure submits a job to the background queue, (dbms_job.submit,) passing to it the key value.

Each of these 'background' jobs then processes table A through a cursor and a for loop. The cursor has a where clause that only select records whose key value matches the one passed to it. For each record it deletes from table A based on the rowid returned from the cursor and inserts into table A_ARCH. A commit is done every 5000 inserts.

Each trace file generated by a deadlock, specifies the current statement is delete from table a where rowid = 'whatever'.

Kevin Received on Fri Oct 23 1998 - 08:27:04 CDT