Hi there.
Recently, one of our application servers is moaning about its handles.
(no more handles available).
I'm guessing it has to do with some bug in our software where it does
not release handles properly and every x thousand queries, one available
handle gets lost (unreleased).
Are handles available PER application, or is there one general pool of
handles from which agents get their share?
In DB2 8.2 LUW 64bit, how many handles are available?
Can this limit be changed or is it hardcoded?
Can I get an overview of handles in use/available (I know about the
application snapshot, but I was hoping for something a little more...
brief.)
Can I assume for every cursor in use, 1 handle is allocated en vice
versa? Or is this wrong to think when you have a query that operates on
multiple datebbase objects. (for instance, 1 query that joins over 3
tables. Is that 1 handle and 3 cursors?)
Perhaps someone knows of some interesting reading on this subject.
Searching for handles in 1 pain in the ** because all I get is how DB2
is *handling* some stuff.
Thanks.
-R-
Recently, one of our application servers is moaning about its handles.
(no more handles available).
I'm guessing it has to do with some bug in our software where it does
not release handles properly and every x thousand queries, one available
handle gets lost (unreleased).
Are handles available PER application, or is there one general pool of
handles from which agents get their share?
In DB2 8.2 LUW 64bit, how many handles are available?
Can this limit be changed or is it hardcoded?
Can I get an overview of handles in use/available (I know about the
application snapshot, but I was hoping for something a little more...
brief.)
Can I assume for every cursor in use, 1 handle is allocated en vice
versa? Or is this wrong to think when you have a query that operates on
multiple datebbase objects. (for instance, 1 query that joins over 3
tables. Is that 1 handle and 3 cursors?)
Perhaps someone knows of some interesting reading on this subject.
Searching for handles in 1 pain in the ** because all I get is how DB2
is *handling* some stuff.
Thanks.
-R-
Comment