CLI0601E
in [DB2]
|
Prev: [IBM][JDBC Driver] CLI0601E
Next: RESOLVED
From: Bernd Hohmann on 17 Jan 2007 12:03 Roger wrote: > My dev team is getting this error when they run big load program : > COM.ibm.db2.jdbc.DB2Exception: [IBM][JDBC Driver] CLI0601E Invalid > statement handle or statement is closed. SQLSTATE=S1000 > . > The application runs fine when they run small loads. I checked the Db2 > client FP..its on DV2 V8 FP10. Wild guess: another thread retrieves a statement from the connection in the meantime and executes it or there is only one statement handle and a different threads uses this handle from time to time. Bernd -- What do you get when you cross a mail pigeon with a parrot ? Voice mail
From: Roger on 17 Jan 2007 13:55 I don't think thats the case. We are running the insert process by itself. Bernd Hohmann wrote: > Roger wrote: > > > My dev team is getting this error when they run big load program : > > COM.ibm.db2.jdbc.DB2Exception: [IBM][JDBC Driver] CLI0601E Invalid > > statement handle or statement is closed. SQLSTATE=S1000 > > . > > The application runs fine when they run small loads. I checked the Db2 > > client FP..its on DV2 V8 FP10. > > Wild guess: another thread retrieves a statement from the connection in > the meantime and executes it or there is only one statement handle and a > different threads uses this handle from time to time. > > Bernd > > -- > What do you get when you cross a mail pigeon with a parrot ? Voice mail
From: aj on 17 Jan 2007 14:06 Is there a connection pooling mechanism? Could something be timing out on big loads and cutting the connection? Roger wrote: > I don't think thats the case. We are running the insert process by > itself. > > > Bernd Hohmann wrote: >> Roger wrote: >> >>> My dev team is getting this error when they run big load program : >>> COM.ibm.db2.jdbc.DB2Exception: [IBM][JDBC Driver] CLI0601E Invalid >>> statement handle or statement is closed. SQLSTATE=S1000 >>> . >>> The application runs fine when they run small loads. I checked the Db2 >>> client FP..its on DV2 V8 FP10. >> Wild guess: another thread retrieves a statement from the connection in >> the meantime and executes it or there is only one statement handle and a >> different threads uses this handle from time to time. >> >> Bernd >> >> -- >> What do you get when you cross a mail pigeon with a parrot ? Voice mail >
From: Bernd Hohmann on 17 Jan 2007 14:05 Roger wrote: > I don't think thats the case. We are running the insert process by > itself. In this case: define "big load program".... If the connection idles for a long while, it will be closed by the tcp/ip stack as every other tcp/ip connection. We had this case a while ago. Either you invent a ping-thread using the same connection (which won't work here because you're waiting for the result) or tune the timeout settings of the workstations tcp/ip stack. Bernd -- What do you get when you cross a mail pigeon with a parrot ? Voice mail
From: Roger on 17 Jan 2007 14:32
I am not using connection pooling. Runs on a type 4 driver. It runs for 1 hr and then gets the error Bernd Hohmann wrote: > Roger wrote: > > > I don't think thats the case. We are running the insert process by > > itself. > > In this case: define "big load program".... If the connection idles for > a long while, it will be closed by the tcp/ip stack as every other > tcp/ip connection. > > We had this case a while ago. Either you invent a ping-thread using the > same connection (which won't work here because you're waiting for the > result) or tune the timeout settings of the workstations tcp/ip stack. > > Bernd > > -- > What do you get when you cross a mail pigeon with a parrot ? Voice mail |