Log Reader Error
in [Replication]
|
Prev: Could not load file or assembly 'Microsoft.SqlServer.BatchParser'
Next: The job step improperly defined error
From: Ken Powers on 12 Jan 2007 09:10 My LogReader Agent is failing, with the following errors: 1) The process could not execute 'sp_replcmds' on 'YKCLNSE'. 2) Execution of filter stored procedure 1364915934 failed. 3) Logreader failed to construct replicated command from LSN {00035e6f:00002a45:0004}. I saw a post from Adam Sewell on this same problem, and one of Hilary Cotter's first questions was whether he was using filtering. I am NOT using filtering on any of my Publications. Here are the Profiles for all three Agents: Distribution Agent BcpBatchSize: 2,147,473,647 CommitBatchSize: 100 CommitBatchThreshold: 1,000 HistoryVerboseLevel: 1 KeepAliveMessageInterval: 300 LoginTimeout: 3,600 MaxBcpThreads: 4 MaxDeliveredTransactions: 0 PollingInterval: 5 QueryTimeout: 3,600 SkipErrors: TransactionsPerHistory: 100 Log Reader Agent HistoryVerboseLevel: 1 LoginTimeout: 3,600 LogScanThreshold: 500,000 PollingInterval: 5 QueryTimeout: 3,600 ReadBatchSize: 500 Snapshot Agent BcpBatchSize: 100,000 HistoryVerboseLevel: 2 LoginTimeout: 3,600 QueryTimeout: 3,600 The first occurrence of this error occurred during the execution of a large data load into the Publisher database. Any idea where and how I should begin troubleshooting this error?
From: Hilary Cotter on 12 Jan 2007 09:39 I ran into a problem like this before. We had to trace it with profiler to figure out what the offending command was and then to rewrite it. Can you repro this? -- Hilary Cotter Looking for a SQL Server replication book? http://www.nwsu.com/0974973602.html Looking for a FAQ on Indexing Services/SQL FTS http://www.indexserverfaq.com "Ken Powers" <KenPowers(a)discussions.microsoft.com> wrote in message news:30FB9687-6F01-4253-9B17-A09DD8198904(a)microsoft.com... > My LogReader Agent is failing, with the following errors: > > 1) The process could not execute 'sp_replcmds' on 'YKCLNSE'. > 2) Execution of filter stored procedure 1364915934 failed. > 3) Logreader failed to construct replicated command from LSN > {00035e6f:00002a45:0004}. > > I saw a post from Adam Sewell on this same problem, and one of Hilary > Cotter's first questions was whether he was using filtering. I am NOT > using > filtering on any of my Publications. > > Here are the Profiles for all three Agents: > > Distribution Agent > BcpBatchSize: 2,147,473,647 > CommitBatchSize: 100 > CommitBatchThreshold: 1,000 > HistoryVerboseLevel: 1 > KeepAliveMessageInterval: 300 > LoginTimeout: 3,600 > MaxBcpThreads: 4 > MaxDeliveredTransactions: 0 > PollingInterval: 5 > QueryTimeout: 3,600 > SkipErrors: > TransactionsPerHistory: 100 > > Log Reader Agent > HistoryVerboseLevel: 1 > LoginTimeout: 3,600 > LogScanThreshold: 500,000 > PollingInterval: 5 > QueryTimeout: 3,600 > ReadBatchSize: 500 > > Snapshot Agent > BcpBatchSize: 100,000 > HistoryVerboseLevel: 2 > LoginTimeout: 3,600 > QueryTimeout: 3,600 > > The first occurrence of this error occurred during the execution of a > large > data load into the Publisher database. > > Any idea where and how I should begin troubleshooting this error?
From: Ken Powers on 12 Jan 2007 09:51 I'm going to have to eat some of my words on this one. It turns out another DBA DID add a filter to one of the publications. We added a new Publication recently, and I assumed it had been set the same as all the other one. How should I set up my Profiler trace? "Hilary Cotter" wrote: > I ran into a problem like this before. We had to trace it with profiler to > figure out what the offending command was and then to rewrite it. > > Can you repro this? > -- > Hilary Cotter > > Looking for a SQL Server replication book? > http://www.nwsu.com/0974973602.html > > Looking for a FAQ on Indexing Services/SQL FTS > http://www.indexserverfaq.com > > > > "Ken Powers" <KenPowers(a)discussions.microsoft.com> wrote in message > news:30FB9687-6F01-4253-9B17-A09DD8198904(a)microsoft.com... > > My LogReader Agent is failing, with the following errors: > > > > 1) The process could not execute 'sp_replcmds' on 'YKCLNSE'. > > 2) Execution of filter stored procedure 1364915934 failed. > > 3) Logreader failed to construct replicated command from LSN > > {00035e6f:00002a45:0004}. > > > > I saw a post from Adam Sewell on this same problem, and one of Hilary > > Cotter's first questions was whether he was using filtering. I am NOT > > using > > filtering on any of my Publications. > > > > Here are the Profiles for all three Agents: > > > > Distribution Agent > > BcpBatchSize: 2,147,473,647 > > CommitBatchSize: 100 > > CommitBatchThreshold: 1,000 > > HistoryVerboseLevel: 1 > > KeepAliveMessageInterval: 300 > > LoginTimeout: 3,600 > > MaxBcpThreads: 4 > > MaxDeliveredTransactions: 0 > > PollingInterval: 5 > > QueryTimeout: 3,600 > > SkipErrors: > > TransactionsPerHistory: 100 > > > > Log Reader Agent > > HistoryVerboseLevel: 1 > > LoginTimeout: 3,600 > > LogScanThreshold: 500,000 > > PollingInterval: 5 > > QueryTimeout: 3,600 > > ReadBatchSize: 500 > > > > Snapshot Agent > > BcpBatchSize: 100,000 > > HistoryVerboseLevel: 2 > > LoginTimeout: 3,600 > > QueryTimeout: 3,600 > > > > The first occurrence of this error occurred during the execution of a > > large > > data load into the Publisher database. > > > > Any idea where and how I should begin troubleshooting this error? > > >
From: Hilary Cotter on 14 Jan 2007 07:10
The default profiler setting will work ok. Run it on the publisher and then watch to see which statements caused the problem. Ideally you will run this is a test environment and be able to use profiler replay to run the statements one by one to figure out which one is the one which breaks the log reader. -- Hilary Cotter Looking for a SQL Server replication book? http://www.nwsu.com/0974973602.html Looking for a FAQ on Indexing Services/SQL FTS http://www.indexserverfaq.com "Ken Powers" <KenPowers(a)discussions.microsoft.com> wrote in message news:CED47583-AEDD-415A-825C-BB8C0C9E9EFE(a)microsoft.com... > I'm going to have to eat some of my words on this one. It turns out > another > DBA DID add a filter to one of the publications. We added a new > Publication > recently, and I assumed it had been set the same as all the other one. > > How should I set up my Profiler trace? > > "Hilary Cotter" wrote: > >> I ran into a problem like this before. We had to trace it with profiler >> to >> figure out what the offending command was and then to rewrite it. >> >> Can you repro this? >> -- >> Hilary Cotter >> >> Looking for a SQL Server replication book? >> http://www.nwsu.com/0974973602.html >> >> Looking for a FAQ on Indexing Services/SQL FTS >> http://www.indexserverfaq.com >> >> >> >> "Ken Powers" <KenPowers(a)discussions.microsoft.com> wrote in message >> news:30FB9687-6F01-4253-9B17-A09DD8198904(a)microsoft.com... >> > My LogReader Agent is failing, with the following errors: >> > >> > 1) The process could not execute 'sp_replcmds' on 'YKCLNSE'. >> > 2) Execution of filter stored procedure 1364915934 failed. >> > 3) Logreader failed to construct replicated command from LSN >> > {00035e6f:00002a45:0004}. >> > >> > I saw a post from Adam Sewell on this same problem, and one of Hilary >> > Cotter's first questions was whether he was using filtering. I am NOT >> > using >> > filtering on any of my Publications. >> > >> > Here are the Profiles for all three Agents: >> > >> > Distribution Agent >> > BcpBatchSize: 2,147,473,647 >> > CommitBatchSize: 100 >> > CommitBatchThreshold: 1,000 >> > HistoryVerboseLevel: 1 >> > KeepAliveMessageInterval: 300 >> > LoginTimeout: 3,600 >> > MaxBcpThreads: 4 >> > MaxDeliveredTransactions: 0 >> > PollingInterval: 5 >> > QueryTimeout: 3,600 >> > SkipErrors: >> > TransactionsPerHistory: 100 >> > >> > Log Reader Agent >> > HistoryVerboseLevel: 1 >> > LoginTimeout: 3,600 >> > LogScanThreshold: 500,000 >> > PollingInterval: 5 >> > QueryTimeout: 3,600 >> > ReadBatchSize: 500 >> > >> > Snapshot Agent >> > BcpBatchSize: 100,000 >> > HistoryVerboseLevel: 2 >> > LoginTimeout: 3,600 >> > QueryTimeout: 3,600 >> > >> > The first occurrence of this error occurred during the execution of a >> > large >> > data load into the Publisher database. >> > >> > Any idea where and how I should begin troubleshooting this error? >> >> >> |