Hello, I have a alert coming periodically in the SCOM console: Database SybariEnterpriseManager in SQL Server instance MSSQLSERVER on computer voforefrontcs1.ad.medctr.ucla.edu is offline/recovery pending/suspect/emergency from the Health Explorer I have: Date and Time: 4/2/2010 8:27:10 AM Property Name Property Value master-State ONLINE tempdb-State ONLINE model-State ONLINE msdb-State ONLINE SybariEnterpriseManager-State SUSPECT ReportServer-State ONLINE ReportServerTempDB-State ONLINE OnePoint-State ONLINE SystemCenterReporting-State ONLINE SybariEnterpriseManagerReports-State ONLINE or 4/2/2010 6:27:10 AMProperty NameProperty Valuemaster-StateONLINEtempdb-StateONLINEmodel-StateONLINEmsdb-StateONLINESybariEnterpriseManager-StateONLINEReportServer-StateONLINEReportServerTempDB-StateONLINEOnePoint-StateONLINESystemCenterReporting-StateONLINESybariEnterpriseManagerReports-StateRECOVERING If I check the SQL log I could not find any trace iof these evenst where should I look? Thanks,Dom System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 Support

you should be able to see this in the sql enterprise manager (or whatever it's called nowadays :))Rob Korving http://jama00.wordpress.com/

Hi Rob, I was expecting too to see something under SQL Server Management Studio (it is SQL Server 2005) but nothing... Database Engine > Management > SQL Server Logs > Current > Log Viewer Nothing as SUSPECT / RECOVERY since the 3/24/2010 so why SCOM is reporting this alert? Thanks,DomSystem Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 Support

You should check the SQL Server Management Studio and check your Databases. Under Databases all the databases installed on the SQL Instance should show. And according to your error one of them should have one of the conditions offline/recovery pending/suspect/emergenct Behind it.....

Hello, I have checked and the SQL Server management Studio is permanetly opened for the last 24 hours and nothing like this...The error is coming time to time at least 2-3 tiomes aday so far!!! Database Engine > Management > SQL Server Logs > Current > Log Viewer is also opened with one operators watching only it... The SQL log does not show any error on the database either... All databases are On-Line. Iam connected to the Main instance hopefully it is correct... Strange... Thanks,Dom System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 Support

Hmmm it looks like at the moment SCOM logs the alert the database is having an issue stated as supect and after the alert is raised the database is recovering as shown in your example. This would mean the database is having an issue but recovers itself..... This would explain why the alert pops up a couple of times a day. By looking at the databases it is Forefront installed? Maybe at the forefront forum they know more on these kind of issues I am not familiar enough with both Forefrotn or SQL to give you an clear anwser why this happens.

You are correct it seems to be recovering by itself as each hour SCOM seems to get a state change on databases... I will chek the Forefront Web Site But does the SQL logs should not reflect the state change also??? How SCOM is it able to detect the issue? Thanks Dom System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 Support

As I am having more and more alert Database <<database name>> in SQL Server instance MSSQLSERVER on computer <<server name>> is offline/recovery pending/suspect/emergency I'm becoming really concerned about these issue.... Messages are coming as 2-3 times per databases each day now.... Could it be connectivity issue? (Network overloaded)(CPU Overloaded) anything else? Thanks, DomSystem Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 Support

I had the same issue. Alerts would come in at during the off-hours, saying the database was offline/recovery pending/suspect/emergency. An hour later, it would come back saying that the issue was now closed. An hour after that it was open again, but another hour later it was closed. I checked the logs and noticed they were constantly saying "Starting up database 'AdventureWorks'". <del>Googling</del> Binging that, I learned to check on the AutoClose property for the database, and discovered that it was indeed enabled. I won't know till tomorrow if it worked, but the dots seem to connect. Wanted to leave this out here now, as I won't remember to post it tomorrow once I know for sure if it worked. I still wonder, though, why the connection that SCOM makes to check on the database doesn't "wake" the database up enough to respond that it's fully functional BUT the next check always does? I guess it's possible that the db is being accessed right before the follow-up check, but that's too strange a coincidence to explain how the follow-up check passes EVERY TIME (at least in my case).

Dom, I was going to suggest looking in the SQL error logs but the previous response beat me to it. You will find multiple error logs. Each time the SQL Server is restarted it copies the error logs to a -1 and starts a new one. So the oldest one has the highest number in the sequence. Any time you're not seeing something in the Management Studio console, check the error logs. Some of this information will also be captured in the Windows logs, but the SQL log is more complete.

Try the following SQL Query from SQL Server Management Studio run again Master Select Name, isnull (databasepropertyex(Name,'Status'),'N/A') from sys.databases This is essentially what the propertybag is returning for the status of the monitor. Is the SybariEnterpriseManager db listed as recovering according to SQL?

Try the following SQL Query from SQL Server Management Studio run again Master Select Name, isnull (databasepropertyex(Name,'Status'),'N/A') from sys.databases This is essentially what the propertybag is returning for the status of the monitor. Is the SybariEnterpriseManager db listed as recovering according to SQL? Not from the SCOM Database neither on the Client databases. Thanks, DomSystem Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 Support

Hi Dom Did you check the autoclose setting as suggest by CaptionSlock? Cheers GrahamView OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

Could it be repaired by itself... it seems the patches came by and a reboot might have fix the issue... now it works (: Thanks, DomSystem Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 Support

Hi, will mark as answer as no activity for a long time. Feel free to re-open it. ThanksAnders Bengtsson | Microsoft PFE | blog at http://www.contoso.se