Troubleshooting COMMITs when using ODBC Driver Manager
When using ODBC Driver Manager and running in autocommit mode, most versions of ODBC Driver Manager regard calls to SQLTransact and SQLEndTran as redundant and never actually pass them to the driver.
This means that the application program receives only the return code 'SUCCESS' from the ODBC Driver Manager, even though no transaction is committed in the database. This situation can go unnoticed. In addition to the ODBC Driver Manager or solidDB® SQL Editor (solsql), other utilities can also have open transactions.
Make sure that you are aware of all database connections. Each FETCH after COMMIT (keeping the statement handle alive) also causes a new transaction to start.