Invalid CRASHED entries in statistics and auditing system tables
Details
| Detail name | Value |
|---|---|
| Changelog Number | 5949 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | EXASOL 6.0.0 |
| Fix Versions | Exasol 6.0.13 |
| Resolution Date | 2018-10-02 |
Synopsis
The EXA_SQL_LAST_DAY and EXA_DBA_AUDIT_SQL system tables may contain entries where
- STMT_ID = 0
- EXECUTION_MODE = 'CRASHED'
- ERROR_TEXT = 'Successfully reconnected after internal server error, transaction was rolled back'.
Consequently, the entries will also be aggregated into EXA_SQL_HOURLY, EXA_SQL_DAILY and EXA_SQL_MONTHLY.
These unexpected entries may appear when a session is interrupted on network level when the client did not execute any SQL statements but only metadata queries (usually the EXAplus metadata connection).
The entries can be safely ignored on a semantic layer, as no transaction / data modification process is affected.
Causes
These entries are typically caused by reconnects after network problems, usually caused by VPN or firewall settings or unstable uplinks (aka DSL reconnect).
Workaround
Simply ignore these entries; after the fix is implemented, these entries will not show up in the above mentioned system tables anymore.
