From: Mark A on 6 Nov 2006 18:26 db2group88 wrote: > the MAXAPPLS is 500 and APPLHEAPSZ is 12000, i have make sure statement > close properly. what else? What exactly does "close properly" mean? Do you do an explicit commit?
From: Gregor Kova? on 7 Nov 2006 06:44 db2group88 wrote: > we had this error while running the applicaiton on db2 v8.2 EE on > windows, jcc driver is what we use > > SQL error 805 > > com.ibm.db2.jcc.b.SQLException: NULLID.SYSLH203 0X5359534C564C3031, > based on my experience, there is no such package exist, so what would > be the main resaon behind this? thank you Hi! When I get this I do: db2jdbcbind.exe -url jdbc:db2://SERVER:50000/DATABASE_NAME -user DATABASE_USER -password DATABASE_PASSWORD -size 300 Best regards, Kovi -- -~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- | In A World Without Fences Who Needs Gates? | | Experience Linux. | -~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
From: Knut Stolze on 7 Nov 2006 10:09 db2group88 wrote: > we had this error while running the applicaiton on db2 v8.2 EE on > windows, jcc driver is what we use > > SQL error 805 > > com.ibm.db2.jcc.b.SQLException: NULLID.SYSLH203 0X5359534C564C3031, > based on my experience, there is no such package exist, so what would > be the main resaon behind this? thank you The main reason is that you do _not_ properly close your statement handles in your application. Each statement handle is associated with a package, and since you don't close them, you run out of packages eventually. You can delay the problem by creating more CLI packages - maybe the delay is sufficient that you won't hit the problem anymore - but that's not a fix. A good description on CLI packages can be found here: http://www.ibm.com/developerworks/db2/library/techarticle/dm-0606chun/index.html -- Knut Stolze DB2 Information Integration Development IBM Germany
First
|
Prev
|
Pages: 1 2 Prev: DB2 and extended ASCII table Next: slow connection to DB2/LINUX 8.2.3 |