You can use the Database Explorer to drop JAR files from a database
server. Dropping a JAR file from the database does not remove the JAR file
from any data development projects that contain it. If the JAR file information
is still in a data development project, you can deploy the JAR file again.
This feature is only supported for DB2® for z/OS® Version 9 database servers.
Prerequisite: Before you drop a JAR file from a database,
you must identify and resolve any dependencies on the JAR file. If you do
not resolve dependencies, you see an error message when you attempt to drop
the JAR file. You can follow these steps to resolve the dependencies:
- Identify all dependent JAR files by running a query on SYSIBM.SYSJAVAPATHS,
where PE_JARSCHEMA and PE_JAR_ID correspond
to the JAR file that you want to drop.
- Import any dependent JAR files into a data development project and remove
any references to the JAR file.
- Deploy the dependent JAR files back to the server, with the references
removed.
- Identify all dependent routines by running a query on SYSIBM.SYSROUTINES,
where JARSCHEMA and JAR_ID correspond
to the JAR file that you want to drop.
- Drop all dependent routines from the database server.
To drop a JAR file from a database:
- Switch to the Data perspective.
- In the Database Explorer, open a database connection.
- Right-click a JAR file under a schema node, and click Drop.
The JAR file is dropped from the database.