Deleting repository objects has a cascading effect.
This section describes the deletion rules.
Physical Layer Rules
If a physical column or a table is deleted, then all of the affected keys, foreign keys, and complex joins are deleted as well. The internal obsolete attribute definition (attr defn) that links a logical column to a physical column is also removed.
Empty schemas, catalogs, and databases are removed.
If a table is deleted, then all its columns are deleted.
Logical Table Rules
If a regular column, not an aggregate or derived column, is not mapped in any logical source, then it is deleted. The keys, including the level key and the logical key, are also removed.
If the source column for a derived column or its referenced variable is deleted (corrupted), then the column is removed.
If an aggregate rule or override aggregate rule for an aggregate column is corrupted, due to deleting a logical column, then the column is removed.
If a logical table is removed, because its underlying physical table was deleted, then the keys, foreign keys, logical joins, sources, and source folder are removed.
If a logical table source does not have any valid mapping, then it is deleted.
If a logical table source is retained, but its aggregate content or filters are corrupted, then the corresponding expressions are set to null. The join specification is also removed.
If a logical table, dimension, or business model is empty, does not contain a meaningful child object, then it is deleted.
Presentation Layer Rules
If a logical column is removed, because its underlying physical column was deleted, then any corresponding presentation columns are removed.
If a presentation table or subject area does not contain children, then it is removed.
If a security filter for a user or application role becomes corrupt due to deletion, then the filter is removed. If all filters are removed for a user or application role, then the internal privilege object is deleted.
Even if all filters for an application role are deleted, the application role is still maintained.
To remove an application role from the repository, you must explicitly delete it. See Security Guide for Oracle Business Intelligence Enterprise Edition for information about deleting application roles.
Initialization blocks are deleted if the underlying connection pool is deleted.
Repository and session variables are deleted if the associated initialization blocks are deleted.
If a session variable is deleted and its parent initialization block does not contain variables, then the initialization block is removed.
If an initialization block is deleted, then its variables are removed.
Qualified list items are deleted if the associated cache catalog, GUID column, or qualified column is deleted.
Target levels are deleted if the associated catalog (Segmentation Catalog name) is deleted.
List catalogs are deleted if the associated catalog, table, or column is deleted.
Conforming dimensions are deleted if the associated catalog, table, or column is deleted.