January 21, 2008 at 5:04 pm
Hello!
I have been asked to help with replication related problem. Database with replication enabled has been restored on a different server. Developer issued:
backup log SBMSData with TRUNCATE_ONLY
and got a 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.
We tried:
EXEC sp_repldone @xactid = NULL, @xact_segno = NULL, @numtrans = 0, @time = 0, @reset = 1
but got an error: The database is not published. (which is true)
If I issue DBCC OPENTRAN in this database, I get:
Transaction information for database 'SBMSData'.
Replicated Transaction Information:
Oldest distributed LSN : (341120:377:1)
Oldest non-distributed LSN : (341116:174:1)
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
Copy we restored will be used for development purposes. I was thinking of rebuilding log on database in question. Is this the proper way of handling this problem?
We would like to be able to truncate log and don't need to support replication in development.
Database in question was acting as publisher in production.
Thanks,
Igor
January 22, 2008 at 1:56 am
Hi,
For the sake of tidying up your environment, can you configure the database as a publisher. You can then run sp_repldone...truncate and then disable the database as as publisher.
HTH
Regards
Graeme
January 22, 2008 at 11:51 am
Good idea! I don't think we will have an opportunity to test it as whole environment will be rebuild soon.
Thanks,
Igor
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply