|Message:||The log for database ‘%.*ls’ is not available. Check the event log for related error messages. Resolve any errors and restart the database.|
The database log was taken offline. Usually this signifies a catastrophic failure that requires the database to restart.
Diagnose other errors and restart the instance of SQL Server if it has not already restarted itself.
|Message:||The log for database ‘%.*ls’ is not available.|
|An I/O error related to data integrity has occurred for the specified database. Either the log or data portion of the database could be damaged. SQL Server has made the log for that database unavailable to prevent further data integrity problems. The I/O error that led to the 9001 message should be reported in the SQL Server error log and/or the Windows event logs.
This error could occur because of a failed ROLLBACK operation. In rare circumstances, the ROLLBACK could fail because of the server is completely out of memory, out of buffer pages, or out of log space.
Run hardware diagnostics and correct any problems. Also examine the Microsoft Windows NT system and application logs and the SQL Server error log to see if the error occurred as the result of hardware failure. Fix any hardware-related problems.
If you have persistent data inconsistency problems, try to swap out different hardware components to isolate the problem. Check that your system does not have write caching enabled on the disk controller. If you suspect this to be the case, contact your hardware vendor.
Finally, you might find it beneficial to switch to a completely new hardware system, including reformatting the disk drives and reinstalling the operating system.
RESTORE FROM BACKUP
If the problem is not hardware related and a known clean backup is available, restore the database from the backup.
If no clean backup is available, execute DBCC CHECKDB without a repair clause to determine the extent of the corruption. DBCC CHECKDB will recommend a repair clause to use. Then, execute DBCC CHECKDB with the appropriate repair clause to repair the corruption.
CAUTION: If you are unsure what effect DBCC CHECKDB with a repair clause has on your data, contact your primary support provider before executing this statement.
If running DBCC CHECKDB with one of the repair clauses does not correct the problem, contact your primary support provider.