|
sql
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
SQL 2008 not starting
relevant lines form the errorlog when the first error is mentioned. I have tried copying the model database files from another SQL server at the same build level but the error still occurs. Does anybody else have any suggestions to get this running? 2009-06-18 16:58:49.08 spid10s Error: 913, Severity: 16, State: 6. 2009-06-18 16:58:49.08 spid10s Could not find database ID 3. Database may not be activated yet or may be in transition. Reissue the query once the database is available. If you do not think this error is due to a database that is transitioning its state and this error continues to occur, contact your primary support provider. Please have available for review the Microsoft SQL Server error log and any additional information relevant to the circumstances when the error occurred. 2009-06-18 16:58:49.08 spid10s Could not create tempdb. You may not have enough disk space available. Free additional disk space by deleting other files on the tempdb drive and then restart SQL Server. Check for additional errors in the event log that may indicate why the tempdb files could not be initialized. 2009-06-18 16:58:49.08 spid10s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
Show quote
Hide quote
"Robin9876" <robin9***@hotmail.com> wrote in message Looks like you have some issues with your databases themselves. SQL Server news:e0f6fc75-650c-4c2e-98ae-569c7c2e1672@o36g2000vbi.googlegroups.com... > On a SQL 2008 (SP1) an instance is not starting up. Below is the > relevant lines form the errorlog when the first error is mentioned. I > have tried copying the model database files from another SQL server at > the same build level but the error still occurs. > > Does anybody else have any suggestions to get this running? > > 2009-06-18 16:58:49.08 spid10s Error: 913, Severity: 16, State: 6. > 2009-06-18 16:58:49.08 spid10s Could not find database ID 3. > Database may not be activated yet or may be in transition. Reissue the > query once the database is available. If you do not think this error > is due to a database that is transitioning its state and this error > continues to occur, contact your primary support provider. Please have > available for review the Microsoft SQL Server error log and any > additional information relevant to the circumstances when the error > occurred. > 2009-06-18 16:58:49.08 spid10s Could not create tempdb. You may > not have enough disk space available. Free additional disk space by > deleting other files on the tempdb drive and then restart SQL Server. > Check for additional errors in the event log that may indicate why the > tempdb files could not be initialized. > 2009-06-18 16:58:49.08 spid10s SQL Trace was stopped due to server > shutdown. Trace ID = '1'. This is an informational message only; no > user action is required. is trying to connect to the system dbs. DB ID 3 is usually the model database and the problem with tempdb suggests that you do not have enough hard disk space. Check to ensure you have diskspace on the drives that these system dbs are loaded on. Ensure that your mdf files are not corrupted for master, model and msdb. If you have placed these databases on a SAN drive somewhere, ensure that the SQL Server service accounts still have access to those drives etc. That is where I would start. Rick Sawtell MCT, MCSD, MCDBA, MCITPro .... in addition: Either prepare to rebuild system databases (read-up
on the subject and the consequences) and/or Google for 3607, 3608 and 3609. One of those trace flags might allow you to stat your SQL Server so you can restore your broken model database (if that indeed is your problem). If you don't feel comfortable with these actions, I suggest you hire a consultant or let MS Support hand-hold you through the process. -- Show quoteHide quoteTibor Karaszi, SQL Server MVP http://www.karaszi.com/sqlserver/default.asp http://sqlblog.com/blogs/tibor_karaszi "Rick Sawtell" <r_sawtell@nospam.hotmail.com> wrote in message news:%23ZlrgTD8JHA.4404@TK2MSFTNGP04.phx.gbl... > > "Robin9876" <robin9***@hotmail.com> wrote in message > news:e0f6fc75-650c-4c2e-98ae-569c7c2e1672@o36g2000vbi.googlegroups.com... >> On a SQL 2008 (SP1) an instance is not starting up. Below is the >> relevant lines form the errorlog when the first error is mentioned. >> I >> have tried copying the model database files from another SQL server >> at >> the same build level but the error still occurs. >> >> Does anybody else have any suggestions to get this running? >> >> 2009-06-18 16:58:49.08 spid10s Error: 913, Severity: 16, State: >> 6. >> 2009-06-18 16:58:49.08 spid10s Could not find database ID 3. >> Database may not be activated yet or may be in transition. Reissue >> the >> query once the database is available. If you do not think this >> error >> is due to a database that is transitioning its state and this error >> continues to occur, contact your primary support provider. Please >> have >> available for review the Microsoft SQL Server error log and any >> additional information relevant to the circumstances when the error >> occurred. >> 2009-06-18 16:58:49.08 spid10s Could not create tempdb. You may >> not have enough disk space available. Free additional disk space by >> deleting other files on the tempdb drive and then restart SQL >> Server. >> Check for additional errors in the event log that may indicate why >> the >> tempdb files could not be initialized. >> 2009-06-18 16:58:49.08 spid10s SQL Trace was stopped due to >> server >> shutdown. Trace ID = '1'. This is an informational message only; no >> user action is required. > > > Looks like you have some issues with your databases themselves. SQL > Server is trying to connect to the system dbs. DB ID 3 is usually > the model database and the problem with tempdb suggests that you do > not have enough hard disk space. > > Check to ensure you have diskspace on the drives that these system > dbs are loaded on. Ensure that your mdf files are not corrupted for > master, model and msdb. > > If you have placed these databases on a SAN drive somewhere, ensure > that the SQL Server service accounts still have access to those > drives etc. > > That is where I would start. > > Rick Sawtell > MCT, MCSD, MCDBA, MCITPro > > > > > >
Other interesting topics
HELP, RAN OUT OF DISK SPACE
Run 32-bit and 64-bit instances on same machine Reseeding identity field Change Column Position SQL Server 2008 / 2005 / 2000 / 7 / 6.5 largest possible database? logshipping on 2000 How to narrow down the failure message Tempdb log Sql Server Shared Hosting Compare Table Structure |
|||||||||||||||||||||||