Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

The process could not execute ''sp_replcmds'' on PRODUCTION Expand / Collapse
Author
Message
Posted Saturday, September 1, 2007 5:54 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, May 20, 2008 10:47 AM
Points: 3, Visits: 3

Hi Champs,

Thursday i run DDREINDEX on my Production Server, Next day i went to office i find out that Replication is not working, It Marked as RED Cross on Replication Monitor.

Production Server Transactional Replication to Subscriber Server (Reporting Server)

In the Log Reader Agent I seen the Message The process could not execute 'sp_replcmds' on 'servername'

Actually am new to this Replication, Now what can i do Please help me.

I Stop the Agent and Re-run but still the same error  message is coming

Please help me it will be very greatefull.

Thanks

Emmanuel

emmanuel_canagallas@hotmail.co.uk

 

Post #395732
Posted Sunday, September 2, 2007 4:58 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Yesterday @ 10:45 AM
Points: 1,402, Visits: 6,893
It could be timing out. You can change batchsize & timeout in the replication agent profiles.
Post #395750
Posted Sunday, September 2, 2007 12:07 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, May 20, 2008 10:47 AM
Points: 3, Visits: 3

Hi I Changed the timeout from 10 to 40, but still its giving same error message.

and my Log file is also filling before is like 2GB on (Thursday) now its increases to 18GB

I think all the Replication Transactions are stored in the Log file.

Every 15min Transaction Log Backup is running and Once a Full backup at mid night.

I really dont know what to do? Please can you help

Thanks..

 

Post #395760
Posted Sunday, September 2, 2007 12:19 PM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Yesterday @ 10:45 AM
Points: 1,402, Visits: 6,893
I would start with reducing the batch size.
It was needed at work to reduce it from 500 to 100 because our subscriber was slower in IO
Found the kb:
http://support.microsoft.com/kb/811030
Post #395761
Posted Sunday, September 2, 2007 3:41 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, May 20, 2008 10:47 AM
Points: 3, Visits: 3

Ok i changed the batch size to 100.

I run the Agents am wating for the Result.

mean time What about the Log file its reached 18GB what can i do with it.

Cheers..

 

Post #395763
Posted Monday, September 3, 2007 4:37 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Yesterday @ 10:45 AM
Points: 1,402, Visits: 6,893
You can perform a transaction log backup. It automatically truncates the inactive portion of the transaction log.
Post #395825
Posted Monday, January 19, 2009 4:42 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, January 19, 2009 4:37 AM
Points: 3, Visits: 50
I think we cannot truncate transaction logs until log reader agent moves the transactions to teh subscriber
Post #639186
Posted Monday, January 19, 2009 5:28 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Monday, November 10, 2014 2:21 AM
Points: 2,223, Visits: 3,652
Aditya (1/19/2009)
I think we cannot truncate transaction logs until log reader agent moves the transactions to teh subscriber


to the distribution database to be more specific.






Pradeep Singh
Post #639220
Posted Tuesday, July 14, 2009 3:22 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Wednesday, September 24, 2014 2:38 PM
Points: 255, Visits: 467
Reducing the batch size did not work for me on this issue, however, by reapplying the snapshot to the subscriber I was able to get the log reader to function without the error. I assume this is because the bulk of the records in the log on the publisher that were marked for replication were brought over with the snapshot. Regardless, wanted to share this info on this subject.
Post #753065
Posted Wednesday, July 29, 2009 5:58 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Tuesday, November 4, 2014 3:37 AM
Points: 1,220, Visits: 700
Yes applying a new snapshot is a last resort..

In your situation, you needed to let the logreader "catch up" as there were many transactions in the TLog. This may have meant stopping activity on your database...perhaps that would not have been viable.

Regards
Graeme



Post #761419
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse