Re: sql cli handle leaks followup

[jom@xxxxxxxxxxxxxxx (Jacob Madsen)]

Hi all

 

Just some final advice to all, who might have been fighting with this problem:

 

com.ibm.db2.jdbc.app.DB2SQLException2: SQL CLI (Call Level Interface) error
      com/ibm/db2/jdbc/app/DB2StatementRuntimeImpl.allocStmt(IIII)I+17(DB2StatementRuntimeImpl.java:74)
      com/ibm/db2/jdbc/app/DB2Statement.<init>(Lcom/ibm/db2/jdbc/app/DB2Connection;IIZ)V+315 (DB2Statement.java:248)
      com/ibm/db2/jdbc/app/DB2Connection.createStatement(II)Ljava/sql/Statement;+64 (DB2Connection.java:494)
      com/ibm/db2/jdbc/app/DB2Connection.createStatement()Ljava/sql/Statement;+19(DB2Connection.java:455)
 

Remember *always* to close your Statement objects immediatly after you're done with them, and you will be saved for a lot of trouble later, if your application crashes. Exception messages like "SQL CLI (Call Level Interface) error" and "[ODBC Driver Manager] Function sequence error" (I once had this exception with an ODBC connection, but the problem has proven to be the same) are really not of much value, so you could spend a lot of time chasing the cause of this error - I did once. But now I've become that experience richer.

 

Thanks again to Alex Garrison, who took MY problem seriously and helped out work it out.

 

Jacob