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

Invalid statement

P: n/a
We are getting this error every other day during the ETL run. It seems
to be random. What is the best solution?

DB2 AIX 8.1.5.

COM.ibm.db2.jdbc.DB2Exception: [IBM][JDBC Driver] CLI0601E Invalid
statement handle or statement is closed. SQLSTATE=S1000

Thank You.
-Jane

Aug 15 '06 #1
Share this Question
Share on Google+
2 Replies


P: n/a
jane wrote:
We are getting this error every other day during the ETL run. It seems
to be random. What is the best solution?

DB2 AIX 8.1.5.

COM.ibm.db2.jdbc.DB2Exception: [IBM][JDBC Driver] CLI0601E Invalid
statement handle or statement is closed. SQLSTATE=S1000
Usually, that's a problem in the application. Run a JDBC trace and see
what's going on at the communication level between the app and DB2. My
guess would be that you have not turned off auto-commit. Maybe you're
sharing connections and multiple threads interfere with each other...

--
Knut Stolze
DB2 Information Integration Development
IBM Germany
Aug 15 '06 #2

P: n/a
hi,

If db2java.zip is prior to DB2 Version 7 FixPak 2:

COM.ibm.db2.jdbc.DB2Exception: [IBM][JDBC Driver]
CLI0601E Invalid statement handle or statement is closed.
SQLSTATE=S1000
If a mismatch occurs, the JDBC applet server logs one of the following
messages in the jdbcerr.log file:

have a look at the fixpack

cheers

Knut Stolze wrote:
jane wrote:
We are getting this error every other day during the ETL run. It seems
to be random. What is the best solution?

DB2 AIX 8.1.5.

COM.ibm.db2.jdbc.DB2Exception: [IBM][JDBC Driver] CLI0601E Invalid
statement handle or statement is closed. SQLSTATE=S1000

Usually, that's a problem in the application. Run a JDBC trace and see
what's going on at the communication level between the app and DB2. My
guess would be that you have not turned off auto-commit. Maybe you're
sharing connections and multiple threads interfere with each other...

--
Knut Stolze
DB2 Information Integration Development
IBM Germany
Aug 17 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.