The log for database 'tempdb' is not available

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

SQL Server 2008 Forums

SQL Server Administration (2008)

The log for database 'tempdb' is not available

Author

Topic

denis_the_thief
Aged Yak Warrior

596 Posts

Posted - 2011-01-19 : 13:25:06

SQL Server shut itself down yesterday. Some weird errors. Any ideas where to start?


SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\templog.ldf] in database [tempdb] (2).  The OS file handle is 0x000006C4.  The offset of the latest long I/O is: 0x00000001540000

...

LogWriter: Operating system error 1784(error not found) encountered.

...

The log for database 'tempdb' is not available. Check the event log for related error messages. Resolve any errors and restart the database.

then

SQL Server must shut down in order to recover a database (database ID 2). 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.

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2011-01-19 : 13:36:12

Sounds like you ran into a disk problem. Run hardware diagnostics to figure out what's going wrong.

It should be able to restart on its own because tempdb gets recreated, but you do need to resolve the hardware issue to prevent this from happening again.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog

denis_the_thief
Aged Yak Warrior

596 Posts

Posted - 2011-01-19 : 13:46:03

quote:
Originally posted by tkizer

Sounds like you ran into a disk problem. Run hardware diagnostics to figure out what's going wrong.

It should be able to restart on its own because tempdb gets recreated, but you do need to resolve the hardware issue to prevent this from happening again.

Tara Kizer

Thankyou for suggesting hardware.

For whatever reason it did not restart on its own although I was able to restart it easy enough.

Sachin.Nand

2937 Posts

Posted - 2011-01-23 : 09:57:30

Maybe you should set up a alert in case the data or log files are over 80%.

PBUH

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources