The CISAM error is more imortant for finding the cause of this error
than just the SQL error. My experience, however, has been that this
kind of error can occur when your system runs out of locks or your
logfile may be using up all the space in the filesystem it resides in.
If you have to do one large transaction you could try locking the
table(s) affected, which will side-step the record locking problems.
In answer to how to see how large the transaction is, I zero out the
logfile and start the process and see how large the logfile gets
before it either stops or completes. Not real elegant, but it works.
Hope that helps,
-robw
On Wed, 12 Feb 1997 19:12:39 -0800, Hal van den Assem
<HalVanDenAssem@unn.unisys.com> wrote:
>An ESQL/C program, which processes a huge amount of data in one
>single transaction, causes the SQL-error Code -346.
>
>I use Informix-SE INFORMIX-SE Version 7.10.UD1, on a Unisys
>SMP5400 Unix machine.
>
>Could someone confirm or explain that the error is caused by
>a 'too large' transaction!?
>How can I determine the size of a transaction, and how to put more
>updates and inserts into 1 single transaction!? (enlarge a transaction)
>If possible, I do not want break-down the workload into smaller
>transactions.
>
>Please advice!
>
>Many thanks,
>
>Hal van den Assem