I/O errors in SQL

  • Hello!!

    I have a McAfee ePO setup where we use SQL  for database.

    I noticed few monitors/say tables are not displaying properly in dashboards. .

    When I went through the sql logs I found below errors.

    Could these errors be a reason for not seeing the tables getting populated ?

    2022-03-21 02:00:26.35 spid16s SQL Server has encountered 808 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [T:\TempDB\tempdb_df4.ndf] in database [tempdb] (2). The OS file handle is 0x0000000000000C30. The offset of the latest long I/O is: 0x00000215ce0000

    2022-03-21 02:00:26.35 spid16s SQL Server has encountered 807 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [T:\TempDB\tempdb_df5.ndf] in database [tempdb] (2). The OS file handle is 0x0000000000000C34. The offset of the latest long I/O is: 0x00000215c60000

    2022-03-21 02:00:26.35 spid16s SQL Server has encountered 805 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [T:\TempDB\tempdb_df3.ndf] in database [tempdb] (2). The OS file handle is 0x0000000000000C0C. The offset of the latest long I/O is: 0x00000215c20000

    2022-03-21 02:00:26.35 spid16s SQL Server has encountered 811 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [T:\TempDB\tempdb_df6.ndf] in database [tempdb] (2). The OS file handle is 0x0000000000000C14. The offset of the latest long I/O is: 0x00000215bb0000

    2022-03-21 02:00:26.35 spid16s SQL Server has encountered 815 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [T:\TempDB\tempdb_df2.ndf] in database [tempdb] (2). The OS file handle is 0x0000000000000C08. The offset of the latest long I/O is: 0x00000215c10000

    2022-03-21 02:00:26.35 spid16s SQL Server has encountered 806 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [T:\TempDB\tempdb_df7.ndf] in database [tempdb] (2). The OS file handle is 0x0000000000000C3C. The offset of the latest long I/O is: 0x00000215c80000

    2022-03-21 02:00:26.35 spid16s SQL Server has encountered 809 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [T:\TempDB\tempdev.mdf] in database [tempdb] (2). The OS file handle is 0x0000000000000B90. The offset of the latest long I/O is: 0x00000215eb0000

    2022-03-21 02:00:26.35 spid16s SQL Server has encountered 808 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [T:\TempDB\tempdb_df8.ndf] in database [tempdb] (2). The OS file handle is 0x0000000000000C40. The offset of the latest long I/O is: 0x00000215c90000

    2022-03-21 02:00:26.35 spid16s SQL Server has encountered 14 occurrence(s) of I/O requests taking longer than 15 seconds to co

  • It could be timing out. Contact your McAfee ePO vendor.

    An sich it shouldn't be a cause for the empty dashboards.

     

  • Why do you have McAfee scanning your database files??? Those should be excluded.

    Michael L John
    If you assassinate a DBA, would you pull a trigger?
    To properly post on a forum:
    http://www.sqlservercentral.com/articles/61537/

  • Absolutely correct.  McAfee could end up damaging your db files, esp. log files.

    SQL DBA,SQL Server MVP(07, 08, 09) "Money can't buy you happiness." Maybe so, but it can make your unhappiness a LOT more comfortable!

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply