<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>VMware Communities: Message List - Virtual Center database in suspect state after reboot</title>
    <link>http://communities.vmware.com/community/vmtn/mgmt/vc?view=discussions</link>
    <description>Most recent forum messages</description>
    <language>en</language>
    <pubDate>Wed, 20 Aug 2008 09:32:51 GMT</pubDate>
    <generator>Clearspace 1.10.12 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2008-08-20T09:32:51Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>Re: Virtual Center database in suspect state after reboot</title>
      <link>http://communities.vmware.com/message/1028750?tstart=0#1028750</link>
      <description>For some reason the SQL Server wasn't shutdown the way it should have been. If this continous after each reboot try to manually shutdown the SQL instance first...&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
Duncan&lt;br /&gt;
My virtualisation blog:&lt;br /&gt;
&lt;a class="jive-link-external" href="http://www.yellow-bricks.com"&gt;http://www.yellow-bricks.com&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
If you find this information useful, please award points for "correct" or "helpful".</description>
      <pubDate>Wed, 20 Aug 2008 09:32:51 GMT</pubDate>
      <author>depping</author>
      <guid>http://communities.vmware.com/message/1028750?tstart=0#1028750</guid>
      <dc:date>2008-08-20T09:32:51Z</dc:date>
      <clearspace:dateToText>1 year, 3 months ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: Virtual Center database in suspect state after reboot</title>
      <link>http://communities.vmware.com/message/1028712?tstart=0#1028712</link>
      <description>Hello  ,   if the database is suspect then you'll need to restore it from a backup.  You can use the &lt;a class="jive-link-external" href="http://www.microsoft.com/downloads/details.aspx?FamilyId=C243A5AE-4BD1-4E3D-94B8-5A0F62BF7796"&gt;SQL Express Management Studio&lt;/a&gt;  to check the status of the database.  The database is for update manager and your VirtualCenter db is still OK.  Thus you can login and use VirtualCenter.  You will see some errors if you try to use Update Manager.</description>
      <pubDate>Wed, 20 Aug 2008 08:36:31 GMT</pubDate>
      <author>Dave.Mishchenko</author>
      <guid>http://communities.vmware.com/message/1028712?tstart=0#1028712</guid>
      <dc:date>2008-08-20T08:36:31Z</dc:date>
      <clearspace:dateToText>1 year, 3 months ago</clearspace:dateToText>
    </item>
    <item>
      <title>Virtual Center database in suspect state after reboot</title>
      <link>http://communities.vmware.com/message/1028687?tstart=0#1028687</link>
      <description>&lt;br /&gt;
Hello all,&lt;br /&gt;
&lt;p /&gt;
On our Virtual Center 2.5U1 server we are running SQL Express 2005. Everything seems to work fine but after reboot our server monitoring system (MOM 2005) detects degraded database health. At one or two occasions after reboot an alarm is raised that database is in suspect state. After that no more alarms occurs. I have found nothing in eventlogs that points to a problem with the database.&lt;br /&gt;
&lt;p /&gt;
Anyone seen this? Any thoughts?&lt;br /&gt;
&lt;p /&gt;
Thank you! &lt;img class="jive-emoticon" border="0" src="http://communities.vmware.com/images/emoticons/happy.gif" alt=":)" /&gt;&lt;br /&gt;
&lt;p /&gt;
/Bj&amp;ouml;rn&lt;br /&gt;
&lt;p /&gt;
 Here is the alarm:&lt;br /&gt;
&lt;p /&gt;
&lt;table class="jive-wiki-table"&gt;
&lt;tr&gt;
&lt;td&gt;Description: The database VIM_UMDB in instance SQLEXP_VIM is in a critical state. The state is Suspect.&lt;/td&gt;
&lt;th&gt;Name:&lt;/th&gt;
&lt;td&gt;SQL Server Database Health - Database is unhealthy&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Severity:&lt;/td&gt;
&lt;td&gt;Warning&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Resolution State:&lt;/td&gt;
&lt;td&gt;New&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Domain:&lt;/td&gt;
&lt;td&gt;DOMAIN&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Computer:&lt;/td&gt;
&lt;td&gt;SERVER&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Time of First Event:&lt;/td&gt;
&lt;td&gt;2008-08-19 22:30:04&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Time of Last Event:&lt;/td&gt;
&lt;td&gt;2008-08-20 03:00:03&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Alert latency:&lt;/td&gt;
&lt;td&gt;4 sec&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Problem State:&lt;/td&gt;
&lt;td&gt;Active&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Repeat Count:&lt;/td&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Age:&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Source:&lt;/td&gt;
&lt;td&gt;SQL Server 2005 Database Health&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Alert Id:&lt;/td&gt;
&lt;td&gt;c991af06-fa4c-4f01-858c-38563d0377d1&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Rule (enabled):&lt;/td&gt;
&lt;td&gt;Microsoft SQL Server\SQL Server 2005\State Monitoring and Service Discovery\SQL Server Database Health - Database is unhealthy&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;/tr&gt;
&lt;/table&gt;
&lt;br clear="left" /&gt;
&lt;p /&gt;</description>
      <pubDate>Wed, 20 Aug 2008 08:10:32 GMT</pubDate>
      <author>BjornJohansson</author>
      <guid>http://communities.vmware.com/message/1028687?tstart=0#1028687</guid>
      <dc:date>2008-08-20T08:10:32Z</dc:date>
      <clearspace:dateToText>1 year, 3 months ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
  </channel>
</rss>

