#

| Chapter 9 Calling Java from PL/SQL |

## 9.5 Using dropjava

The dropjava utility reverses the action of loadjava. It converts filenames into the names of schema objects, drops the schema objects, and finally deletes their digest table rows. Dropping a class invalidates classes that depend on it directly or indirectly. Dropping a source also drops classes derived from it.

Here is the syntax:

>     dropjava {-user | -u} username/password[@database]
>       [-option_name [-option_name] ...] filename [filename] ...

where option_name stands for the following syntax:

>     {  {oci8 | o}
>      | {schema | s} schema_name
>      | {thin | t}
>      | {verbose | v} }

On the command line, you can enter the names of Java source, class, and resource files, SQLJ input files, and uncompressed .jar files and .zip archives, in any order.

Table 9.3 describes the dropjava command-line options.

Table 9.3: dropjava Options
Option | Description
--- | ---
-oci8 | Directs dropjava to communicate with the database using the OCI JDBC driver. This option (the default) and -thin are mutually exclusive.
-schema | Drops Java schema objects from the specified schema. If this option is not specified, then the logon schema is used. You must have the DROP ANY PROCEDURE privilege to drop objects from another user's schema.
-thin | Directs dropjava to communicate with the database using the thin JDBC driver. This option and -oci8 (the default) are mutually exclusive.
-verbose | Enables the verbose mode, in which progress messages are displayed.

9.4 Using loadjava |  | 9.6 Managing Java in the Database

Copyright (c) 2000 O'Reilly & Associates. All rights reserved.