Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Bug in "DBSS - Unavailable" on a Database Mirror? Or an actual outage? Expand / Collapse
Author
Message
Posted Wednesday, June 6, 2012 8:19 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, June 21, 2012 7:17 PM
Points: 9, Visits: 73
Is anyone else getting false-positives on the "DBSS - Unavailable" rule for mirrored databases?



Once every week or two I am getting a fatal alert of "Unavailable" for the "DBSS - Unavailable" rule on all of the mirrored databases for my server. It only lasts for a few minutes in Foglight then goes back to a normal status.



I have looked at all Database Monitoring logs for both the Mirror and Principle, all SQL server and Agent logs, all server event logs.. nothing. The entire history of all mirrored databases have no sign of availability issues according to the actual SQL server itself.



The only reference towards this Foglight Rule is:

https://support.quest.com/Search/SolutionDetail.aspx?ID=SOL76183



Going by the article, I have looked at the data stored in "DB Status" for the affected databases, which it states "Unavailable" for the times the alert has come up. However, I cannot locate anywhere on the actual SQL server where this error might have come from.



I don't particualrly want to go rushing towards false-positive fatal alerts stating my mirror is unavailable



Any thoughts on what else I could try? Has anyone experienced this issue?

Or is this just a blip?


Post #1312268
Posted Wednesday, June 6, 2012 8:19 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, June 21, 2012 7:17 PM
Points: 9, Visits: 73
It seems the last error for this in Foglight has now continued for 16 hours. Having looked at my actual database mirror on many occasions, I can 100% confirm the mirror is working perfectly...



- No SQL or server errors

- No Foglight Client errors

-100% mirroring sync with <1ms wait time

- the database Status is "Restoring" as per normal.



The Foglight client application itself is able to monitor all other rules successfully.



I am at a loss. Anyone have any ideas? Does anyone know exactly how the "db_status" data in Foglight is extracted from SQL server?
Post #1312269
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse