Re: "Lock table overflow - user id 6, session id 4" in online.log

sbe wrote: > > Does anyone know what this message means ? It means that you had X locks configured and a program run by userid 6 which happened to be session 4 requested >X locks and so overflowed the lock table and was rolled back. The solution, as others will point out, is to 1) increase the number of locks, 2) perform such mass updates/deletes/inserts with the table locked so you only consume one lock, and 3) restructure such updates so that they use fewer locks (ie commit partial datasets & perform deletes and updates as multiple statements with where clauses that restrict the number of affected rows). Look in dbcopy.ec and dbdelete.ec in my submission, utils2_ak, to the IIUG Software Repository for methods for doing this in a generalized fashion for inserts and deletes, respectively. Art S. Kagel