Re: Replication Issues

Tech-Archive recommends: Fix windows errors by optimizing your registry

I see 3 transactions with 9 commands flow in this log. There is no error
reported. Does the distribution agent display an error? If so, what is the
error number?

--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.

This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.

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



"maxzsim" <u14644@uwe> wrote in message news:5fef40c9939d1@xxxxxx
Hi ,

The below acct does not have the problem (i.e changes not replicated
across
after i have reinitialized the snapsho)

any reason ? is it due to the acct at the destination db being changed
instead of at the source db ?
if so wouldn't the replication failed saying that the data between source
&
destination db are not in sync in the first place ?

tks & rdgs

maxzsim wrote:
Hi ,

This is with regards to an earlier posting :

(1) sp_browsereplcmds will show you the command in human-readable format
(2) The above command will indicate which table on the subscriber is
affected.
(3) The agent history will report any errors. You can also enable logging
to
a text file (http://support.microsoft.com/?id=312292).

Please also check that the distribution agent is ether running
continuously
or running on a schedule that is appropriate.

Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

==========================================================
I have logged the replication agent to a text file but

ques :
How do i actually see if there's any error to the replication. it seems
to
me that the replication is ok as it stated
there were 3 txns with 9 commands being delivered

below is the abstract of the log while changing some values for this acct
21102

[5/8/2006 4:05:31 PM]SQL1.distribution: {call sp_MSget_repl_commands(33,
?, 0,
7500000)}
[5/8/2006 4:05:31 PM]TLDDC1.scalaDB_TLD: {CALL sp_MSdel_GL530106 (?, ?, ?,
?,
?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)}
{CALL
sp_MSins_GL530106 (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?,
?, ?,
?, ?, ?, ?, ?, ?, ?)} {CALL sp_MSupd_GL530106 (?, ?, ?, ?, ?, ?, ?, ?, ?,
?, ?
, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?,?, ?, ?, ?, ?, ?, ?, ?,
?, ?,
?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)} {CALL
sp_MSdel_GL530106 (?
, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?,
?, ?
)} {CALL sp_MSins_GL530106 (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?,
?, ?,
?, ?, ?, ?, ?, ?, ?, ?, ?, ?)} {CALL sp_MSupd_GL530106 (?, ?, ?, ?, ?, ?,
?, ?
, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?,?, ?, ?, ?, ?,
?, ?,
?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)} {CALL
sp_MSdel_GL530106 (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?,
?, ?,
?, ?, ?, ?, ?, ?, ?)} {CALL sp_MSins_GL530106 (?, ?, ?, ?, ?, ?, ?, ?, ?,
?, ?
, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)} {CALL sp_MSupd_GL530106
(?,
?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?,
?,?
, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?,
?, ?
)}
sp_MSget_repl_commands timestamp value is: 0x0000042d000003ff000100000000
Parameterized values for above command(s): {{N'21102', N'ACCRUED
LEGAL/PROF
FEES', N'1', N'0', N'100000000', N'0', N'0', -4000.00000000, N'0', N'XXX',
N'ZZ', N'y', N' ', N' ', N' ', N' ', N' ', N' ', N' ', N' ', N' ', N' ',
N' ',
2, N' ', N'0', {6CB12E3F-AF28-4C26-B19B-221B62B21F78}}, {N'21102',
N'ACCRUED
LEGAL/PROF FEES', N'1', N'0', N'100000000', N'0', N'0', -4000.00000000,
N'0',
N'KKK', N'ZZ', N'y', N' ', N' ', N' ', N' ', N' ', N' ', N' ', N' ', N' ',
N'
', N' ', 2, N' ', N'0', {6CB12E3F-AF28-4C26-B19B-221B62B21F78}},
{N'21102',
N'ACCRUED LEGAL/PROF FEES', N'1', N'0', N'100000000', N'0', N'0', -4000.
00000000, N'0', N'KKK', N'ZZ', N'y', N' ', N' ', N' ', N' ', N' ', N' ',
N' ',
N' ', N' ', N' ', N' ', 2, N' ', N'0',
{6CB12E3F-AF28-4C26-B19B-221B62B21F78},
N'21102', N'ACCRUED LEGAL/PROF FEES', N'1', N'0', N'100000000', N'0',
N'0', -
4000.00000000, N'0', N'KKK', N'ZZ', N'y', N' ', N' ', N' ', N' ', N' ', N'
',
N' ', N' ', N' ', N' ', N' ', 2, N' ', N'0', {6AE7412E-2D28-4B61-B8D0-
067FB28134DC}}, {N'21102', N'ACCRUED LEGAL/PROF FEES', N'1', N'0',
N'100000000', N'0', N'0', -4000.00000000, N'0', N'KKK', N'ZZ', N'y', N' ',
N'
', N' ', N' ', N' ', N' ', N' ', N' ', N' ', N' ', N' ', 2, N' ', N'0',
{6AE7412E-2D28-4B61-B8D0-067FB28134DC}}, {N'21102', N'ACCRUED LEGAL/PROF
FEES', N'1', N'0', N'100000000', N'0', N'0', -4000.00000000, N'0',
N'XXXX',
N'ZZ', N'y', N' ', N' ', N' ', N' ', N' ', N' ', N' ', N' ', N' ', N' ',
N' ',
2, N' ', N'0', {6AE7412E-2D28-4B61-B8D0-067FB28134DC}}, {N'21102',
N'ACCRUED
LEGAL/PROF FEES', N'1', N'0', N'100000000', N'0', N'0', -4000.00000000,
N'0',
N'XXXX', N'ZZ', N'y', N' ', N' ', N' ', N' ', N' ', N' ', N' ', N' ', N'
',
N' ', N' ', 2, N' ', N'0', {6AE7412E-2D28-4B61-B8D0-067FB28134DC},
N'21102',
N'ACCRUED LEGAL/PROF FEES', N'1', N'0', N'100000000', N'0', N'0', -4000.
00000000, N'0', N'XXXX', N'ZZ', N'y', N' ', N' ', N' ', N' ', N' ', N' ',
N'
', N' ', N' ', N' ', N' ', 2, N' ', N'0', {8266B10B-D4C3-4A7F-B537-
DCCC754C20F1}}, {N'21102', N'ACCRUED LEGAL/PROF FEES', N'1', N'0',
N'100000000', N'0', N'0', -4000.00000000, N'0', N'XXXX', N'ZZ', N'y', N'
',
N' ', N' ', N' ', N' ', N' ', N' ', N' ', N' ', N' ', N' ', 2, N' ', N'0',
{8266B10B-D4C3-4A7F-B537-DCCC754C20F1}}, {N'21102', N'ACCRUED LEGAL/PROF
FEES', N'1', N'0', N'100000000', N'0', N'0', -4000.00000000, N'0',
N'XXXX',
N'ZZ', N'YYY', N' ', N' ', N' ', N' ', N' ', N' ', N' ', N' ', N' ', N' ',
N'
', 2, N' ', N'0', {8266B10B-D4C3-4A7F-B537-DCCC754C20F1}}, {N'21102',
N'ACCRUED LEGAL/PROF FEES', N'1', N'0', N'100000000', N'0', N'0', -4000.
00000000, N'0', N'XXXX', N'ZZ', N'YYY', N' ', N' ', N' ', N' ', N' ', N'
',
N' ', N' ', N' ', N' ', N' ', 2, N' ', N'0', {8266B10B-D4C3-4A7F-B537-
DCCC754C20F1}, N'21102', N'ACCRUED LEGAL/PROF FEES', N'1', N'0',
N'100000000',
N'0', N'0', -4000.00000000, N'0', N'XXXX', N'ZZ', N'YYY', N' ', N' ', N'
',
N' ', N' ', N' ', N' ', N' ', N' ', N' ', N' ', 2, N' ', N'0',
{995EF2F1-7F15-
41BE-9201-7412AB6A0987}}}
[5/8/2006 4:05:32 PM]TLDDC1.scalaDB_TLD: update
MSreplication_subscriptions
set transaction_timestamp = ?, "time" = ? where publisher = ? and
publisher_db = ? and publication = ? and subscription_type = 0
The commit timestamp value is: 0x0000042d000003ff000100000000
[5/8/2006 4:05:32 PM]TLDDC1.scalaDB_TLD: if exists (select * from
sysobjects
where name = 'syspublications') if exists( select * from syspublications
where repl_freq = 0) exec sp_replsetoriginator ?, ?
[5/8/2006 4:05:32 PM]TLDDC1.scalaDB_TLD: exec sp_MSsub_check_identity
@lower_bound_id = 0
3 transaction(s) with 9 command(s) were delivered.
[5/8/2006 4:05:32 PM]SQL1.distribution: {call
sp_MSadd_distribution_history
(33, 3, ?, ?, 3, 9, 5.01, 0x00, 1, ?, 0, 0x01, 0x01)}
[5/8/2006 4:05:42 PM]SQL1.distribution: {call
sp_MSget_subscription_guid(33)}
[5/8/2006 4:05:42 PM]SQL1.distribution: {call sp_MSget_repl_commands(33,
?, 0,
7500000)}
sp_MSget_repl_commands timestamp value is: 0x0000042d000003ff000100000000
Last transaction timestamp: 0x0000042d000003ff000100000000
Transaction seqno: 0x0000042d000004060001
Command Id: 1
Partial: 0
Type: 30
Command: <<parameterized command>>

I am using continuously updating and for certain acct the replication can
reflect the new changes

appreciate any advise

tks & rdgs

--
Message posted via http://www.sqlmonster.com


.

Relevant Pages

  • Re: MSRepl_Commands question
    ... make all database changes to the ... publisher and the subscriber and then reinitialize replication. ... We considered checking the status of the distribution agent but realized ... by checking their transaction number against this value. ...
    (microsoft.public.sqlserver.replication)
  • Re: transactional replication problem
    ... They will be reapplied the next time the distribution agent runs. ... Looking for a SQL Server replication book? ... > All transaction from killed process were rolled back... ...
    (microsoft.public.sqlserver.replication)
  • Re: Newbie question: "No replicated transactions are available"
    ... Hilary, you are right, it turns out I was using transaction ... when running the replication wizard. ... replication instead of snapshot for this particular data. ... >> snapshot pr day generated and 1/24 of the distribution agent cycles will ...
    (microsoft.public.sqlserver.replication)
  • Re: time out and replication
    ... This means that the distribution agent has issued a command on the ... subscriber and this command is still executing. ... Change querytimeout by right clicking on your distribution agent, ... To change the heartbeat interval Right click Replication Monitor, ...
    (microsoft.public.sqlserver.replication)
  • RE: Pull Subscription Continues to Run Indefinitely
    ... There are several optimization techniques for transactional replication one ... 10000] to the log reader agent where 10000 is the maximum number of commands ... replication pipe per transaction. ... > The SQL Query Analyzer completes the command successfully. ...
    (microsoft.public.sqlserver.replication)