Just exactly what everyone else said. I'm going from memory, but I bet
ISAM is -113.
Ways you can reduce the number of locks required, at the expense of
concurrency:
Lock the table or database in exclusive mode...this will also buy you
performance.
I'm not sure it would affect the number of locks, but cursors for update
and insert cursors are helpful in such large transactions (at least for
performance).
Hal van den Assem 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