MOM - Database Health

Question

Post reply

MOM - Database Health

Vera Maras

SSC Enthusiast

Points: 119
More actions
January 26, 2006 at 5:12 am

#167914

Hi Everyone.
I am DBA of SQL Server 2000.
I do have a strange situation which I don't know how to cope with.
There is a database on our SQL Server 2000 that, it seems to me, works fine.
Users do not complain.
We have Microsoft Operations Manager in the firm and I am occasionally sent a very strange message regarding the state of that particular database.
Here is the message:

I am not sure what's going on with the database. The MOM administrator is also confused.
I hope it's just a fault MOM alert but can't stay calm.
Thank you for your help/suggestions.

Viewing 15 posts - 1 through 14 (of 14 total)

You must be logged in to reply to this topic. Login to reply

jordanac Hall of Fame Points: 3653 More actions · Answer 1

jordanac

Hall of Fame

Points: 3653

January 26, 2006 at 5:56 am

#617119

Vera, I cannot see the error message.....

Andy.

Vera Maras SSC Enthusiast Points: 119 More actions · Answer 2

I am so sorry.

Here is the message:

Operations Manager Critical Error Alert on ServerNAme

Severity: Critical Error

Status: New

Source: SQL Server 2000 Database

Health:MSSQLSERVERatabase( DatabaseName)

Name: SQL Server 2000 Database Health

Description: The database " DatabaseName " in the instance "MSSQLSERVER" is in a critical state. The state is: Unable to identify state after 3 retries.

Domain: DomainName

Agent: SQLServerAgentName

Time: 1/26/2006 08:20:07

Owner:

Vera Maras SSC Enthusiast Points: 119 More actions · Answer 3

I am so sorry.

Here is the message:

Operations Manager Critical Error Alert on ServerNAme

Severity: Critical Error

Status: New

Source: SQL Server 2000 Database

Health:MSSQLSERVERatabase( DatabaseName)

Name: SQL Server 2000 Database Health

Description: The database " DatabaseName " in the instance "MSSQLSERVER" is in a critical state. The state is: Unable to identify state after 3 retries.

Domain: DomainName

Agent: SQLServerAgentName

Time: 1/26/2006 08:20:07

Owner:

Vera Maras SSC Enthusiast Points: 119 More actions · Answer 4

I am so sorry.

Here is the message:

Operations Manager Critical Error Alert on ServerNAme

Severity: Critical Error

Status: New

Source: SQL Server 2000 Database

Health:MSSQLSERVERatabase( DatabaseName)

Name: SQL Server 2000 Database Health

Description: The database " DatabaseName " in the instance "MSSQLSERVER" is in a critical state. The state is: Unable to identify state after 3 retries.

Domain: DomainName

Agent: SQLServerAgentName

Time: 1/26/2006 08:20:07

Owner:

Vera Maras SSC Enthusiast Points: 119 More actions · Answer 5

I am so sorry.

Here is the message:

Operations Manager Critical Error Alert on ServerNAme

Severity: Critical Error

Status: New

Source: SQL Server 2000 Database

Health:MSSQLSERVERatabase( DatabaseName)

Name: SQL Server 2000 Database Health

Description: The database " DatabaseName " in the instance "MSSQLSERVER" is in a critical state. The state is: Unable to identify state after 3 retries.

Domain: DomainName

Agent: SQLServerAgentName

Time: 1/26/2006 08:20:07

Owner:

Vera Maras SSC Enthusiast Points: 119 More actions · Answer 6

Oops!

Sorry for this. Something went wrong with posting so it's has been posted for 4 times.

Hope you are still willing to help me.

Vera

jordanac Hall of Fame Points: 3653 More actions · Answer 7

I do not know MOM. But in the mean time,untill someone who knows MOM replies, did you check the SQL Server logs for any errors on the database? Do your disks have enough space for the mdf & ldf's? If not its probable that its a MOM problem.

Andy.

Vera Maras SSC Enthusiast Points: 119 More actions · Answer 8

There is enough disk space, log is ok, and everything looks fine.

But MOM still reports error.

Vera

Phil.Nicholas SSCrazy Points: 2147 More actions · Answer 9

Error reads like MOM can't attach to server/db to ascertain correct status

Phil Nicholas

Rudyx - the Doctor SSC-Forever Points: 43695 More actions · Answer 10

Talk to your MOM Admin. There is a link on the MOM console for every error generated to a MS article. That's a good place to start. If that does not help, have the MOM admin check the MOM service and it's account on the SQL Server. Then check if Windows, SQL Server and MOM all patched and up to date ? Are the MOM 'management packs' up to date ? That should do for starters ... if things are still flaky, then I'd say call MS PSS.

RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."

aureolin Hall of Fame Points: 3520 More actions · Answer 11

One more thing to look at: Check your network. If your network becomes saturated (i.e. too busy) during the moment when MOM is trying to attach to the SQL Server you would see this sort of error.

This could be quite difficult to determine since the error would be completely dependant on external factors; both MOM and SQL Server would show no (internal) problems.

Buck-262603 Grasshopper Points: 15 More actions · Answer 12

I'm having the same problem. Did you ever find a resolution?

Buck-262603 Grasshopper Points: 15 More actions · Answer 13

This link provides a little insight to this problem.

http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.mom.managementpack.sql&tid=4558d349-bdfe-4be7-bfd8-21d1e55d7757&cat=en_US_4ca59556-9b3d-4558-ae24-800874bcaeeb&lang=en&cr=US&sloc=&p=1

David Sorauer SSCrazy Points: 2874 More actions · Answer 14

I'm finding this happening on one of our databases that is set to auto close. I'm guessing the 'ping' that MOM does doesn't actually wake up the database...and MOM thinks it's unavailable.