I have a SQL Server 2008 R2.
I got a mail that the backup had failed, I opened the SQL log viewer and started browsing. And i found these two errors a bunch of times.
Date 31-01-2013 13:20:30 Log SQL Server (Current - 01-02-2013 05:13:00) Source spid20s Message Error: 9001, Severity: 21, State: 1.
Date 31-01-2013 13:20:30 Log SQL Server (Current - 01-02-2013 05:13:00) Source spid20s Message The log for database 'DB_NAME' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
After a little googling, I had read a few times that the errors indicated that the DB or log file maybe corrupt.
I read that I could confirm it, by running a
DBCC CHECKDB 'DB_NAME', so i did, and here are the last to lines of the output:
CHECKDB found 0 allocation errors and 0 consistency errors in database 'DB_NAME'. DBCC execution completed. If DBCC printed error messages, contact your system administrator.
The output shows that the DB isn't corrupt. But can the log file still be corrupt?
I also read that one solution might be run something called "Emergency Mode Repair" to fix the corrupt files. But some users did NOT recommend it.
Could another solution be to delete the log file completely and then create a new?.