August 20, 2013 at 1:50 pm
One of the databases in my clustered instance is in the recovery pending state.
I see the following error in the SQL Server error logs:
I think the database has gone corrupted. How could I fix the issue now?
The operating system returned error 1167(The device is not connected.) to SQL Server during a read at offset 0000000000000000 in file 'X:\\MSSQL\DATA\Giraffe_log.LDF'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
August 20, 2013 at 2:16 pm
I could not run a database consistency check on this database. I had to do the following things to recover the database:
1. Put the database in single user mode with immediate rollback option.
2. Set the database in emergency mode
3. Ran the database consistency check with repair_rebuild option but it didn't work.
4. Ran the database consistency check with REPAIR_ALLOW_DATA_LOSS option. The consistency check ran without any consistency errors.
5. Database cameup online in the single user mode. I switched it to multi user mode.
Now, the database is accessible.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply