By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
454,279 Members | 1,629 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 454,279 IT Pros & Developers. It's quick & easy.

db cfg setup and SYSLH packages

P: n/a
I am getting -805 on SYSLH packages and I have already increase the
CLIPKG to 30. I am still getting -805.
Is there any db or dbm cfg setting that could cause DB2 to use new
SYSLH packages ?
Is there any benefit is doing a DB2JDBCBIND on top of the db2 bind with
clipgk 30. ?

thanks

Aug 7 '06 #1
Share this Question
Share on Google+
4 Replies


P: n/a
By using DB2JDBCBIND you can increase the number of SYSLH
packages....for example you can go to 50.

But the REAL issue here somewhere in the code the APPLICATION is not
releasing the HANDLES. This will happen primarily because of STATEMENT
HANDLE LEAKS.

cheers...
Shashi Mannepalli
Roger wrote:
I am getting -805 on SYSLH packages and I have already increase the
CLIPKG to 30. I am still getting -805.
Is there any db or dbm cfg setting that could cause DB2 to use new
SYSLH packages ?
Is there any benefit is doing a DB2JDBCBIND on top of the db2 bind with
clipgk 30. ?

thanks
Aug 7 '06 #2

P: n/a
thanks for the quick reply Shashi. How can i find the statement handle
leaks ? Also any ways to identify the sqls thats holding the handles.
I took a db2 application snapshot and it only showed SYSLH200 and
SYSLH202 and a few SYSSH200 series.
How does DB2 decide to use SYSSH vs SYSLH ?

thanks

Shashi Mannepalli wrote:
By using DB2JDBCBIND you can increase the number of SYSLH
packages....for example you can go to 50.

But the REAL issue here somewhere in the code the APPLICATION is not
releasing the HANDLES. This will happen primarily because of STATEMENT
HANDLE LEAKS.

cheers...
Shashi Mannepalli
Roger wrote:
I am getting -805 on SYSLH packages and I have already increase the
CLIPKG to 30. I am still getting -805.
Is there any db or dbm cfg setting that could cause DB2 to use new
SYSLH packages ?
Is there any benefit is doing a DB2JDBCBIND on top of the db2 bind with
clipgk 30. ?

thanks
Aug 7 '06 #3

P: n/a
http://publib.boulder.ibm.com/infoce...n/c0012277.htm

Search for HANDLES IN CLI

Temporarily you can resolve this by using DB2JDBCBIND with 50.
(hopefully that would be enough for your application)

Further informaton can be found ....

http://www-1.ibm.com/support/docview...=utf-8&lang=en

cheers...
Shashi Mannepalli
Roger wrote:
thanks for the quick reply Shashi. How can i find the statement handle
leaks ? Also any ways to identify the sqls thats holding the handles.
I took a db2 application snapshot and it only showed SYSLH200 and
SYSLH202 and a few SYSSH200 series.
How does DB2 decide to use SYSSH vs SYSLH ?

thanks

Shashi Mannepalli wrote:
By using DB2JDBCBIND you can increase the number of SYSLH
packages....for example you can go to 50.

But the REAL issue here somewhere in the code the APPLICATION is not
releasing the HANDLES. This will happen primarily because of STATEMENT
HANDLE LEAKS.

cheers...
Shashi Mannepalli
Roger wrote:
I am getting -805 on SYSLH packages and I have already increase the
CLIPKG to 30. I am still getting -805.
Is there any db or dbm cfg setting that could cause DB2 to use new
SYSLH packages ?
Is there any benefit is doing a DB2JDBCBIND on top of the db2 bind with
clipgk 30. ?
>
thanks
Aug 7 '06 #4

P: n/a
The application server is a vignette application running on WAS, but it
uses its own properitory JDBC API to talk to DB2 V8.2 . So it doesn't
go thru the DB2CLI.INI . I don't see any SQLFreeHandle statment, but
they do close the statement and close the result set. Also they don't
specify cursor hold on the application code, so I suspect its being set
at the API level.

Now my dilema is when I do db2pd -static -db datadb1 |grep SYSLH|wc -l
I see the numbers keep climbing every hour.

but when I do a DB2 APPLICATION SNAPSHOT, i only see SYSLH200
andSYSLH202 being held by applications. Why is that ?

I was expecting lot of other SHSLH2 series packages. Does increase
the statement or package heap size help ?

any input is greatly appreciated.
Shashi Mannepalli wrote:
http://publib.boulder.ibm.com/infoce...n/c0012277.htm

Search for HANDLES IN CLI

Temporarily you can resolve this by using DB2JDBCBIND with 50.
(hopefully that would be enough for your application)

Further informaton can be found ....

http://www-1.ibm.com/support/docview...=utf-8&lang=en

cheers...
Shashi Mannepalli
Roger wrote:
thanks for the quick reply Shashi. How can i find the statement handle
leaks ? Also any ways to identify the sqls thats holding the handles.
I took a db2 application snapshot and it only showed SYSLH200 and
SYSLH202 and a few SYSSH200 series.
How does DB2 decide to use SYSSH vs SYSLH ?

thanks

Shashi Mannepalli wrote:
By using DB2JDBCBIND you can increase the number of SYSLH
packages....for example you can go to 50.
>
But the REAL issue here somewhere in the code the APPLICATION is not
releasing the HANDLES. This will happen primarily because of STATEMENT
HANDLE LEAKS.
>
cheers...
Shashi Mannepalli
>
>
Roger wrote:
I am getting -805 on SYSLH packages and I have already increase the
CLIPKG to 30. I am still getting -805.
Is there any db or dbm cfg setting that could cause DB2 to use new
SYSLH packages ?
Is there any benefit is doing a DB2JDBCBIND on top of the db2 bind with
clipgk 30. ?

thanks
Aug 7 '06 #5

This discussion thread is closed

Replies have been disabled for this discussion.