March 26, 2008 at 12:34 pm
I've got canned alerts set up on both my Principal and Mirror servers to monitor matters. One of these alerts is to send out an e-mail should the transaction log file size exceed 90% of capacity. No issues with this until last night. I had to make some configuration changes on the mirror machine which necessitated a reboot. So, I paused mirroring, cycled the machine, made sure SQL Server was back up and running and then re-started mirroring. All appears to be hunky-dory except for the fact that I am now getting spammed with alerts that the transaction log on the mirror is 100% full.
There are no space issues on the t-log drive.
Snapshot of the mirror DB looks normal and up to date.
I'm running a checkdb to see if that shows anything. Since the DB is 2.4TB in size, though, even a PHYSICAL_ONLY takes a while.
Anyone have any clues?
March 26, 2008 at 3:38 pm
To update:
DBCC CHECKDB with PHYSICAL_ONLY returned no errors.
AN idle thought is that there is simply a mis-reading somewhere as this is a mirror DB, but I've had the mirror and the alert up and active for quite some time with no issues / errors.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply