July 1, 2010 at 3:57 am
My production SQL server restarted itself last night. Any ideas on where I can get some more information regarding the below error message?
SQL Server must shut down in order to recover a database (database ID 1). The database is either a user database that could not be shut down or a system database. Restart SQL Server. If the database fails to recover after another startup, repair or restore the database.
July 1, 2010 at 4:28 am
SQLSeTTeR (7/1/2010)
My production SQL server restarted itself last night. Any ideas on where I can get some more information regarding the below error message?SQL Server must shut down in order to recover a database (database ID 1). The database is either a user database that could not be shut down or a system database. Restart SQL Server. If the database fails to recover after another startup, repair or restore the database.
database with the ID =1 is your master database
have a look in your error logs for more information?
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This thing is addressing problems that dont exist. Its solution-ism at its worst. We are dumbing down machines that are inherently superior. - Gilfoyle
July 1, 2010 at 4:37 am
Two things jump out at me. Any ideas?
Event Type:Error
Event Source:MSSQL$xxxxx
Event Category:(3)
Event ID:19019
Date:6/30/2010
Time:10:33:38 PM
User:N/A
Computer:xxxxx
Description:
[sqsrvres] CheckServiceAlive: Service is dead
Event Type:Error
Event Source:MSSQL$xxxxx
Event Category:(2)
Event ID:602
Date:6/30/2010
Time:10:33:16 PM
User:N/A
Computer:xxxxx
Description:
Could not find an entry for table or index with partition ID 491897996509184 in database 2. This error can occur if a stored procedure references a dropped table, or metadata is corrupted. Drop and re-create the stored procedure, or execute DBCC CHECKDB.
July 1, 2010 at 4:50 am
SQLSeTTeR (7/1/2010)
Could not find an entry for table or index with partition ID 491897996509184 in database 2. This error can occur if a stored procedure references a dropped table, or metadata is corrupted. Drop and re-create the stored procedure, or execute DBCC CHECKDB.
Not looking good. What's the exact version of SQL that you're running? There was a bug with tempDB that was fixed in a very recent hotfix.
Also, please run a database consistency check on the 4 system databases as soon as possible.
DBCC CheckDB (<Database Name>) WITH No_INFOMSGS, ALL_ERRORMSGS
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 1, 2010 at 5:03 am
SELECT @@VERSION
--Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86) Feb 9 2007 22:47:07 Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
What is the impact to the system DB's and end users of running those DBCC's?
July 1, 2010 at 5:14 am
There were quite a few nasty bugs in SP2. Consider upgrading to SP3 + the latest hotfix.
Minimal impact from the checkDBs, the system databases are small.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 1, 2010 at 5:19 am
I ran the DBCC's on the system DB's. Stupid question. Where do I find the output? In my query window I am getting the command completed successfully.
July 1, 2010 at 5:29 am
That is the output.
If there was anything wrong it would have said so in the output window.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 1, 2010 at 5:33 am
Anything else I can do for now?
July 1, 2010 at 5:40 am
Make plans to patch the server
Check the windows event log, make sure that there are no more errors relating to the DBs, to any hardware issues around the time of restart,
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 1, 2010 at 5:44 am
Thank you for all your help!!
July 1, 2010 at 5:52 am
Thank you very MUCH! You're a lifesaver!
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply