Re: Row locking

If at all possible (and I realize it often isn't) lock the table or the database in exclusive mode. This allows Informix to obtain a single lock for all the work. 2nd possibility is to increase the number of locks available....I believe this is an Informix tunable parameter, but it might be related to your SCO system locks, (which might also be tuneable). If those don't work, you may have to redesign to do smaller transactions....we use "commit levels" where we have a parameter passed to the program telling it to commit every so often....this also saves time if it dies in the middle of a long process...we can start over very near where we had the problem, rather than at the beginning Paulo Abreu wrote: > I'v noticed that with my Informix-SE on Unix SCO, if i make a .. > > begin work > lock table x in exclusive mode ... > > for every row updated i got just one System Lock for the table X. > > ... but ... > > if for any reason i have to rollback, the system will make a lock for every > row that is rolling back, producing eventualy a "Out of Locks" system error > and then an Informix error such as "Could not rollback work" > > any help? -- - Danny Wright danwright@nospam.com to e-mail, replace "nospam" with "bigfoot". No headhunters please, #include <stddisclaimers.h>