"Arithmetic overflow error converting expression

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

SQL Server 2000 Forums

Import/Export (DTS) and Replication (2000)

"Arithmetic overflow error converting expression

Author

Topic

andypatterson
Starting Member

1 Post

Posted - 2002-01-21 : 18:34:34

I am having a transactional replication of the imm. updating subs type.( SQL 7.0 SP2). I ran the intial snapshot, that went ok, the log reader agent then complains of the following error text

"Arithmetic overflow error converting expression to data type int"

I ran a trace and found that each time i start the log reader agent, following SP is run, this SP is passed value 2041905750 along with other values. I think logread.exe could be passing this value. I have tried workaround discussed as in (Q260342), does not do any good.

sp_MSadd_logreader_history 2, 3, N'500 transaction(s) with 500 command(s) were delivered.', 0x000001f200000b630005, 344, 500, 500, 2041905750, 0x00, 1, 0x01

sp_MSadd_logreader_history 2, 3, N'Delivering replicated transactions', 0x, 344, 500, 500, 2041905750, 0x00, 1, 0x01

I was looking at the SP text sp_MSadd_logreader_history in distribution database and understand that the following calculation is being done and at this place avg_delivery_latency is also an int, so it is here that the error might be happening and reported to the repl_monitor.

if @latest_delivered_commands <> 0 -- Work around for Logreader passing in @delivery_latency on shutdown.
BEGIN
IF @delivery_latency <> 0
IF @last_delivery_latency <> 0
SELECT @avg_delivery_latency = (@delivery_latency + @last_delivery_latency)/2
ElSE
SELECT @avg_delivery_latency = @delivery_latency
ELSE
SELECT @avg_delivery_latency = 0
END
ELSE
BEGIN
SELECT @avg_delivery_latency = @last_delivery_latency

-- Ignore latency value if no commands
SELECT @delivery_latency = 0
END

Now there is a KB article (Q260342) describing some workaround to this, but i also executed the workaround for this, i have had no success. I did not get this type of error message earlier when the same DB participated in replication. If SP3 could solve this problem, why am i not getting errors on replication having servers at SP2. and SP3 is difficult to implement in our production environment.

SQL Pros please help throw some light on this one.

Thanks

Andy patterson

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources