Loading Stored Procedures

Using dropjava

The dropjava utility converts filenames into the names of schema objects, drops the schema objects, then 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.

On the command line, you can enter the names of Java source, class, and resource files, SQLJ input files, and uncompressed JARs and ZIP archives in any order. 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} }

Table 2-3 describes the dropjava command-line options.

Table 2-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 verbose mode, in which progress messages are displayed.

Specifying Filenames

dropjava interprets most filenames the same way loadjava does. With class files, dropjava finds the name of the class in the file, then drops the corresponding schema object. With source files and SQLJ input files, dropjava finds the name of the first class in the file, then drops the corresponding schema object. With uncompressed JARs and ZIP archives, dropjava processes the names of archived files as if you had entered them on the command line.

If a filename has an extension other than .java, .class, .sqlj, .jar, or .zip, or has no extension, dropjava assumes the filename is the name of a schema object, then drops all source, class, and resource schema objects with that name. If the filename begins with a slash, then dropjava prefixes ROOT to the name of the schema object.

If dropjava encounters a filename that does not match the name of any schema object, it displays an error message, then processes the remaining filenames.

Examples

In the following example, dropjava connects to the default database using the OCI JDBC driver, then drops all objects from schema BLAKE that were loaded from serverObjs.jar:

> loadjava -user scott/tiger -schema BLAKE serverObjs.jar

In the next example, dropjava connects using the thin JDBC driver, then drops a class and resource from the user's schema:

> loadjava -u scott/tiger@dbhost:5521:orcl -t Agent.class images.dat