June 2, 2003 at 11:29 pm
We are experiencing page 'locks' which are not being released when users break the connection to the DB (all users exit the application and logoff the network). The only way we have found to release the locks is to restart the DB service. The lock will not allow users to update the page's records, retrieveing the records is ok.
June 3, 2003 at 4:18 am
Are the users doing major tasks. If the lock is there for a large update and the user disconnects then the update has to rollback. Look at the last statement run on the spids producing the locks (especially the first in the chain). You may have even created a deadlock that has not victimized for some reason.
June 3, 2003 at 8:41 pm
Thank-you for the prompt reply.
The record lock is not associated with an update of a large number of records in the locked table but is enclosed within a CNN.BeginTrans, CNN.EndTrans structure. The user may call this structre many times within the screen each time updating only one record in the locked table (but a few records in other tables).
Does this make sense.
How can a deadlock not be 'victimized' and what can we do about it?
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply