# SQLJ.REPLACE_JAR system procedure

The `SQLJ.REPLACE_JAR` system procedure replaces a jar file in a database.

## Syntax

    SQLJ.REPLACE_JAR(IN JAR_FILE_PATH_OR_URL VARCHAR(32672),
                     IN QUALIFIED_JAR_NAME VARCHAR(32672))

JAR_FILE_PATH_OR_URL
  The path or URL of the jar file to use as a replacement. A path includes both the directory and the file name (unless the file is in the current directory, in which case the directory is optional). For example:

      d:/todays_build/tours.jar

QUALIFIED_JAR_NAME
  The Derby name of the jar file, qualified by the schema name. Two examples:

      MYSCHEMA.Sample1

       -- a delimited identifier.
      MYSCHEMA."Sample2"

## Execute privileges

If authentication and SQL authorization are both enabled, only the database owner has execute privileges on this procedure by default. See "Configuring user authentication" and "Configuring user authorization" in the Derby Security Guide for more information.

The database owner can grant access to other users. Since this procedure can be used to install arbitrary code (possibly from across the network) that runs in the same Java Virtual Machine as the Derby database engine, the execute privilege should be granted only to trusted users.

## SQL example

    -- SQL statement
    CALL sqlj.replace_jar('c:\myjarfiles\newtours.jar', 'APP.Sample1')

    -- SQL statement
    -- replace jar from remote location
    CALL SQLJ.REPLACE_JAR('http://www.example.com/tours.jar', 'APP.Sample2')

Parent topic: System procedures for storing jar files in a database
Related reference
SQLJ.INSTALL_JAR system procedure
SQLJ.REMOVE_JAR system procedure