RE: Error -121 (cannot write log record) on update in Informix SE 5.01 in a Transaction

This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. Contact your mail administrator for information about upgrading your reader to a version that supports MIME. ------ =_NextPart_000_01BB4E02.2CBDFBD0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit You are probably running out of UNIX locks. This is a common problem with older versions of SCO, in fact the default number of locks is often 300. Try monitoring the lock table with sar during the transaction. Tom Boldt nnnnnnnnnnnnnnnnnnnnnnnnnnn Thomas Boldt on!Contact Software, Inc. (414)375-6555 2110 tom@oncontact.com http://www.oncontact.com nnnnnnnnnnnnnnnnnnnnnnnnnnn >---------- >From: tatuan@worldnet.fr[SMTP:tatuan@worldnet.fr] >Sent: Thursday, May 30, 1996 10:21 AM >To: informix-list@rmy.emory.edu >Subject: Error -121 (cannot write log record) on update in Informix SE >5.01 in a Transaction > >Informix SE 5.01 seems to have a problem with some kind of >transaction. >As reading a table, we update each rows of the same table, one row at >a time. If we commit after each update, no problem. In the case of a >global transaction (commit after the last updated row), we got the >error 346 followed by Isam error 121. The number of rows updated is >about 300 and enough space is available for Informix Logs. > >If you are award about known problems, thanks to you to help us. >Implicit software Corporation > > ------ =_NextPart_000_01BB4E02.2CBDFBD0--