Error writing to the log file

Hi, I am using Informix-SE version 7.10. I have a report that creates a temp table and then updates a certain field in it before sending the content of this table to a report. It seems that when the report parameters cover too many records the report gets the following error at the update stage: Date: 08/16/1999 Time: 16:24:25 Program error at "woemrtr1.4gl", line number 543. SQL statement error number -346. Could not update a row in the table. SYSTEM error number -121. ISAM error: cannot write log record The log file is a reasonable size (~ 50 Mo) There is enough temporary space available. Does anybody have advice on this ? Thanks, Chris

But is there enough space on the disk holding the table's transaction log file? The -346 -121 combination indicates that some transaction failed, possibly writing the reports sort-work temp table, and the temp table's transaction log file could not be written to. Usually this is becuase the disk is full. Art S. Kagel Christian Allaire wrote: > > Hi, > > I am using Informix-SE version 7.10. > I have a report that creates a temp table and then updates > a certain field in it before sending the content of this table > to a report. It seems that when the report parameters cover > too many records the report gets the following error at the > update stage: > > Date: 08/16/1999 Time: 16:24:25 > Program error at "woemrtr1.4gl", line number 543. > SQL statement error number -346. > Could not update a row in the table. > SYSTEM error number -121. > ISAM error: cannot write log record> > The log file is a reasonable size (~ 50 Mo) > There is enough temporary space available. > > Does anybody have advice on this ? > > Thanks, > > Chris

In article <37B88510.48E0EEFF@bloomberg.net>, Art S. Kagel <kagel@bloomberg.net> writes >But is there enough space on the disk holding the table's transaction log >file? The -346 -121 combination indicates that some transaction failed, >possibly writing the reports sort-work temp table, and the temp table's >transaction log file could not be written to. Usually this is becuase the >disk is full. > >Art S. Kagel Art, I have also seen this under Se when it runs out of locks1 Solution is to up the kernel parameter FLCKREC.. -- David Williams