Selecting "OLE DB Provider for DB2" freezes enterprise manager

  • SQL Server 2000 SP4

    Host Integration Server 2000

    Windows 2000

    Hi, whenever I go to add a linked server, as soon as I choose "Microsoft OLE DB Provider for DB2", enterprise manager freezes up and I have to kill it. This only started happening today and only for the DB2 provider. If I create it using sql in query analyzer, it creates the linked server but if I try to see it's properties in enterprise manager it freezes.

    If I try and query and existing DB2 linked server the query sits there forever without completing or returning an error.

    If I create a connection object in a DTS package I have no problems.

    To further confuse matters, one of the DB2 servers is having connection issues. I would assume these issues are related since they seemed to have started at the same time, except the "freezing" problem I'm having happens before I even enter a data source in the linked server properties. It's almost as if one DB2 server having issues caused all other DB2 linked servers to stop working.

    Any advice would be greatly appreciated!

  • Does the error log or Windows logs show anything?

    Joie Andrew
    "Since 1982"

  • Joie Andrew (1/11/2010)


    Does the error log or Windows logs show anything?

    No, but I found out that this statement was basically correct:

    "It's almost as if one DB2 server having issues caused all other DB2 linked servers to stop working."

    What seems to have happened is that as soon as you try to make one connection to the bad server, it "blocks" all other linked servers that use that DB2 OLE DB connection. Stopping and restarting the service would clear it up, and it would work until you tried connecting to the bad DB2 server.

    Anyways the DB2 servers were fixed and I stopped and restarted the SQL services so it's all working now.

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

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