By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,334 Members | 1,328 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,334 IT Pros & Developers. It's quick & easy.

Emergency question about SQL0818 gotten on SQLJ proc

P: n/a
Dear all,

We try to isolate on Windows 8.2 FP8/FP9 a problem or a bug ? we have on
call's on SQLJ procs.

Call proc gives SQL0818 indicating a mismatch between the JAR and package
(all was done thru Dev Center). Checking syscat.packages gives the same
constitency token as a db2sqljprint of the ser file taken out from the JAR.
.... strange, isn't it ? No classes or Jar files found on the server.

db2stop / db2start, then call proc --> it works.

Has any body encountered such a problem and could help us ? We have applied
FP9, and did not get rid of this problem.

Could a missing explicit connection context in some procs lead to this
SQL0818 ? The DB2 Information Center tells that this missing context can
lead to "unexpected failures" ...

Thanks for your help,

JM
Nov 12 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a

"Jean-Marc Blaise" <no****@nowhere.com> a écrit dans le message de
news:42*********************@news.wanadoo.fr...
Dear all,

We try to isolate on Windows 8.2 FP8/FP9 a problem or a bug ? we have on
call's on SQLJ procs.

Call proc gives SQL0818 indicating a mismatch between the JAR and package
(all was done thru Dev Center). Checking syscat.packages gives the same
constitency token as a db2sqljprint of the ser file taken out from the JAR. ... strange, isn't it ? No classes or Jar files found on the server.

db2stop / db2start, then call proc --> it works.

Has any body encountered such a problem and could help us ? We have applied FP9, and did not get rid of this problem.

Could a missing explicit connection context in some procs lead to this
SQL0818 ? The DB2 Information Center tells that this missing context can
lead to "unexpected failures" ...

Thanks for your help,

JM

No classes or Jar files found on the server... other than the normal ones
under SQLLIB\function\JAR\Schema I meant ...

Nov 12 '05 #2

P: n/a
I have found this note related to SQL0805 ...

http://www-1.ibm.com/support/docview...=utf-8&lang=en

I guess you could extrapolate to SQL0818 for SQLJ routines, as the packages
keeps being the sames.

The link
http://publib.boulder.ibm.com/infoce...d/c0010019.htm
related to context connection tells about "unexpected failures", that's all.

Basically, I personally think the IBM support site needs to be enhanced with
more info... as well as the documentation.
"Jean-Marc Blaise" <no****@nowhere.com> a écrit dans le message de
news:42***********************@news.wanadoo.fr...

"Jean-Marc Blaise" <no****@nowhere.com> a écrit dans le message de
news:42*********************@news.wanadoo.fr...
Dear all,

We try to isolate on Windows 8.2 FP8/FP9 a problem or a bug ? we have on
call's on SQLJ procs.

Call proc gives SQL0818 indicating a mismatch between the JAR and package (all was done thru Dev Center). Checking syscat.packages gives the same
constitency token as a db2sqljprint of the ser file taken out from the

JAR.
... strange, isn't it ? No classes or Jar files found on the server.

db2stop / db2start, then call proc --> it works.

Has any body encountered such a problem and could help us ? We have

applied
FP9, and did not get rid of this problem.

Could a missing explicit connection context in some procs lead to this
SQL0818 ? The DB2 Information Center tells that this missing context can
lead to "unexpected failures" ...

Thanks for your help,

JM

No classes or Jar files found on the server... other than the normal ones
under SQLLIB\function\JAR\Schema I meant ...

Nov 12 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.