runaway sqls 
November 4th, 2008, 05:15 PM
| | | |
Hello,
Sometime, clients disconnect after starting sql and sql keep running
in the db2 engine making it a runaway sql.
is there something in DB2 which can avoid this behavior i.e. clean any
agents/subagents/sqls when client is no longer connected ?
|
November 4th, 2008, 05:45 PM
| | | | re: runaway sqls
On 4 Nov, 18:10, db2admin <jag...@gmail.comwrote: Quote:
Hello,
>
Sometime, clients disconnect after starting sql and sql keep running
in the db2 engine making it a runaway sql.
is there something in DB2 which can avoid this behavior i.e. clean any
agents/subagents/sqls when client is no longer connected ?
|
I’m not sure if SET CLIENT command can help you; see following link: http://publib.boulder.ibm.com/infoce.../r0001999.html
Regards
Salvatore Vacca |
November 5th, 2008, 05:15 PM
| | | | re: runaway sqls
On Nov 4, 12:37*pm, Salvatore Vacca <s.va...@gmail.comwrote: Quote:
On 4 Nov, 18:10, db2admin <jag...@gmail.comwrote:
>> Quote:
Sometime, clients disconnect after starting sql and sql keep running
in the db2 engine making it a runaway sql.
is there something in DB2 which can avoid this behavior i.e. clean any
agents/subagents/sqls when client is no longer connected ?
| >
I’m not sure if SET CLIENT command can help you; see following link:
>
http://publib.boulder.ibm.com/infoce...dex.jsp?topic=....
>
Regards
Salvatore Vacca
| thankyou,
i am going to look into that
i also noticed this DB2CHECKCLIENTINTERVAL parameter
is this something which can also help to clean runaway sql ? |
November 5th, 2008, 05:25 PM
| | | | re: runaway sqls
Hi!
Will you please publish the results if you succeed!
Thanks
/dg
"db2admin" <jagdip@gmail.comwrote in message news:55eb88f0-c4f6-482e-b5e6-fb65050f1b3f@f37g2000pri.googlegroups.com... Quote:
Hello,
>
Sometime, clients disconnect after starting sql and sql keep running
in the db2 engine making it a runaway sql.
is there something in DB2 which can avoid this behavior i.e. clean any
agents/subagents/sqls when client is no longer connected ?
| |
November 5th, 2008, 05:35 PM
| | | | re: runaway sqls
On 5 Nov, 18:14, db2admin <jag...@gmail.comwrote: Quote:
On Nov 4, 12:37*pm, Salvatore Vacca <s.va...@gmail.comwrote:
> Quote: |
On 4 Nov, 18:10, db2admin <jag...@gmail.comwrote:
| >> Quote: Quote:
Sometime, clients disconnect after starting sql and sql keep running
in the db2 engine making it a runaway sql.
is there something in DB2 which can avoid this behavior i.e. clean any
agents/subagents/sqls when client is no longer connected ?
| | > Quote: |
I’m not sure if SET CLIENT command can help you; see following link:
| >>>
thankyou,
i am going to look into that
i also noticed this DB2CHECKCLIENTINTERVAL parameter
is this something which can also help to clean runaway sql ?
|
It depends on which version of db2 are you using; as you can see from
documentation the default value of DB2CHECKCLIENTINTERVAL is 50 for
version >= 8.1.4, prior to version 8.1.4, the default value was 0 (no
client connection verifications is performed). http://publib.boulder.ibm.com/infoce.../r0005660.html |  |
| | |  /bytes/about
We are a network of experts and professionals in IT and software development that help one another with answers to tough questions and share insights.
Get the best answers to your questions from over 225,662 network members.
|
