When you select a view from the contents pane and select Show Related for that object, the Show Related dialog lists any objects with first-level dependencies on that view. These objects can be: aliases, base tables, packages, plans, synonyms, or views. You can view second-level dependencies by selecting Show Related for each object with a first-level dependency.
When you drop a view, the alias with which it is associated remains unchanged. You can create a view on an alias that refers to a local table or view, but not on an alias that refers to an object from a remote DB2 subsystem.
When you drop a view, DB2 invalidates application plans and packages that are dependent on the view. DB2 revokes the privileges of users who are authorized to use it. DB2 attempts to rebind the package or plan the next time it is executed, and you receive an error if you do not re-create the view.
Whenever a view is directly or indirectly dropped, all synonyms that are defined on the view are also dropped.
If the SELECT privilege on the base table is revoked from the owner of the view, the view is dropped. All existing views and authorizations on the table remain intact after you delete a table or view. The DELETE statement deletes all rows of a table unless you specify a WHERE clause to limit it. The table continues to exist but it is empty.
When you drop a view, DB2 also drops any dependent views.
The only way to change a view is by dropping the view, committing the drop, and re-creating the view. To tell how much rebinding and re-authorizing is needed if you drop a view, check the following catalog tables: