Merge Replication database can not truncate log

In my SQL Server 2000 Standard Edition.
I am trying to truncate the log for the database but i am getting the below
message.
The log was not truncated because records at the beginning of the log are
pending replication. Ensure the Log Reader Agent is running or use
sp_repldone to mark transactions as distributed.
Ponnu
This message relates to transactional replication rather than merge. Please
run your log-reader agent which will mark the log as read then it can be
truncated.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||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
"Paul Ibison" wrote:

> This message relates to transactional replication rather than merge. Please
> run your log-reader agent which will mark the log as read then it can be
> truncated.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||Presumably you once had a tranasactional replication setup and have removed
it without the log reader havong completed. In this case running sp_repldone
should suffice.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||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
"Paul Ibison" wrote:

> Presumably you once had a tranasactional replication setup and have removed
> it without the log reader havong completed. In this case running sp_repldone
> should suffice.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
>
|||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)
|||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
"Paul Ibison" wrote:

> 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)
>
>
>
>