Unable to configure Replication from SQL to Oracle

  • Hi,

    I am configuring a snapshot replication from SQL Server 2005 to Oracle 10g.

    After generating the article, when connecting to subscriber(Oracle 10g) I am getting the following error:

    The process could not connect to Subscriber 'ORCL'. (Source: MSSQL_REPL, Error number: MSSQL_REPL20084)

    SQL Server 2005 and Oracle 10g are running on the same box (Windows 2003 Server).

    Any quick response will be highly appreciated.

     

    Warm regards,

    Atiq Rahman

  • This was removed by the editor as SPAM

  • At a guess (because I've never tried this before), take a look at the permissions of the "user" doing the connecting. A "could not connect" message is typically about permissions but as I'm not familiar with the setup I can't be more specific.

    Good luck.


    Regards,

    Steve

    Life without beer is no life at all

    All beer is good, some beers are just better than others

  • Hi Atiq,

    I'm not attempting the exact same thing, but I received the same error message recently while trying to set up Peer-to-Peer replication between to SQL2005 servers.  As Steve has suggested, it was a user permissions issue in my case.  Basically, I had to make sure that everything - ie, all publications, all subscriptions, all jobs, everything, were running under a super-user account.  Setting anything up under a local system account is not just a bad security practice, it actually doesn't WORK, as your local sa will likely have problems with network privileges.

    So the best suggestion that I can make from my limited experience in this field is to try getting everything running under Windows security on a domain admin account.  In terms of security, maybe set up a new ReplicationAdmin account or something, with at least full SysAdmin rights on the servers (both the machines and the SQL instance), and full network admin rights.

    If that works, and you're worried about the extent of permissions, you can then try and eliminate permissions systematically and see what you can trim.

    -----------------

    C8H10N4O2

  • Hi,

    i faced the same problem.

    My problem was, that I had not installed the Oracle-Oledb part in my Oracle Client on the Sqlserver. (Odbc-Drivers are not sufficent)

    regards

    Hans G.

     

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

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