July 2, 2010 at 4:10 am
I am trying to truncate the transaction log file for one of my database. When i try to do so, it gives me the below error message:
Cannot shrink log files because all logical log files are in use.
The database log file size is around 65 GB.
It acts as a publisher for replication. The problem is that corressponding subscribers have been disabled. Also the free space of the drive holding the log file is in MB.
Can someone, please provide me help on this?
With Thanks.
July 2, 2010 at 4:38 am
singhsatnam84 (7/2/2010)
It acts as a publisher for replication. The problem is that corressponding subscribers have been disabled. Also the free space of the drive holding the log file is in MB.
Although the subscribers are disabled, it is still enabled and configured as a distributor.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This thing is addressing problems that dont exist. Its solution-ism at its worst. We are dumbing down machines that are inherently superior. - Gilfoyle
July 2, 2010 at 5:11 am
singhsatnam84 (7/2/2010)
It acts as a publisher for replication. The problem is that corressponding subscribers have been disabled.
The fact that the subscribers have been disabled does not change that the database is configured as a publisher and, a such, it's log records must be retained until picked up by the log reader.
I assume that someone disabled the log reader as well.
If the replication is not needed any longer, you need to drop the publications off of the publisher. Until you do that it's still configured for replication and log records cannot be discarded until they are picked up by the log reader.
If the replication is still needed, ensure that the log reader is running. That will extract records from the publisher's log and write them into the distributor, and allow for those log records to be marked as reusable
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply