Merge Replication database can not truncate log -- sql server replication

ponnu
2/21/2006 4:39:27 AM

Paul,
Nice to hear from you.

Sorry I have 1 snapshot replication and 6 merge replication on publication
on the database. I do not have any transaction replication.

Please let me know

regards
Ponnu

[quoted text, click to view]

ponnu
2/21/2006 6:56:30 AM

I never created Transactional replication on the this server.
It is looks lie very strange problem.

But Running the sp_repldone will cause any problem i mean need to
republished ?

EXEC sp_repldone @xactid = NULL, @xact_segno = NULL, @numtrans = 0, @time
= 0, @reset = 1

Caution This procedure can be used in emergency situations to allow
truncation of the transaction log when transactions pending replication are
present. Using this procedure prevents MicrosoftÂ® SQL Serverâ„¢ 2000 from
replicating the database until the database is unpublished and republished.

Thanks
Ponnu

[quoted text, click to view]

ponnu
2/21/2006 8:20:34 AM

Thanks Paul,
I have open the ticket with MS. i have checked with DBCC OpenTran, It looks
like some old transaction is there.

dbcc opentran
Transaction information for database 'ShipSure'.

Replicated Transaction Information:
Oldest distributed LSN : (0:0:0)
Oldest non-distributed LSN : (178321:74147:1)

Regards
Ponnu

[quoted text, click to view]

Paul Ibison
2/21/2006 3:32:19 PM

Ponnu,
AFAIK this warning message relates exclusively to transactional replication.
If you are at all concerned, then you could open up a support case.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages about sql server replication

sql server replication : Merge Replication database can not truncate log