Re: how to determine cause of deadlock

Thanks for the help...I'm positive it's a deadlock, because that's the error that oracle sends back to the process:

ORA-00060 deadlock detected while waiting for resource

We're trying to isolate the problem and we've stripped out alot of code. We now have multiple threads doing inserts only and we still get this deadlock problem. How can this be possible? I thought a deadlock should only occur with an update.

The only thing that we are suspicious of is the fact that are generating unique keys by calling the nextval of a sequence. Can a sequence ever be in a locked state such that it could cause this?

Multiple threads all calling the same sequence and then sending inserts. Our commit rate is pretty frequent (100 rows)...

Does anyone know what might be happening. I'm utterly clueless at this point.

Thanks,
Gavin

Got questions? Get answers over the phone at Keen.com. Up to 100 minutes free!
http://www.keen.com Received on Thu Jul 13 2000 - 00:00:00 CDT