Results 1 to 3 of 3
  1. #1
    Join Date
    Dec 2004
    Posts
    21

    Question Unanswered: Trying to add a Linked Server

    So, I need to bring data from db2 using sql server.
    I tried to add a Linked Server but I wasn't be able to do it.

    The Linked Server Properties was like this...

    Linked Server: <whatever: AAAA>
    Provider: IBM OLE DB Provider for DB2
    Product Name: <blank>
    Data Source: db2_teste (I put the name of db2 db in other server)
    Provider String: <blank>
    Location: lab23
    Catalog: <blank>

    So, but the case is where the db2 db is located there's a password and a user name. So I choose in "Security", "Be made using this security context:" :

    Remote Login: <the name and domain of administrator>
    With Password: <the password of the db2 db in that server>

    But it's failed...
    What Am I doing wrong?
    Any claus?
    Thanks previously

  2. #2
    Join Date
    Dec 2004
    Location
    CA, USA
    Posts
    63

  3. #3
    Join Date
    Dec 2004
    Posts
    21

    Thumbs up

    First pshisbey: Really thanks for replying my doubt.
    These links that you gave me are really nice =) Especially that one from MSDN.

    So, I found a way that made it works, but actually It was'nt the best practice of resolving the trouble =)
    The problem I think was with DB2 in server that I wanted to link. I unistalled it, and reinstalled... for surprise of all... it worked!

    This is the new configuration of my Linked Server Proprierties, for someone who is in same situation:

    Linked Server: AAAA
    Provider: IBM OLE DB Provider for DB2
    Product Name: <blank>
    Data Source: DB2 <the name of the db2 database>
    Provider String: IBMDADB2.1 or <blank>
    Location: lab23
    Catalog: <blank>

    In Security session: "Be made using this security context"

    Remote Login: test <the name of the db2 count>
    With Password: test123456 <the password you use to access db2 databases>

    As you see, there isn't any special diference in configuration, that's why I suspect that the error was in DB2.

    Thanks

Posting Permissions

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