When you select a trigger from the contents pane and select Show Related for that object, the Show Related dialog lists any objects with first-level dependencies on that trigger. These objects can be: schemas, tables. You can view second-level dependencies by selecting Show Related for each object with a first-level dependency.
Whenever a trigger is directly or indirectly dropped, all privileges on the trigger are also dropped and the associated trigger package is freed. The name of that trigger package is the same as the trigger name and the collection ID is the schema name.
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.
When you drop a trigger, the schema with which it is associated remains unchanged.
When a triggering table is dropped, the associated trigger and trigger package are also dropped.