Error: 9001, Severity: 21, State: 4 | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

Error: 9001, Severity: 21, State: 4

When I checked the disk on which production server data are stored it showed "disk at risk".I was shocked to see that.Though the applications were running fine.I checked application logs in event viewer and found it consist of following error.
17053 :
LogWriter: Operating system error 1167(The device is not connected.) encountered.
Error: 9001, Severity: 21, State: 4
The log for database ‘tade’ is not available.
Error: 9001, Severity: 21, State: 1
The log for database ‘tade’ is not available.
Error: 3314, Severity: 21, State: 4
Error while undoing logged operation in database ‘tade’. Error at log record ID (15880:410:143).
Error: 3314, Severity: 21, State: 5
Error while undoing logged operation in database ‘tade’. Error at log record ID (15880:410:1). I have a maint plan which truncate the log file of all userdatabases,which is scheduled to run at 3am as no transactions happen between 9pm-7am.After checking the job history I found that the log file truncation worked fine for all user databases before this database(tade).
This job havent executed today. This disk is a new disk which came with dell server last week.So I cant say that the disk is damaged.
I am wondering what is the possible cause of this and how to avoid it.
These errors indicate log corruption. A bit strange is the "The device is not connected" message, which might be the root of all evil. I would immediately take a full backup and check hardware *very* carefully (even new disks can be damaged. Not matter how old they are).
Interestingly I think, usually such db’s are marked suspect and the only way out then is to recover from backup. —
Frank Kalis
Microsoft SQL Server MVP
http://www.insidesql.de
Ich unterstütze PASS Deutschland e.V. http://www.sqlpass.de)
Even though this is a new disk check whether it has been installed properly and no hardware issues are occuring from event viewer log. As suggested by Frank make sure you’ve full backup. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
]]>