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 |
|
tfountain
Constraint Violating Yak Guru
491 Posts |
 Posted - 2008-07-07 : 15:14:01
|
| I have a SQL 2005 server running as both the distributor and publisher. I'm pushing articles to an Oracle 10gR2 database. The first time the subscription is pushed everything works fine and all tables defined in the publication get moved over. Any subsequent pushes fail with the error:ORA-00955: name is already used by an existing object (Source: MSSQL_REPL_ORACLE, Error number: 955)The error is on a CREATE TABLE statement for a table named MSREPL7. It appears this table is created when the subscription is pushed but it is not dropped or recreated on subsequent pushes.Has anyone seen this type of error before and have any suggestions on how to resolve this? The MSREPL7 table appears to be information on what the subscription is and where it came from (it has identifying information on the SQL Server box that acts as dist/pub). It's not a table I configured as an article. |
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-07-07 : 16:30:33
|
| Why do you mean by subsequent push or do you mean reinitialize subscriber? I think you just push once and replication job will take care after that |
 |
|
|
tfountain
Constraint Violating Yak Guru
491 Posts |
Posted - 2008-07-07 : 16:38:11
|
quote:
Originally posted by sodeep
Why do you mean by subsequent push...
Subsequent means every time following the initial action...The replication works just fine so don't degress into questions regarding how it's setup. Anytime the subscriber is synchronized after the first time this error happens.One thing to note that this only appears to happen on subscriptions that are set to manual. Any continuous subscriptions do not exhibit this behavior. |
|
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-07-07 : 16:55:15
|
| so don't degress into questions regarding how it's setup. Did I ever degress into question? So Why the heck you are asking when you don't like answer? |
|
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-07-07 : 22:57:40
|
| >> It appears this table is created when the subscription is pushed but it is not dropped or recreated on subsequent pushes.You may check schema option in article properties, does it set to drop and recreate? |
|
|
|
tfountain
Constraint Violating Yak Guru
491 Posts |
Posted - 2008-07-09 : 09:54:55
|
quote:
Originally posted by rmiao
>> It appears this table is created when the subscription is pushed but it is not dropped or recreated on subsequent pushes.You may check schema option in article properties, does it set to drop and recreate?
Here is the funny thing, there is not an article for a table named MSREPL7. This appears to be a table that SQL Server creates on the subscriber. However, what I did find is if the distributor is set to run in continuous mode this table gets recreated everytime. It's only when the distributor runs in manual mode that this errors out on subsequent runs. I'm guessing Microsoft designed this to mean if in manual mode, assume it's a one time deal or something. Anyway, I worked around it by having the distributor run in continuous mode. Works better for me this way anyway. |
|
|
|
|
|
|
Manual snapshot push subscription error