STOP_TIME is NULL in EXA_DBA_TRANSACTION_CONFLICTS for WAIT_FOR_COMMIT conflicts upon session/statement kill
Details
| Detail name | Value |
|---|---|
| Changelog Number | 10419 |
| Type | Bug |
| Status | Open |
| Affected Versions | Exasol 6.1.0, Exasol 6.2.0, Exasol 7.0.0, Exasol 7.1.0, Exasol 8.0.0 |
Description
When a WAIT_FOR_COMMIT conflict occurs, the STOP_TIME field is set to NULL until the conflict is resolved (the conflicting transaction has ended). However, if any of the corresponding sessions/statements is killed, the STOP_TIME field remains NULL, even though the conflict has ended with the session/statement being killed.
You can verify which transaction conflicts are still open with the following query:
SELECT * FROM EXA_DBA_TRANSACTION_CONFLICTS WHERE STOP_TIME IS NULL AND SESSION_ID IN (SELECT SESSION_ID FROM EXA_DBA_SESSIONS)
Workaround
You can use the query above to check for open transaction conflicts. The query above will only show conflicts that have a session currently running.
Fix
EXA_DBA_TRANSACTION_CONFLICTS will display the correct STOP_TIME. Specifically, it will display the time that the session is killed
