Queries on EXA_DBA/USER_PROFILE_RUNNING containing sessions of dropped users may fail
Details
| Detail name | Value |
|---|---|
| Changelog Number | 11075 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | Exasol 6.2.0, Exasol 7.0.0, Exasol 7.1.0 |
| Fix Versions | Exasol 7.1.0, Exasol 7.0.4, Exasol 6.2.12 |
| Resolution Date | 2020-11-17 |
Description
Dropping a user does not automatically kill sessions of that user. When these types of sessions still exist, queries on the EXA_DBA/USER_PROFILE_RUNNING system tables may return an internal server error.
Workaround
You can either wait for all sessions of the dropped user to end or you can kill them explicitly. You can identify these sessions with the following query:
SELECT * FROM EXA_DBA_SESSIONS WHERE USER_NAME IS NULL;
Fix
The query will execute without any errors.
