Re: sp_replcmds
From: Hilary Cotter (hilary.cotter_at_gmail.com)
Date: 08/31/04
- Next message: lancemc5: "Re: Updating Subsciber Replication Error"
- Previous message: Hilary Cotter: "Re: What is faster? 1 replication 2 tables or 2 replication with 1 table?"
- In reply to: Andre: "Re: sp_replcmds"
- Next in thread: Andre: "Re: sp_replcmds"
- Reply: Andre: "Re: sp_replcmds"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 30 Aug 2004 22:43:39 -0400
run a dbcc opentran
see if there is an open transaction you can identify as not belonging to an
active process and kill it. It is possible that there is an open transaction
which is holding your transaction log open.
I'd call PSS to see if they can't help you through this one.
You can also issue an sp_repldone to mark your tlog as replicated and then
truncate your transaction log. Look up the syntax for this command in BOL.
The problem is that your publisher and subscriber(s) will be out of sync.
You will then need to reinitalize and regenerate and redistribute your
snapshots to all subscribers.
-- Hilary Cotter Looking for a book on SQL Server replication? http://www.nwsu.com/0974973602.html "Andre" <no@spam.com> wrote in message news:%23DpnSYvjEHA.3852@tk2msftngp13.phx.gbl... > Hillary, > > I bounced my publisher and am having the same exact issue with the Log > Reader retrying. Any other suggestions? I really don't want to blow away > my subscriptions but I'm afraid I might have to do that because my tran log > is full. I've expanded it a little but 60 GB is pretty much my max... > > Thanks again, Andre > > > "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message > news:%23ENhbAqjEHA.3664@TK2MSFTNGP11.phx.gbl... > > This is caused by a resource problem on your Publisher. Unfortunately the > > way to stop it is to try the following sequence. > > > > Stop SQL Server agent, restart it and see if this clears the error. > > Stop SQL Server, restart it and see if this clears the error. > > Bounce your OS and see if this clears the error. > > > > -- > > Hilary Cotter > > Looking for a book on SQL Server replication? > > http://www.nwsu.com/0974973602.html > > > > > > "Andre" <no@spam.com> wrote in message > > news:OwJt$0pjEHA.1040@TK2MSFTNGP10.phx.gbl... > > > Thanks for both of the replies. I used the link Hillary provided and > did > > > see the issue that Paul mentioned - 'Another log reader is replicating > the > > > database.'. > > > So I ran sp_replflush and it seemed like the Log Reader was going to > work. > > > But this time it timed out, as you can see below. Now it seems to be > > stuck > > > in a loop where it's "Initializing". I'm not sure why it can't talk to > > the > > > publication server because I'm having no problems at all. I pulled up > QA > > on > > > REP01 and was able to logon and run queries on SQL01 just fine. > > > > > > Any suggestions? > > > > > > Thanks, Andre > > > > > > Server: > > > DBMS: Microsoft SQL Server > > > Version: 08.00.0818 > > > user name: dbo > > > API conformance: 2 > > > SQL conformance: 1 > > > transaction capable: 2 > > > read only: N > > > identifier quote char: " > > > non_nullable_columns: 1 > > > owner usage: 31 > > > max table name len: 128 > > > max column name len: 128 > > > need long data len: Y > > > max columns in table: 1024 > > > max columns in index: 16 > > > max char literal len: 524288 > > > max statement len: 524288 > > > max row size: 524288 > > > > > > [8/30/2004 7:06:42 AM]SQL01.LIVE: select @@SERVERNAME > > > [8/30/2004 7:06:42 AM]SQL01.LIVE: sp_MSgetversion > > > Status: 4096, code: 20024, text: 'Initializing'. > > > The agent is running. Use Replication Monitor to view the details of > this > > > agent session. > > > Publisher: {call sp_repldone ( 0x00051a7500003a050004, > > > 0x00051a7500003a050004, 0, 0)} > > > Status: 2, code: 0, text: 'The process could not execute > > > 'sp_repldone/sp_replcounters' on 'SQL01'.'. > > > The process could not execute 'sp_repldone/sp_replcounters' on 'SQL01'. > > > Status: 2, code: 18752, text: 'Another log reader is replicating the > > > database.'. > > > Status: 0, code: 22017, text: 'The process could not set the last > > > distributed transaction.'. > > > Disconnecting from Publisher 'SQL01' > > > The agent failed with a 'Retry' status. Try to run the agent at a later > > > time. > > > Microsoft SQL Server Log Reader Agent 8.00.760 > > > Copyright (c) 2000 Microsoft Corporation > > > Microsoft SQL Server Replication Agent: SQL01-LIVE-2 > > > > > > Connecting to Publisher 'SQL01.LIVE' > > > > > > [8/30/2004 7:07:51 AM]SQL01.LIVE: select @@SERVERNAME > > > [8/30/2004 7:07:51 AM]SQL01.LIVE: sp_MSgetversion > > > Status: 4096, code: 20024, text: 'Initializing'. > > > The agent is running. Use Replication Monitor to view the details of > this > > > agent session. > > > Publisher: {call sp_repldone ( 0x00051a7500003a050004, > > > 0x00051a7500003a050004, 0, 0)} > > > Publisher: {call sp_replcmds (500, 0)} > > > Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds' > on > > > 'SQL01'.'. > > > The process could not execute 'sp_replcmds' on 'SQL01'. > > > Status: 2, code: 0, text: 'Timeout expired'. > > > Disconnecting from Publisher 'SQL01' > > > The agent failed with a 'Retry' status. Try to run the agent at a later > > > time. > > > > > > [8/30/2004 7:14:00 AM]SQL01.LIVE: select @@SERVERNAME > > > [8/30/2004 7:14:00 AM]SQL01.LIVE: sp_MSgetversion > > > Status: 4096, code: 20024, text: 'Initializing'. > > > The agent is running. Use Replication Monitor to view the details of > this > > > agent session. > > > Publisher: {call sp_repldone ( 0x00051a7500003a050004, > > > 0x00051a7500003a050004, 0, 0)} > > > Publisher: {call sp_replcmds (500, 0)} > > > > > > > > > > > >
- Next message: lancemc5: "Re: Updating Subsciber Replication Error"
- Previous message: Hilary Cotter: "Re: What is faster? 1 replication 2 tables or 2 replication with 1 table?"
- In reply to: Andre: "Re: sp_replcmds"
- Next in thread: Andre: "Re: sp_replcmds"
- Reply: Andre: "Re: sp_replcmds"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
Loading
