Re: Publishers disappeared from under replication monitor
From: michelle (michelle_at_nospam.com)
Date: 08/09/04
- Next message: Dan: "Schema Changes After Publishing"
- Previous message: Oussama Albairat: "context in trigger"
- In reply to: Hilary Cotter: "Re: Publishers disappeared from under replication monitor"
- Next in thread: Hilary Cotter: "Re: Publishers disappeared from under replication monitor"
- Reply: Hilary Cotter: "Re: Publishers disappeared from under replication monitor"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 9 Aug 2004 14:05:09 -0500
Not exactly but what was done could have had the same effect...
We had a problem a couple of weeks ago. I'll try to make a long story short.
Basically the only database on the server being replicated suddenly had 'no'
tables showing up. This happened at the same time that the job that backup
the transaction logs failed (SQL LiteSpeed). We have a support case open
with MS but at this point they are asking that we pursue it with LiteSpeed
(yet we do not have a support contract). We were getting assertion errors.
Not sure if you care to hear about the details of that...
This seemed like some kind of corruption in the database. We thought that we
would first try to detach and re-attach the files but since it was being
replicated, we were unable to do so because it was being replicated. One of
the other DBAs here 'deleted everything from the distribution database' (I
think that's what he said). I explained that the user database kept
replication 'stuff' in it, too so that would not do any good. Too Late.
Even a restore would require that we get rid of the existing database so we
restarted the sql server service to see what happened. Lo-and-behold, the
database came back up.
The next day we set up transactional replication again (Yes, probably used
the same name). It seemed to be fine. I don't actually recall if the
publisher was showing up at that time or not. Someone later rebooted the
server with the subscriber on it and the jobs did not start back up on the
publisher (couldn't authenticate job owner, have now changed job owner).
That's the only reason why I noticed that there was even a problem. When I
tried to get it running again, it had to retry numerous times: The process
could not execute 'sp_replcmds' on 'servername'. But, I did get it running.
Due to all of this mess, I was going to try to use the validate subscription
thing but I couldn't find it. I ended up just doing row counts. That
combined with my understanding of the OLTP activity and checking with the
users of the subscriber, it seems to be fine - except that it is missing
from the replication monitor folder.
Plus, the conflict tables are called aonflict instead of conflict. I had
already researched this and believe that it is not anything to worry about.
I was thinking of waiting until after the sql server service was restarted
and if it is still not right, setting up a maintenance window to drop the
publication, disable this server as a publisher, drop the distribution
database, and start over.
What do you think?
"Hilary Cotter" <hilaryk@att.net> wrote in message
news:u%23u8dCkfEHA.644@tk2msftngp13.phx.gbl...
> Can you give me a history of this problem.
>
> Note that if you script out publications and recreate them on the same
> server but in different databases and have the same snapshot agent and
> distribution agent name you can get a condition like this.
>
> By chance did you do something like this?
>
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
>
> "michelle" <michelle@nospam.com> wrote in message
> news:u$PVj7jfEHA.720@TK2MSFTNGP11.phx.gbl...
> > Same as Ray:
> >
> > Server: Msg 208, Level 16, State 1, Procedure
> sp_MSload_replication_status,
> > Line 14
> > Invalid object name 'tempdb.dbo.MSreplication_agent_status'.
> >
> > Which is why I restarted the agent service. It didin't help me out
though.
> >
> >
> > "Hilary Cotter" <hilaryk@att.net> wrote in message
> > news:ewTOZxjfEHA.2468@TK2MSFTNGP12.phx.gbl...
> > > what happens when you issue this command?
> > >
> > > sp_MSload_replication_status
> > >
> > > --
> > > Hilary Cotter
> > > Looking for a book on SQL Server replication?
> > > http://www.nwsu.com/0974973602.html
> > >
> > >
> > > "michelle" <michelle@nospam.com> wrote in message
> > > news:%23UIngtjfEHA.632@TK2MSFTNGP12.phx.gbl...
> > > > We have this problem on one of our servers. We tried restarting the
> > agent
> > > > service but that did not resolve this. Is is so crucial that we
> identify
> > a
> > > > maintenance window asap to take care of this or do you think that it
> can
> > > > wait a few days? It does not seem to be causing any problems. The
> > machine
> > > > will most likely be rebooted in the near future for security
patches,
> > > > anyway.
> > > >
> > > > Michelle
> > > >
> > > >
> > > >
> > > > You hit the nail on the head. Restarting the SQL agent cured the
> > problem.
> > > >
> > > > Many thanks!
> > > >
> > > > Ray
> > > >
> > > > "Hilary Cotter" <hilaryk@att.net> wrote in message
> > > > news:O96$4HLVEHA.2992@TK2MSFTNGP12.phx.gbl...
> > > > > that's your problem. Bounce sql server agent. If this does not
solve
> > it,
> > > > > bounce sql server.
> > > > > "Ray Price" <ray.price@gartner.com> wrote in message
> > > > > news:%23dff%237HVEHA.3944@tk2msftngp13.phx.gbl...
> > > > > > It says...
> > > > > >
> > > > > > Invalid object name 'tempdb.dbo.msreplication_agent_status'
> > > > > >
> > > > > > Ray
> > > > > >
> > > > > > "Hilary Cotter" <hilaryk@att.net> wrote in message
> > > > > > news:OoTpVGBVEHA.2508@TK2MSFTNGP12.phx.gbl...
> > > > > > > can you issue a sp_MSload_replication_status and see if this
> > helps?
> > > > > > >
> > > > > > > --
> > > > > > > Hilary Cotter
> > > > > > > Looking for a book on SQL Server replication?
> > > > > > > http://www.nwsu.com/0974973602.html
> > > > > > >
> > > > > > >
> > > > > > > "Ray Price" <ray.price@gartner.com> wrote in message
> > > > > > > news:uF%23AOF8UEHA.760@TK2MSFTNGP12.phx.gbl...
> > > > > > > > Strange thing has happened on one of our servers. The
> > > publications
> > > > > have
> > > > > > > > disappeared from under the replication monitor/publishers in
> > > > > Enterprise
> > > > > > > > Manager. We can still see them under
replication/publications
> > > > though.
> > > > > > > >
> > > > > > > > Any ideas what may cause this?
> > > > > > > >
> > > > > > > > Thanks
> > > > > > > >
> > > > > > > > Ray
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
- Next message: Dan: "Schema Changes After Publishing"
- Previous message: Oussama Albairat: "context in trigger"
- In reply to: Hilary Cotter: "Re: Publishers disappeared from under replication monitor"
- Next in thread: Hilary Cotter: "Re: Publishers disappeared from under replication monitor"
- Reply: Hilary Cotter: "Re: Publishers disappeared from under replication monitor"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
