Hi,

If it is pre-6.5, there can be two limits.
1. Each transaction can be only upto 4 MB. However, when the transaction
size becomes more than this, one should get a 'Stalled Transaction' message,
and the transaction will be automatically rolled back.

2. There is a fixed limit for transaction manager (XM) log, which is 64 MB.
When there are many open transactions in the system, this log file also gets
filled up. When the total logsize about 32 MB (this 32 MB limit is, since we
may rollback all transactions) , one will again get another 'stalled
transaction' message, and IMAGE rolls back all transactions.

In either case, one should get the stalled transaction message before
process abort.

The above limits have been increased in 6.5. The new limit for transaction
size is 32 MB. The default size for XM log size is still 64 MB. However,
this can be configured to higher values using VOLUTIL.
See 6.5 Communicator article 'Large Transactions for IMAGE...' for further
details.

Hope this helps

Regards,
Vikram


Vince Martyn wrote:

> Hi all,
>
> I have an issue to resolve where a customer is using Image/SQL to update
>
> an image database.  I don't think there are any space issues on the
> Image
> side, but......
>
> When they try to fire about 350 individual insert statements to one
> dataset,
> the program aborts.  If they do less than this in one attempt, it is
> fine.
> They DON'T commit the transaction until the end.  A number of data
> sources are involved, this needs to complete as one transaction.
>
> We tested the front-end of the application, by pointing it at an Oracle
> database, and it worked, it only fails going to Image/SQL.
>
> Unfortunately we don't have any errors back from Image/SQL.  These
> are probably lost (if there are any) by the program driving Image/SQL.
> It is also possible that it is aborting and not returning an error!
>
> Are there any resourse/working area size issues?
>
> Thanks,
> Vince.