-20201   THE INSTALL, REPLACE, REMOVE, OR ALTER OF jar-name FAILED DUE TO REASON reason-code-(reason-string)

Explanation

The JAR name jar-name that was specified on the alter, install, replace, or remove JAR procedure is not valid. For example, this message is issued for the following reasons:
  • The JAR name has the improper format.
  • The JAR cannot be installed because it already exists.
  • The JAR cannot be altered, replaced, or removed because it does not exist.
The following list shows the possible values for reason-code-(reason-string):
1 (UNDEFINED JAR)
A JAR with the name specified on ALTER_JAVA_PATH, REPLACE_JAR, or REMOVE_JAR does not exist in DB2®.
2 (SCHEMA LENGTH)
In the jar-name parameter, the schema delimiter period ('.') appears after more than 128 bytes, but the schema has a maximum length of 128 bytes.
3 (NAME LENGTH)
In the jar-name parameter, more than 128 bytes appear after the schema delimiter or the default schema is used, and the JAR name exceeds the maximum length of 128 bytes.
4 (PARSER ERROR)
During ALTER_JAVA_PATH, INSTALL_JAR, or REMOVE_JAR processing, the DB2 parser was invoked and returned an error message. This error can occur due to invalid characters or an invalid length of the jar-name parameter.
5 (DUPLICATE JAR)
A JAR with the name specified on INSTALL_JAR already exists in DB2.

System action

The statement cannot be processed.

User response

Take the following actions as appropriate:
  • Ensure that the JAR identifier has the correct format.
  • If the JAR already exists, remove it before you reinstall it.
  • If you want to alter, remove, or replace procedures within the JAR, ensure that the JAR exists.

SQLSTATE

46002