Re: Adjacent Key Locking/"Twin Problem"

> > I would like to see the doc. We've had a problem on table deletes > which caused an exhaustion of SCO UNIX locks. > > Doesn't sound to me like you're suffering from the adjacent key lock problem there, but simply a shortage of locks / attempting to lock (by deleting) too many rows in one go. You need to either (a) Drop and re-create the table rather than deleting rows - also *much* quicker, but you can't roll it back if you change your mind; (b) Configure more locks; (c) Delete the rows in smaller bunches and commit each bunch one at a time; but this could give you data integrity problems. akent@cix.compulink.co.uk (Andy Kent) -------------------------------------