When you select an index from the contents pane and select Show Related for that object, the Show Related dialog lists any objects with first-level dependencies on that index. These objects can be: packages, plans, storage groups, tables. You can view second-level dependencies by selecting Show Related for each object with a first-level dependency.
If you drop an index - Not all clauses of an index definition can be changed altering the index (available from the Control Center). To change an index without using ALTER INDEX, you must drop the index, commit, and redefine it. Dropping an index does not cause DB2 to drop any other objects. You must drop the index (available from the Control Center) before you create any new table spaces or indexes by the same name. If an index is dropped and an application program using that index is run (and thereby automatically rebound), that application program does not use the old index. If, at a later time, the index is created again, and the application program is not rebound, the application program cannot take advantage of the new index.
DROP INDEX cannot be performed while a DB2 utility has control of the index or its associated table space.
Dropping indexes invalidates application plans and packages that use the index and automatically rebinds them the next time they are used.
If an index is used to access a storage group and privileges to that index are revoked, then attempts at accessing the storage group through the index fail.
If a unique index is dropped and that index was used to enforce the uniqueness of a parent key, the definition of the parent table is changed to incomplete. Otherwise, if the index was used to enforce a UNIQUE constraint, the definition of the table is not changed. The table can still be used, but the UNIQUE constraint implied by the index is no longer enforced.
If a unique index is dropped and that index was defined on a ROWID column that is defined as GENERATED BY DEFAULT, the table can still be used, but rows cannot be inserted into that table. If an empty index on an auxiliary table is dropped, the base table is marked incomplete.
For tables with a primary key, plan to create the primary index soon after creating the table. The primary index is the first unique index created on the tables primary key columns, with the same order of columns as the primary key columns. The table has an incomplete definition until you create an index on the parent key, meaning that you will not be able to load the table, insert data, retrieve data, update data, delete data, and create foreign keys that reference the primary key.
An index on an auxiliary table cannot be explicitly dropped.