June 29, 2010 at 1:09 am
Hi
I am facing a problem with transaction log size, currently db log file reached 15 GB, once I try to truncate log file or dump it returns back that there is still pending transactions or log reader has stopped. Upon running dbcc OpenTran I have noticed that both values LSN_NON_Distr. and LSN_Distr are not 0 which clears the point of pending transactions. At this point am not able to drop or rollback these transaction knowing that I can't rebuild replication scenario of distributor and publisher and use repldone or reactivate logReader agent since server crashed before and it seems that some of the files get damaged at that point.
Does any one have a suggestion regarding this issue and how to force the rollback of these pending transaction if replication can't be established again ??
Nadia
June 29, 2010 at 1:29 am
Is the log reader running? If not, start it.
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
June 29, 2010 at 1:37 am
over enterprise manager it is not appearing at all under Replication Group monitor and if I tried to run it from main path C:\Program Files \......\tools a cmd window pops up with a set of statements that ends with click Ctlr + C to close... So I assume it is not working.
June 29, 2010 at 1:45 am
You can't run the log reader manually. Check the SQL jobs, check replication monitor.
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
June 29, 2010 at 1:56 am
After the server crashed I wasn't not able to view the Replication monitor anymore ,even the jobs related to replication (distributor ,publisher, log reader and snapshots) were all removed.
June 29, 2010 at 2:32 am
You didn't mention there had been a database crash. It would have been helpful to know that.
Publish the database, then remove the publication. That should remove all traces of replication and you can reconfigure the replication from scratch if needed.
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
June 29, 2010 at 2:36 am
I have mentioned before that we faced before a server crash and a DB crash, upon this crash SQL server wasn't able to work properly, and at this level I lost the ability to configure or create any publication for many reasons the main one is that SQL server Agent is not able to work under administrator authentication account anymore and it is only running over Local account.. It is a huge mess
June 29, 2010 at 2:41 am
Sorry Server crash NOT DB crash
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply