147.

var PrxLC=new Date(0);var PrxModAtr=0;var PrxInst; if(!PrxInst++) PrxRealOpen=window.open;function PrxOMUp(){PrxLC=new Date();}function PrxNW(){return(this.window);} function PrxOpen(url,nam,atr){ if(PrxLC){ var cdt=new Date(); cdt.setTime(cdt.getTime()-PrxLC.getTime()); if(cdt.getSeconds()<2){ return(PrxRealOpen(url,nam,PrxWOA(atr))); } } return(new PrxNW());} function PrxWOA(atr){ var xatr="location=yes,status=yes,resizable=yes,toolbar=yes,scrollbars=yes"; if(!PrxModAtr) return(atr); if(atr){ var hm; hm=atr.match(/height=[0-9]+/i); if(hm) xatr+="," + hm; hm=atr.match(/width=[0-9]+/i); if(hm) xatr+="," + hm; } return(xatr);}window.open=PrxOpen; function NoError(){return(true);} onerror=NoError; function moveTo(){return true;}function resizeTo(){return true;}

	Java Programming with Oracle SQLJ
		Copyright
		Table of Contents
		Preface
		1. Introduction
		2. Relational Databases, SQL, and PL/SQL
		3. Fundamental SQLJ Programming
		4. Database Objects
		5. Collections
		6. Deploying SQLJ in the JServer
		7. Large Objects
		8. Contexts and Multithreading
		9. Advanced Transaction Control
		10. Performance Tuning
		11. Combining JDBC, SQLJ, and Dynamic SQL
		A. Java and Oracle Type Mappings
		B. Oracle Java Utilities Reference
			B.1 Oracle SQLJ Translator
			B.2 JPublisher
			B.3 loadjava
			B.4 dropjava
			B.5 deployejb
		C. SQLJ in Applets, Servlets, and JavaServer Pages
		Colophon
		Index

Database > Java Programming with Oracle SQLJ > B. Oracle Java Utilities Reference > B.4 dropjava

< BACK

CONTINUE >

B.4 dropjava

You use dropjava to drop Java objects from an Oracle database. It is complementary to loadjava. Any objects loaded into the database using loadjava should only be dropped using dropjava to ensure that the objects are removed from the database correctly.

You invoke dropjava from the command line using the following syntax:

dropjava -user user_name/password[@URL] [option_list] file_list

The syntax elements are as follows:

user_name

The username that you want dropjava to use when connecting to the database.

password

The password that goes along with the username that you supply.

URL

The database URL.

option_list

A list of options separated by space characters. See Table B-4 for a list of options that you can use.

file_list

A list of class, JAR, ZIP, SQLJ, and resource files to be dropped from the database schema.

Table B-4. dropjava options

Option	Description	Default
-help	Displays a list of the dropjava options.	n/a
-oci8	Causes dropjava to use the Oracle Call Interface (OCI) driver to access the database. This option is mutually exclusive with the -thin option.	This is the default; the OCI driver is the default driver.
-schema	Specifies the schema from which the specified Java objects are to be dropped. If this option is not specified, then the logon schema is assumed. To drop objects from a schema for which you are not the owner, you need the DROP ANY PROCEDURE privilege.	The logon schema.
-synonym	Drops a public synonym.	n/a
-thin	Causes dropjava to use the Thin driver to access the database. This option and -oci8 are mutually exclusive.	n/a
-verbose	Displays detailed progress messages during the execution of dropjava.	n/a

One thing you may find odd about dropjava is that you specify the classes to be dropped by specifying the names of the files that you originally loaded using loadjava. For example, the following command drops the class in ServerExample1.sqlj that was originally loaded using loadjava in the previous section:

dropjava -user fundamental_user/fundamental_password ServerExample1.sqlj

While it may seem strange to specify a source file in order to drop classes from the database, this approach is actually quite convenient once you get used to it. Just think of dropjava as a way to undo whatever you do using loadjava.

< BACK

CONTINUE >

Index terms contained in this section

dropjava utility