Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Replication Headaches

230 views
Skip to first unread message

Dave MacKinnon

unread,
Jan 4, 2002, 2:30:41 PM1/4/02
to
Greetings all,
I'm sorry, but this is going to be a long post. We run a
program called Pivotal as our CRM system. It used SQL 2K
enterprise as it's back end, and I do have it clustered. I
have setup replication of the databases to our DR site,
and all was working well. A few weeks ago, we had a major
problem with the database, a result of the CRM app. I
ended up doing a SQL dump of an identical database and
then restoring it to our production system. Doing this
worked, for all intensive purposes. The one thing that did
not work was replication. We replicate 3 databases, and I
was able to stop replication on 2 of them. The third is
getting the following errors:
"Error 208: Invalid object name 'sysarticles'"
"Invalid object name 'sysschemaarticles"
"Could not use view or function 'sysentendedarticlesview'
because of binding errors"

So this started like 2 weeks ago. Today I decided to
build a new server and install SQL on it. I then did a
SQL backup from the EM and restored it to the new server.
This worked fine. The new server didn't have any
replication issues at all. This leads me to believe that
something is foobar'd with the SQL server itself, not the
database.

Does anyone have any ideas. Any help would be greatly
appreciated.
Thanks,
Dave

Jim Johnston

unread,
Jan 5, 2002, 4:11:44 PM1/5/02
to
I have had this error before whenever I have tried to create a merge pull
subscription
on an old database (that had been created with a previous snapshot or
publication) Fastest way I
found to correct the problem was delete the old database, and snapshot a new
one to the subscriber
when I create the new subscription. Sorry for the blunt approach, but this
was easier for me than trying to get into
the sysschemaarticles/sysarticles table(s) and correct the problem.

V/R Jim Johnston


"Dave MacKinnon" <dmack...@secureworks.net> wrote in message
news:5e2401c19556$4bdaa170$19ef2ecf@tkmsftngxa01...

Dave MacKinnon

unread,
Jan 5, 2002, 6:56:40 PM1/5/02
to
Jim,
Thanks for the info. I had previously tried to delete the
database, but it would not allow me to do so because it
thinks it's replicating. I guess I should've posted that
info too. Thanks again.
Dave
>.
>

J.P. Rhea

unread,
Jan 7, 2002, 12:11:20 PM1/7/02
to
exec sp_removedbreplication 'dbname'.

This will allow you to delete the db.

J.P.

"Dave MacKinnon" <dmack...@secureworks.net> wrote in message

news:580201c19644$9ebb1d90$a4e62ecf@tkmsftngxa06...

Mike Hotek

unread,
Jan 8, 2002, 3:18:52 PM1/8/02
to
Maybe. It doesn't always work. Make sure you turn off
the database options telling that it is suybscribed.
After that, drop the database and start over.

Don't apologize for a blunt approach. In many cases,
simple is usually the best method.

Mike
SQL Server MVP

>.
>

0 new messages