Informix Error -12204: RSAM error: Long transaction detected.
Cause and resolution
RSAM error: Long transaction detected.
The database server ran out of log space in which to record this transaction. A transaction that is not fully recorded cannot be rolled back. To preserve database integrity, the database server ended the current operation that caused the long transaction.
Terminate the application and replan it so that it requires less log space in a transaction. Alternatively, contact the database server administrator to discuss increasing the number or the size of the logical logs. Be prepared to talk about the number of rows being updated or inserted and the size of each row.
Oninit® Troubleshooting Guidance
Reasons / Common Causes
-12204 fires when the database server runs out of logical-log space to record a transaction — per the official guidance.
- A transaction whose changes exceed the available logical-log space, per the official guidance — the direct, only cause; since an unrecorded transaction can't be rolled back, the server ends the operation to preserve integrity.
Solutions / Resolution
- Terminate the application and replan it to require less log space per transaction, per the official guidance — e.g. commit in smaller batches.
- Contact the database server administrator to discuss increasing the number or size of logical logs, per the official guidance — be ready to discuss row counts and row size.
Examples
N/A
No specific triggering statement is documented beyond a transaction outgrowing the available log space.
Diagnostic Checks
- Check the number of rows being updated/inserted per transaction and their size, and either batch the work into smaller transactions or increase logical-log capacity.
Related Errors / Related Topics
No closely related error codes are cross-referenced for -12204 in this set yet.
A transaction outgrew the available logical-log space — batch the work into smaller transactions, or increase the number/size of logical logs.