Informix Error -6065: Database does not have transactions.

Cause and resolution

Database does not have transactions.

This call to dbbegin(), dbcommit() or dbrollback() is inappropriate because the current database does not support transactions. To use transaction processing to convert the database, see the reference material for your database server.

Oninit® Troubleshooting Guidance

Reasons / Common Causes

-6065 fires when dbbegin(), dbcommit(), or dbrollback() is called against a database that doesn't support transactions — per the archived catalogue.

The current database not configured for transaction logging, per the archived catalogue — the direct, only cause.

Solutions / Resolution

Convert the database to use transaction logging, per the archived catalogue's reference to the database server's own documentation for that process, if transaction processing is actually needed.

Examples

N/A

No specific triggering statement is documented beyond the function-level condition described above.

Diagnostic Checks

Confirm whether the current database is logged (transaction-capable) at all.

Related Errors / Related Topics

-6064 — "Tried to terminate a transaction that hasn't been started."
-6067 — "Tried to unlock a table inside a transaction."
-6069 — "Tried to lock a table outside a transaction."

The current database isn't transaction-logged — convert it if transaction processing is needed.