SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Bug in "DBSS - Unavailable" on a Database Mirror? Or an actual outage?


Bug in "DBSS - Unavailable" on a Database Mirror? Or an actual outage?

Author
Message
Tiazi
Tiazi
SSC Journeyman
SSC Journeyman (83 reputation)SSC Journeyman (83 reputation)SSC Journeyman (83 reputation)SSC Journeyman (83 reputation)SSC Journeyman (83 reputation)SSC Journeyman (83 reputation)SSC Journeyman (83 reputation)SSC Journeyman (83 reputation)

Group: General Forum Members
Points: 83 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?
Tiazi
Tiazi
SSC Journeyman
SSC Journeyman (83 reputation)SSC Journeyman (83 reputation)SSC Journeyman (83 reputation)SSC Journeyman (83 reputation)SSC Journeyman (83 reputation)SSC Journeyman (83 reputation)SSC Journeyman (83 reputation)SSC Journeyman (83 reputation)

Group: General Forum Members
Points: 83 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?
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search