Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.server -> Re: Lock waits even though nothing in v$session.lockwait ... ?
DML locks are gotten for dml operations, normally you do a commit after a couple statements. Then those DML locks should be released. For some reason you are not committing. You need to find out why. Look at v$session_wait to find out what these processes are waiting on.
Anjo.
Andy Kent wrote:
> How do you tidy up after a system has become beset with lock waits and 'out
> of DML locks' errors?
>
> This afternoon our processes all remained resolutely frozen and the locks
> remained on even after the session that caused all the locks to back up
> behind it had been killed. The strangest thing was that all the processes
> just sat there even though there was not one single non-null value in
> v$session.lockwait.
>
> I thought I knew my way around the Oracle server pretty well but I must
> admit I became very confused about how I should be approaching the problem,
> and I couldn't find anything of help in the HTML manuals.
>
> Can someone offer me some pointers please?
>
> And why was I getting 'out of DML locks' errors at 630 locks even though our
> total configured number is in the 10000's?
>
> --
> -Andy Kent-
> Bristol, England
>
> Remove '.DontSpamMe' from return address to respond.
Received on Wed Mar 07 2001 - 13:36:32 CST
![]() |
![]() |