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.
| Author |
Topic |
|
rdugre
Starting Member
32 Posts |
 Posted - 2004-01-16 : 15:30:38
|
| We are running SQL Server 2000 Enterprise under Windows 2000 Advanced Server (2 clustered machines accessing shared storage). We have several databases under SQL Server and one of our databases became "Suspect" in the middle of the day today. Once it became suspect, it was made completely unavailable.Here are the error messages that appeared in the log file when this all happened:----------------------------------2004-01-16 12:43:20.17 spid2 LogWriter: Operating system error 170(The requested resource is in use.) encountered.2004-01-16 12:43:20.18 spid2 Write error during log flush. Shutting down server2004-01-16 12:43:20.18 spid65 Error: 9001, Severity: 21, State: 4.2004-01-16 12:43:21.22 spid18 Error: 926, Severity: 14, State: 1.2004-01-16 12:43:21.22 spid18 Error: 926, Severity: 14, State: 1.2004-01-16 12:43:21.22 spid18 Error: 926, Severity: 14, State: 1.2004-01-16 12:43:21.22 spid18 Error: 926, Severity: 14, State: 1.2004-01-16 12:43:21.33 spid18 fcb::close-flush: Operating system error 170(The requested resource is in use.) encountered.2004-01-16 12:43:21.33 spid18 fcb::close-flush: Operating system error 170(The requested resource is in use.) encountered.2004-01-16 12:43:21.33 spid18 Starting up database 'MyDatabase'.2004-01-16 12:43:21.33 spid18 Error: 823, Severity: 24, State: 6.2004-01-16 12:43:21.33 spid18 Error: 823, Severity: 24, State: 2.----------------------------------We were able to remedy the situation by restarting SQL Server with the Server Manager app. Once restarted, the database came back online immediately. I ran DBCC CHECKALLOC, TEXTALL, and CHECKDB with no errors reported.Does anyone know what may have caused this? It almost seems like a disk problem, but we show no other signs of there being anything wrong with the disk. Could it be memory related? We have 2Gb of RAM in the machine.Any help would be greatly appreciated. |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-01-16 : 16:05:59
|
| Have you run the diagnostic checks on the hardware?Tara |
 |
|
|
Grouchie
Starting Member
7 Posts |
Posted - 2004-01-19 : 10:31:30
|
| If this is IBM hardware, there is currently an issue with raid controllers corrupting raids. I am not sure the full information on this, but IBM released a bunch of bad drivers, and it ended up screwing up raids... my Hardware guy had a hell of a time figuring the issue out, but finally IBM fessed up on how to figure it out... If you have IBM hardware send me an email lee.smith@infarmbureau.com and I will have the server guy send you a note about it.... |
|
|
|
rdugre
Starting Member
32 Posts |
Posted - 2004-01-22 : 11:39:24
|
| We ran the diagnostics for the drive array and it reported that everything was okay. The issue hasn't happened again and its been almost a week. Does stuff like this just happen on occasion?Thanks for the note about IBM drives. This is a Dell RAID array, so I'll have to check to see if they are using IBM drives. |
|
|
|
|
|
|
|
|
Database Suspect Issue