× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: sql cli handle leaks followup
  • From: jom@xxxxxxxxxxxxxxx (Jacob Madsen)
  • Date: Thu, 13 Apr 2000 17:47:31 +0200

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
 

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.