sqlj.remove_jar

Use the sqlj.remove_jar( ) procedure to remove a previously installed JAR file from the current database. You must hold the Resource privilege or the DBA privilege on the database, and also hold the Usage privilege on the Java™ language, before you can create or drop a Java UDR.

sqlj.remove_jar

Notes:

¹ See Jar Name


Argument	Description	Restrictions	Syntax
deploy	Integer that causes the procedure to search for deployment descriptor files in the JAR file	None	Literal Number

If you attempt to remove a JAR file that is referenced by one or more UDRs, the database server generates a 46003 error. You must drop the referencing UDRs before you replace the JAR file. An invalid JAR file name generates a 46002 error.

For example, the following SQL statements remove the JAR file that is associated with the course_jar JAR ID:

DROP FUNCTION sql_explosive_reaction;
EXECUTE PROCEDURE sqlj.remove_jar("course_jar");

When you specify a nonzero number for the second argument, the database server searches through any included deployment descriptor files. For example, you might want to include descriptor files that include SQL statements to revoke privileges on UDRs in the associated JAR file and drop them from the database.

If the IFX_EXTEND_ROLE configuration parameter is enabled (which is its default setting), only the DBSA or users who hold the EXTEND role are able to run the sqlj.remove_jar( ) procedure. When IFX_EXTEND_ROLE is disabled, any user can run sqlj.remove_jar( ).