runaway sqls

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • db2admin
    #1

    runaway sqls

    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 ?
    Tags: None
    • Salvatore Vacca
      #2
      Re: runaway sqls

      On 4 Nov, 18:10, db2admin <jag...@gmail.c omwrote:
      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/infocenter/db2luw/v9r5/index.jsp?topic=/com..ibm.db2.luw.admin.cmd.doc/doc/r0001999.html


      Regards
      Salvatore Vacca

        Comment

        • db2admin
          #3
          Re: runaway sqls

          On Nov 4, 12:37 pm, Salvatore Vacca <s.va...@gmail. comwrote:
          On 4 Nov, 18:10, db2admin <jag...@gmail.c omwrote:
          >
          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...dex.jsp?topic=....
          >
          Regards
          Salvatore Vacca
          thankyou,
          i am going to look into that
          i also noticed this DB2CHECKCLIENTI NTERVAL parameter
          is this something which can also help to clean runaway sql ?

            Comment

            • Dan van Ginhoven
              #4
              Re: runaway sqls

              Hi!

              Will you please publish the results if you succeed!
              Thanks
              /dg

              "db2admin" <jagdip@gmail.c omwrote in message news:55eb88f0-c4f6-482e-b5e6-fb65050f1b3f@f3 7g2000pri.googl egroups.com...
              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 ?

                Comment

                • Salvatore Vacca
                  #5
                  Re: runaway sqls

                  On 5 Nov, 18:14, db2admin <jag...@gmail.c omwrote:
                  On Nov 4, 12:37 pm, Salvatore Vacca <s.va...@gmail. comwrote:
                  >
                  On 4 Nov, 18:10, db2admin <jag...@gmail.c omwrote:
                  >
                  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...dex.jsp?topic=....
                  >
                  Regards
                  Salvatore Vacca
                  >
                  thankyou,
                  i am going to look into that
                  i also noticed this DB2CHECKCLIENTI NTERVAL 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 DB2CHECKCLIENTI NTERVAL 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/infocenter/db2luw/v9r5/index.jsp?topic=/com..ibm.db2.luw.admin.regvars.doc/doc/r0005660.html


                    Comment

                    Previous template Next
                    Working...