June 16, 2010 at 11:41 am
Hello DB Champs
I was looking into the ErrorLog file and found the below error:
2010-06-16 01:43:57.35 spid6s SQL Server has encountered 86008 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [D:\MSSQL$\MSSQL.1\MSSQL\Data\SIEBEL_Data_10.NDF] in database [SIEBEL] (7). The OS file handle is 0x0000000000000C74. The offset of the latest long I/O is: 0x000006d3422000
2010-06-15 01:28:48.16 spid10s SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [D:\MSSQL$\MSSQL.1\MSSQL\DATA\MSDBLog.ldf] in database [msdb] (4). The OS file handle is 0x0000000000000B18. The offset of the latest long I/O is: 0x00000000f9b000
What could be the possible causes of the error message? Any suggestion to stop the errors to come?
Thanks.
June 16, 2010 at 11:57 am
The following is a Link to article with a pretty good description as to how and why this error can occur. there are also many other various blogs and posts most of which hold the veiw that this is not a SQL problem at all. This is likely the best article however for giving some direction.
http://www.sql-server-pro.com/i-o-requests-taking-longer-than-15-seconds-to-complete.html
Dan
If only I could snap my figures and have all the correct indexes apear and the buffer clean and.... Start day dream here.
June 16, 2010 at 6:45 pm
This article from Microsoft has a little bit more information: http://support.microsoft.com/kb/897284/en-us
June 18, 2010 at 6:47 am
Are you seeing this while running dbcc checkdb against large databases? I have seen this occur under that condition... SQL 2005 performs more extensive checks in Checkdb than 2000 did and therefore MS recommends running checkdb with physical_only.
February 19, 2011 at 3:14 pm
We had these errors for a while (in most cases when Index rebuild or reorganize jobs were running). SQL Server was installed on Windows 2003 64 bit, database files on SAN. We have tried firmware update, NIC driver update, but it didn't help. Just last week these errors disappeared when I have changed under network card's property for the "File and Print Sharing" to "Maximize data throughput for network applications". Something interesting I have noticed when you set System properties->Performance Options-> Advanced-> Memory Usage-> System cache to optimize performance it actually resets NIC setting "Maximize data throughput for network applications" to default ("Maximize data throughput for files sharing").
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply