Replace JAR failed in DB2 Development Center on AIX

[blackpzh]

We moved our DB[V8.1FP7] from one AIX[32bit] to another AIX[64bit] by
using backup/restore, ...it’s a long story..., then when we buid a
java stored procedure in development center, we got following message,
and a SQL0444N exception occurred.

################################################## ####################
####
MYDB.EXPORTMSTDATA - Build started.
javac -classpath
.:/home/db2inst1/sqllib/java/db2java.zip:/home/db2inst1/sqllib/java/ru
ntime.zip:/home/db2inst1/sqllib/java/sqlj.zip
ExportMstData.java
MYDB.EXPORTMSTDATA - Javac completed.
jar cf EXPORTMSTDATA.jar ExportMstData.class
MYDB.EXPORTMSTDATA - Jar file created.
Call SQLJ.DB2_REPLACE_JAR
(<</home/db2inst1/.ibm/db2/dc/Projects/bld1107315289621/EXPORTMSTDATA.
jar>>,’MYDB.EXPORTMSTDATA’)
[IBM][CLI Driver][DB2/AIX64] SQL0444N Routine
"SQLJ.DB2_REPLACE_JAR" (specific name "") is implemented with code
in library or path "", function "" which cannot be accessed.
Reason code: "". SQLSTATE=42724
MYDB.EXPORTMSTDATA - Build failed.
MYDB.EXPORTMSTDATA - Roll back completed successfully.
################################################## ####################
####

We also found a topic with very similar problem but on
windows.[http://www.dbforumz.com/DB2-developm...ct155415.html]

In this case, we didn’t find the temporary Jar file generated by
DB2DC. Anybody can help?

regards,
Arthur

--
Posted using the http://www.dbforumz.com interface, at author's request
Articles individually checked for conformance to usenet standards
Topic URL: http://www.dbforumz.com/DB2-Replace-...ict194076.html
Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.dbforumz.com/eform.php?p=656674

[HoT!cE]

Hi,please read the topic: db2 store procedure build failed.(aix 64bit
server)

infact we also move DB[V8.1FP7] from one AIX[32bit] to another
AIX[64bit] by
using backup/restore and same problem happend.

Develop center seems not be able to call the Routine
"SQLJ.DB2_REPLACE_JAR" or "SQLJ.DB2_INSTALL_JAR" etc.

at last , we reinstalled the db2 server to be a Aix[32bit] db , and
restore again,then this issue is gone.
please try it.