sqlj.replace_jar

Use the sqlj.replace_jar( ) procedure to replace a previously installed JAR file with a new version. When you use this syntax, you provide only the new JAR file and assign to it the JAR ID for which you want to replace the file.

sqlj.replace_jar

Notes:

¹ See Jar Name


Argument	Description	Restrictions	Syntax
jar_file	URL of the JAR file that contains the UDR written in Java™	The maximum length of the URL is 255 bytes	Quoted String

If you attempt to replace a JAR file that is referenced by one or more UDRs, the database server generates an error. You must drop the referencing UDRs before replacing the JAR file.

For example, the following call replaces the Courses.jar file, which had previously been installed for the course_jar identifier, with the Subjects.jar file:

EXECUTE PROCEDURE 
   sqlj.replace_jar("file://students/data/Subjects.jar",
   "course_jar");

Before you replace the Course.jar file, you must drop the user-defined function sql_explosive_reaction( ) with the DROP FUNCTION (or DROP ROUTINE) statement. (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.)

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 execute the sqlj.replace_jar( ) procedure. When IFX_EXTEND_ROLE is disabled, any user can execute sqlj.replace_jar( ).