Troubleshooting
Problem
In IBM Business Automation Workflow, users encounter a “500 Internal Server Error” when attempting to access the Process Admin Console. The error is typically accompanied by the message “CWTBG0019E: Unexpected exception during execution”, along with the DB2 error “Exception information: 'PreparedStatementCallback; SQL [INSERT INTO LSW_LOCK (LOCK_ID, DESCRIPTION) VALUES (?,?)]; The transaction log for the database is full.. SQLCODE=-964, SQLSTATE=57011, DRIVER=4.32.28; nested exception is com.ibm.db2.jcc.am.SqlException: The transaction log for the database is full.. SQLCODE=-964, SQLSTATE=57011, DRIVER=4.32.28'.
Symptom
- A 500 Internal Server Error is encountered when accessing IBM Business Automation Workflow Process Admin Console. The error message indicates that the DB2 transaction log is full, returning SQLCODE=-964 and SQLSTATE=57011.
The issue occurs during the execution of an INSERT operation on the LSW_LOCK table. The DB2 transaction log has been exhausted due to the presence of indoubt transactions—transactions that have neither been committed nor rolled back.
These unresolved transactions continue to consume log space, eventually leading to log saturation. As a result, DB2 is unable to process new database operations, causing application failures such as the Process Admin Console becoming inaccessible.
Cause
The issue was caused by indoubt transactions in the DB2 database, which resulted in the transaction log becoming full. These indoubt transactions were generated due to failures during the commit phase of distributed transactions, typically triggered by network interruptions or node crashes in a two-phase commit scenario.
As a result, the transactions remained unresolved (neither committed nor rolled back), continuing to occupy transaction log space and eventually leading to log saturation.
Resolving The Problem
To resolve the issue, the indoubt transactions must be cleared by executing the FORGET TRANSACTION command (option f1). This action removes entries for transactions that were heuristically completed (i.e., already committed or rolled back internally) and releases the associated resources held in the transaction log.
Once the indoubt transactions are forgotten and the log space is freed, the database resumes normal operation. After completing these steps, access to the IBM Business Automation Workflow Process Admin Console is restored, and users will be able to log in successfully without encountering errors.
To execute the FORGET TRANSACTION command and resolve the indoubt transactions, refer to the following documentation:
https://www.ibm.com/docs/en/db2/11.5.x?topic=commands-list-indoubt-transactions
https://www.ibm.com/support/pages/db2-how-solve-transaction-log-databases-full-sql0964c?view=full
https://www.ibm.com/docs/en/db2/11.5.x?topic=commands-list-indoubt-transactions
Document Location
Worldwide
Product Synonym
BAW
Was this topic helpful?
Document Information
Modified date:
20 March 2026
UID
ibm17266401