Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Transactional Replication to Oracle Expand / Collapse
Author
Message
Posted Monday, June 18, 2012 8:30 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Monday, August 27, 2012 8:07 PM
Points: 41, Visits: 114
Hi all,

I've got an issue with SQL Server 2005 Replication with Oracle.

Issue Summary:
When the replication is stopped and the tnsnames.ora file is modified to make the connection points to another Oracle database, the replication returns error when I try to start it again.

Environment Description:
I've successfully created a transactional replication from SQL Server 2005 (distributer) for a single table to Oracle server ( named as db1)(substriber). When I do the following, an error is raised:

1. SQL Server replication is stopped
2. the table is copied from Oracle db1 to another Oracle server db2 (the same schema name and password in both dbs)
3. hostname in tnsnames.ora file is changed to point to db2 server
4. the Server link in SQL Server tested and succeeded
5. when the replication is started, it returns error... the error is trying to re-initialize the table and claims the table is already there.

My questions are:
- Why SQL Server 2005 wants to reinitialize in the scenario described above?
- Is there a way to make SQL Server proceed with the synchronization without initialization?

By the way, if I set the hostname back to db1, the replication proceeds with synchronization without any problem.


Thanks in advance,
Post #1317695
Posted Thursday, June 21, 2012 10:47 AM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Tuesday, January 28, 2014 8:15 AM
Points: 3,068, Visits: 4,639
Well... if TNSNAMES is changed to point to a different database I would also want to re-initialize; new database, new replication schema.

_____________________________________
Pablo (Paul) Berzukov

Author of Understanding Database Administration available at Amazon and other bookstores.

Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.
Post #1319464
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse