Linked server error

  • Hi everyone

    I'm trying to set up an Oracle linked server from a MSSQL Server, and failing miserably.

    However, i'm pretty sure i'm just missing a step or two.

    Here's what i got so far:

    My SQL Server is running under an AD account, with minimum privileges.

    The Oracle Client tools are installed and working correctly.

    However, when i try to set up an oracle linked server, i get the following error:

    "Oracle client and networking components were not found.."

    So, just to try, i changed the startup account to local system, and the linked server worked perfectly, so, the answer should be in the configuration of the component services and adding the service startup account to the correct component. But i don't have any idea of the permissions that i should grant to the account. If any of you have any clue or thought about this, i'll really appreciate it

    I hope i haven't bored you guys with this long first post.

    😎

  • These links might help. Also what is version of oracle you are trying to connect to

    http://support.microsoft.com/kb/280106

    http://support.microsoft.com/kb/259959/

  • Bobby (4/14/2009)


    These links might help. Also what is version of oracle you are trying to connect to

    http://support.microsoft.com/kb/280106

    http://support.microsoft.com/kb/259959/%5B/quote%5D

    Thanks, i didn't know about these links, but it appears that the installation and configuration of the oracle 9.2 client tools is ok.

    Investigating a little more, i gave the network service account (since it's used by MSDTC) read permission on the oracle installation folders ,the oracle home and the one in program files, but still , no dice.

    Any ideas of what else i might be missing? I really don't want to put the SQL startup account in the administrators group if there's other way.

  • And it's solved! 😀

    I used the oracle provider intead of the one provided by microsoft and gave the startup account the permissions for local and remote activation of MSDAINITIALIZE.

    Now all that is left is to document the changes and try them in the QA enviroment before migrating it into production (i tampered with too many things and my development box is a mess)

    Once that is done, i'll post back the step by step for any other that had the same problem

    Thanks for your help!

    EDIT:

    Actually, the permissions for MSDAINITIALIZE was all i needed to set up the linked server against oracle.

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

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