Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2002-05-31 : 09:09:23
|
| Gregory writes "I currently have replication setup from a MSSQL2k machine to Oracle 8.1.5 and while the replication works, it times out every time there is a hiccup in the network. It acts as if it won't retry like it does from MSSQL2k to MSSQL2k. I'm using Microsoft ODBC for Oracle for my connection. Any ideas?" |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2002-05-31 : 09:26:55
|
| Have you tried using OLE DB providers for Oracle instead of ODBC? Microsoft has an OLE DB provider for Oracle, and Oracle also has one of their own. I've never tried replication, especially like this, but whenever I see Oracle and ODBC in the same sentence I harken back to the good ol' days (not) when Oracle-ODBC combinations drove me insane, and OLE DB was a salvation. |
 |
|
|
JamesH
Posting Yak Master
149 Posts |
Posted - 2002-05-31 : 14:28:35
|
| You might try scheduling your logreader and distributor agents on your own schedule rather than continuous. I have had pretty good success with this as if one minute the logreader/distributor fails, they usually pick up the next minute. The main problem you run into with the transactions repl is that after the retry attempts (default 10) have failed, your agent will go suspect and if it is a large amount of data, re-initializing can cause some serious problems including blocking in production. If you've already identified that the network is having 'hiccups', then I would definately give it a shot, start by setting the logreader agent to run every minute, if you still have problems, set the distribution agent to every minute. If these don't work, send more information...HTH,JamesH. |
|
|
|
|
|
|
|
|
SQL2000 replication to Oracle