When it is running do a
db2 list application
If you are showing lots of connects - thats a problem.
if not,
db2 get snapshot for applications on dbname
If your app is showing lots and lots of sections in the snapshot - that points to there being lots of unclosed statements lying around.
Regards, Wayne
James Collins wrote:
Help Tim!!! I'm been backwards, forwards, and all over this code. It is, admittedly, processing millions of records, and the code is 3808 lines long. But I am _convinced_ that I Connect to the various database connections at the beginning of execution, discconect at the end, and in-between cycle through a process of Prepare, Execute, Fetch or Commit and Finish over and over of course.
Is there something I can call to clear used statement handles?
I am using Redhat 9 and DB2 Version 8 with the latest fixpacks all properly bound up and everything. perl-5.8.0-88. Perl Client and DB2 server are two different machines (Same OS config). Both equalised.
After approxiamately 50,000 iterations, it dies with the below...
prepare SQL statement: [IBM][CLI Driver] CLI0129E No more handles. SQLSTATE=HY014 [EMAIL PROTECTED] db2 "? CLI0129E"
CLI0129E No more handles.
Explanation:
A call was made to SQLAllocEnv, SQLAllocConnect, or SQLAllocStmt but no more handles are available in the driver.
User Response:
Call SQLFreeEnv, SQLFreeConnect, or SQLFreeStmt to free up some handles which are no longer being used in the application.
