Problem with long transactions

We currently are having a problem with "aborting long transactions." When this occurs our logical logs (we have 6 @ 500 pages/log) fill up and tbtape (running continuously) is unable to back them up. This situation fills turbo.log with countless "Logical logs are full. . .etc." We are able to recover okay but it is annoying (at the least). We are going to increase the number of logs to ten in the future. QUESTIONS: 1) Does anyone think increasing the number of logical logs will help? 2) Does anyone have any reasons why aborting a long transaction would fill up the logs? Consensus around here is that for some reason Informix is unable to rollback the transaction quickly enough and other concurrent transactions fill the logs. If this is the case why doesn't the database eventually "catch up?" Thanks in advance. Brad Knotwell bpk@evolving.com Evolving Systems, Inc. Denver, CO