August 11, 2004 at 7:51 pm
We had a sudden error, which caused our sql server to basically freeze and required a restart.
We are win2k3, Enterprise Edition, SP3 plus security patch, 8 proc, 8GB. We use a NAS device for disk.
Any information or advice would be greatly appreciated!
2004-08-10 18:15:54.50 spid2 LogWriter: Operating system error 1450(Insufficient system resources exist to complete the requested service.) encountered.
2004-08-10 18:15:54.54 spid2 Write error during log flush. Shutting down server
2004-08-10 18:15:54.85 spid19 Error: 9001, Severity: 21, State: 4
2004-08-10 18:15:54.85 spid19 The log for database <databasenameremoved> is not available..
2004-08-10 18:15:56.03 spid22 Database <databasenameremoved> cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.
2004-08-10 18:15:56.12 spid22 Database <databasenameremoved> cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.
2004-08-10 18:15:56.17 spid22 Database <databasenameremoved> cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.
2004-08-10 18:15:58.74 spid22 Starting up database <databasenameremoved>.
2004-08-10 18:16:09.78 spid22 Analysis of database <databasenameremoved> (8) is 100% complete (approximately 0 more seconds)
2004-08-10 18:16:09.80 spid22 Recovery of database <databasenameremoved> (8) is 0% complete (approximately 3 more seconds) (Phase 2 of 3).
2004-08-10 18:16:13.38 spid22 Recovery of database <databasenameremoved> (8) is 100% complete (approximately 0 more seconds) (Phase 2 of 3).
2004-08-10 18:16:13.39 spid22 840 transactions rolled forward in database <databasenameremoved> (8).
2004-08-10 18:16:13.49 spid22 0 transactions rolled back in database <databasenameremoved> (8).
2004-08-10 18:16:13.52 spid22 Recovery is checkpointing database <databasenameremoved> (8)
August 16, 2004 at 8:00 am
This was removed by the editor as SPAM
August 16, 2004 at 8:10 am
The errors point there cound be problems in I/O subsystem, Check application/system logs.
August 16, 2004 at 10:32 am
I/O subsystem, which is a NAS device, is clean.
August 16, 2004 at 11:40 am
Collect the perfmon stats for disk queue lengths. Usually this is an indication of disk system saturation. Are any backups running at the time of the error?
August 16, 2004 at 12:01 pm
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply