select from EXA_*_SESSIONS may lead to internal server error if session of a dropped user still exists
Details
| Detail name | Value |
|---|---|
| Changelog Number | 8277 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | Exasol 6.1.0, Exasol 6.2.0 |
| Fix Versions | Exasol 7.0.0, Exasol 6.1.11, Exasol 6.2.9 |
| Resolution Date | 2020-07-28 |
Executing a select on EXA_ALL_SESSIONS, EXA_DBA_SESSIONS or EXA_USER_SESSIONS may result in an internal server error if a session of a dropped user is still connected to the database. In this case you will receive the following exception:
Error: [42000] Internal server error. Please report this. Transaction has been rolled back.
This error will only disappear after the session of the dropped user has been removed.
Workaround
The session of the dropped user has to be terminated by using the KILL SESSION command or perform a disconnect on its own.
If the session of the user can't be identified, the database has to be restarted.
