When you select a package from the contents pane and select Show Related for that object, the Show Related dialog lists any objects with first-level dependencies on that package. These objects can be: aliases, indexes, plans, synonyms, tables, table spaces, views. You can view second-level dependencies by selecting Show Related for each object with a first-level dependency.
A package is an object containing SQL statements that are bound statically and that are available for processing. If you need to change only one SQL statement in your package, you do not need to bind the entire plan again. You only need to bind the package associated with the changed SQL statement.
Dropping a package or dropping a trigger (which implicitly drops the trigger package) can not be performed while the package or trigger package is in use by an application. For applications that are bound with RELEASE(COMMIT), you can drop the package or trigger package at a commit point. For applications that are bound with RELEASE (DEALLOCATE), you can drop the package or trigger package only when the application's thread is deallocated.
Whenever the last or only version of a package is dropped, all privileges on the package are dropped and all plans that are dependent on the execute privilege of the package are invalidated.
If you drop an alias that was used in a package, you need to rebind the package.
When an index is deleted, its description is deleted from the catalog and any packages that reference the index become invalid.
Whenever the last or only version of a package is dropped, all privileges on the package are dropped and all plans that are dependent on the execute privilege of the package are invalidated.
If a database user has access privileges to indexes, tables, table spaces, or views through a package, and if it is dropped, all indexes, tables, table spaces, and views that were dependent on the package become inaccessible to that database user.
When an index is deleted, its description is deleted from the catalog and any packages that reference the index become invalid. If you drop a table, any views and authorizations based on the table are dropped. Dropping or changing a table space invalidates packages that use the table space so that the package needs to be rebound.
When you drop a view, DB2 invalidates application packages that are dependent on the view. Also, DB2 revokes the privileges of users who are authorized to use it. DB2 attempts to rebind the package the next time it is executed, and you receive an error if you do not re-create the view.