logo  
Google
 

DB2 SQL-Error: -20201

SQLState: 46002

Short Description: THE INSTALL REPLACE OR REMOVE OF FAILED DUE TO REASON

The JAR name jar-name that was specified on the install, replace, or remove JAR procedure was invalid. For example, this message could be issued for one of the following reasons: v The JAR name might have the improper format v The JAR procedure cannot be replaced or removed because it does not exist v The JAR procedure cannot be installed because it already exists The following list contains the possible values for reason-code and reason-string: 1 (UNDEFINED JAR) A JAR with the name specified on SQLJ.REPLACE_JAR or SQLJ.REMOVE_JAR does not exist in DB2. 2 (SCHEMA LENGTH) In the jar-name parameter, the schema exceeded the maximum length of 128 bytes. 3 (NAME LENGTH) In the jar-name parameter, the name exceeded the maximum of 128 bytes. 4 (PARSER ERROR) During SQLJ.INSTALL_JAR or SQLJ.REMOVE_JAR processing, the DB2 parser was invoked and returned an error. 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 SQLJ.INSTALL_JAR already exists in DB2.System action: The statement cannot be processed.

 <-  BACK TO INDEX