EXA_DBA_RESTRICTED_OBJ_PRIVS contains reference to deleted object
Details
| Detail name | Value |
|---|---|
| Changelog Number | 12566 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | Exasol 7.0.0 |
| Fix Versions | Exasol 7.0.11 |
| Resolution Date | 2021-07-16 |
Background
The system table EXA_DBA_RESTRICTED_OBJ_PRIVS lists all connection objects to which certain, restricted scripts or schemas were granted access to. When a user is dropped, all objects which they were the owner of are also dropped.
Description
In the following scenario, grants are not cleaned up in EXA_DBA_RESTRICTED_OBJ_PRIVS properly:
- A user is dropped (with CASCADE option)
- The user was the owner of a schema
- A script in the now-dropped schema (or the entire schema) had restricted ACCESS privileges on a connection.
In this scenario, the next query (after querying EXA_DBA_RESTRICTED_OBJ_PRIVS) may return an internal server error If autocommit is turned off.
Workaround
Execute a COMMIT after querying EXA_DBA_RESTRICTED_OBJ_PRIVS
Fix
The grants are correctly removed from EXA_DBA_RESTRICTED_OBJ_PRIVS.
