When you select a table space from the contents pane and select Show Related for that object, the Show Related dialog lists any objects with first-level dependencies on that table space. These objects can be: packages, plans, storage group, tables. You can view second-level dependencies by selecting Show Related for each object with a first-level dependency.
When a table space is dropped, DB2 loses all information about the image copies of that table space. Although the image copy data set is not lost, locating the table space requires examination of image copy job listings or manually recorded information about the image copies.
Dropping or changing a table space invalidates packages and plans that use the table space so that any package or plan associated with it needs to be rebound.
When you drop a table space, the storage with which it is associated remains unchanged. Except it does free up additional space on that particular storage group.
A storage group can not be dropped if it is used by any table space or index space.
Whenever a table space is directly or indirectly dropped, all the tables in the table space are also dropped. The name of a dropped table space cannot be reused until a commit operation is performed.
A LOB table space can be dropped only if it does not contain an auxiliary table.