Queries against DB2 linked server can't be killed

  • We have a problem which has proven intractable for about two weeks. We are running SQL Server 2000 with SP3 on Windows 2000. We haven't installed SP 3a because it doesn't seem to explicitly address the problems we are having.

    We have linked servers to a DB2 environment (OS/390), all set up with the IBM DB2 OLEDB drivers, part of the IBM CLI version 7.2.

    Everything was hunky-dory until about 2 weeks ago, when SELECT queries run against these servers began to exhibit strange behavior (same behavior for OPENQUERY and 4-part syntax):

    1) the query never returns results

    2) when the query is cancelled, it shows this message: "Rollback in progress. 100% complete." Since these are SELECT statements only, we are baffled as to why a rollback would be occurring...

    3) the PID never goes away, despite repeated attempts to kill it. By never, I mean 3 days or more.

    4) the DB2 system does not show any activity after the kill attempt (i.e., the query is no longer live on the DB2 side)

    5) eventually, after 2 or 3 of these PIDs are active, the entire server slows to a crawl

    6) reboot clears up the problem until the next time

    We've tried a lot of things:

    1) reinstalled the IBM client software

    2) rebuilt the linked servers

    3) rebuilt the server (i.e., reinstalled OS and all software)

    4) installed a new network card (in the off chance that it was a packet loss issue)

    Thanks in advance for any suggestions you can offer.

    Andy Hilliard

    Organon Professional Services

    -Andy Hilliard

    VP, Organon Professional Services

    Andy Hilliard
    Owl Creek Consulting[/url]

  • This was removed by the editor as SPAM

  • If you have any support this will be the time to contact them

    Mike

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply