EXA_DBA_DEPENDENCIES and EXA_DBA_DEPENDENCIES_RECURSIVE unusable when dropping schemas of dependent objects

Detail name	Value
Changelog Number	12266
Type	Bug
Status	Resolved
Affected Versions	Exasol 6.2.0, Exasol 7.0.0
Fix Versions	Exasol 7.0.10
Resolution Date	2021-06-05

Description

Accessing the EXA_DBA_DEPENDENCIES and EXA_DBA_DEPENDENCIES_RECURSIVE system tables become raises the below exception
if the schema containing the dependent objects of a view is dropped. More precisely, the scenario below is reproducing the problem.

Exception:

 Trying to access already dropped object 

Example

Session 1	Session 2	Session 3
create schema if not exists s1;
create schema if not exists s2;
create table s1.t1 as select * from dual;
commit;
	drop schema s1 cascade;
		create view s2.v1 as select * from s1.t1;
		commit;
	commit;

After this scenario is run, any transaction attempting to read EXA_DBA_DEPENDENCIES or EXA_DBA_DEPENDENCIES_RECURSIVE will get an exception.

Workaround

There is no workaround

Fix

A dropped schema does not prevent accessing these system tables.