Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Transaction logs growing abnormally

Hi all,

We upgraded our primary and additional polling engines yesterday to version 10.3 and until yesterday I was not having any issues with the transaction logs. However, today in the morning I noticed that the transaction log file was growing abnormally and within a few hours it reached a size of 100GB! I tried to shrink the 'Log' file but it didnt help. I also ran a full backup of the DB assuming that it would truncate the transaction logs. However, nothing helped and then I stopped the SQL server service and started it again after a minute.

SQL server management studio showed me the status of the NetPerfMon DB to be in recovery for a couple of minutes, and when it came back online, I tried to shrink the file again and it worked this time! Now, the size of transaction log file is about 200 MB only. Please note that I have the recovery mode set to 'Simple' since beginning.

I have also noticed that the Orion Database Manager is giving wrong information regarding size of the transaction logs. It was reporting that the NetPerfMon DB was having a size of 213 KB, while in actuality the disk size of this file was 218 MB. It looks like a bug whereby they have divided the actual file size by an 1024.

The system is stable now and the transaction logs are not going crazy. I have opened a ticket with Solarwinds Support as well but I would appreciate any advice on how to avoid this issue from recurring and also shed some light on what could have caused this issue.

Thanks.

Find more posts tagged with

Accepted answers

All comments

michal.hrncirik

It seems this case needs and investigation and support should be able to help you with that. We would appreciate if you can share the outcome of this on Thwack when it will be resolved.

danielleh

Yes, please post your ticket # and keep us updated with your progress.

Thanks!

azakir

Hi all,

It turned out that the DB maintenance was the process causing this havoc on the DB server. I found it out after I checked the logs for DB maintenance and saw that the maintenance activity was stuck at a point. I stopped the process on the polling engine server for DB maintenance after which the transaction log size stopped growing and I was able to shrink the transaction logs to a few hundred MBs.

I told the Solarwinds support about the same and they advised me to run a query on the DB server after which I ran the DB maintenance again and it worked fine this time around.

For the second issue regarding the DB Manager showing incorrect size of the transaction logs, Solarwinds support has logged it as a bug, so you guys better check the transaction log size yourself on the DB server rather than relying on DB manager which is giving incorrect information.