Results 1 to 14 of 14
  1. #1
    Join Date
    Feb 2012
    Posts
    19

    Unanswered: Apps hang after disconnect

    We ran into an issue after migration from 9.7.3 x86_32 to 9.7.5 x86_64 when users' applications hang after forced disconnect from database.

    Sometimes we need to perform particular procedures on a database and be sure that no one is connected. We make an announcement and if someone is still connected after a period of time, we force disconnect using Application List window in the Control Center.

    On a 9.7.3 if a user click somewhere in an application after a disconnect, he would get an error. On a 9.7.5 application hangs and user need to manually kill it from the Task Manager. We want to get rid of that and revert back to an "error" variant.

    But it's a tricky issue and I don't even know where to start digging.

    Any ideas?

  2. #2
    Join Date
    Feb 2012
    Posts
    19
    Guys, seriously..

  3. #3
    Join Date
    May 2003
    Location
    USA
    Posts
    5,737
    I would update the client driver to same fixpack as database server.
    M. A. Feldman
    IBM Certified DBA on DB2 for Linux, UNIX, and Windows
    IBM Certified DBA on DB2 for z/OS and OS/390

  4. #4
    Join Date
    Feb 2012
    Posts
    19
    Tried that. Updated DB2 client to the same 9.7.5 version. Same problem. The only difference is that server is 64-bit and client is 32-bit.

  5. #5
    Join Date
    Nov 2011
    Posts
    334
    If you disconnected from db2 successfully , maybe the problem is not on db2 side but on your own application。
    You can take a jdbc or odbc trace to see what happend。

  6. #6
    Join Date
    Feb 2012
    Posts
    19
    Quote Originally Posted by fengsun2 View Post
    If you disconnected from db2 successfully , maybe the problem is not on db2 side but on your own application。
    You can take a jdbc or odbc trace to see what happend。
    I can't call forced disconnection "successful". But still, on 32-bit 9.7.3 we didn't have this issue. Hence it's not an application fault.

    It's annoying, because when user just sees an error he could restart an application. Now helpdesk needs to explain everybody to go to Task Manager and kill it.
    Last edited by Harmont; 04-05-12 at 03:44.

  7. #7
    Join Date
    Feb 2012
    Posts
    19
    Any other ideas?

  8. #8
    Join Date
    May 2003
    Location
    USA
    Posts
    5,737
    Open an APAR with IBM support.
    M. A. Feldman
    IBM Certified DBA on DB2 for Linux, UNIX, and Windows
    IBM Certified DBA on DB2 for z/OS and OS/390

  9. #9
    Join Date
    Feb 2012
    Posts
    19
    Quote Originally Posted by Marcus_A View Post
    Open an APAR with IBM support.
    Our support period, which was 1 year after the purchase, has come to an end.

  10. #10
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650
    So, you do not have support for DB2 and you think it is DB2's problem. Not the situation I would like to be in.

    You can take a jdbc or odbc trace to see what happend。
    In your situation, this is the best you can do. Doing this might tell you the reason for the "hang" and you can address it from the application end [ hope you have support for that ].
    Visit the new-look IDUG Website , register to gain access to the excellent content.

  11. #11
    Join Date
    Feb 2012
    Posts
    19
    Quote Originally Posted by sathyaram_s View Post
    So, you do not have support for DB2 and you think it is DB2's problem. Not the situation I would like to be in.
    Thanks for being supportive.

    To the question. Can you suggest any tracing utility? Google might help. But I've never done tracing before. And taking the right path right away would be much better in my situation.

  12. #12
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650
    You haven't told how your app connects to db2. Have a look at the following line anyways

    CLI/ODBC/JDBC trace facility - IBM DB2 9.7 for Linux, UNIX, and Windows
    Visit the new-look IDUG Website , register to gain access to the excellent content.

  13. #13
    Join Date
    Feb 2012
    Posts
    19
    Our apps connect in different ways ODBC/BDE/dbExpress.

  14. #14
    Join Date
    Apr 2012
    Posts
    1,034
    Provided Answers: 18
    Quote Originally Posted by Harmont View Post
    Our apps connect in different ways ODBC/BDE/dbExpress.
    On your client workstations which client package are you using: the run time client (or whatever it is called now), or the full client (Data Server client), or the "Data Server Driver Package" or that standalone ODBC driver?

    If you are using one of the smaller clients, make a test with the Data-Server client package and compare the results.

    If your clients connect with JDBC, use a JDBC-trace on the client.
    If your clients connect with ODBC, use a CLI trace on the client.

    What you are looking for (in the trace output from the client) is an indication that the connection has been terminated or is broken in some way (tcpip error).

    This might be a 32-bit to 64-bit issue. If you have the full db2-client installed on any workstation then you can just use the db2-command-line window to examine if CLI connections get notified upon the first db2 command that happens at the client following the force action on the server.

    I'm assuming you already bound the correct packages post fixpack, to all databases.

    In your cli configuration check the
    impact on the symptom of varying the following settings:

    ConnectTimeout
    QueryTimeoutInterval
    ReceiveTimeout

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •