Sqlerrorlog Message_Io_Problem

Question

Post reply

Sqlerrorlog Message_Io_Problem

muthukkumaran Kaliyamoorthy

SSCoach

Points: 19026
More actions
January 27, 2009 at 12:33 am

#126953

Hi All,
I am working in SS2K standard and WIN2003 standard and I got below error message in sql error log
8.00.2050
SQL Server has encountered 6 occurrence(s) of IO requests taking longer than 15 seconds to complete on file [e:\mssql\datafiles\MSSQL\data\stdfqads_Data.MDF] in database [stdfqads] (26). The OS file handle is 0x0000062C. The offset of the latest long IO is: 0x00000151ba0000
also this error(More than 100 time)
DBCC TRACEON 3604 SERCVER PROCESS ID (SPID)88
Please Help Me...
Muthukkumaran Kaliyamoorthy
https://www.sqlserverblogforum.com/

Viewing 6 posts - 1 through 5 (of 5 total)

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

MANU-J. SSC-Dedicated Points: 31126 More actions · Answer 1

What is the size,autogrow increment of this data file?

MJ

muthukkumaran Kaliyamoorthy SSCoach Points: 19026 More actions · Answer 2

MANU,

Thanks for ur replay manu.My Database Size is 9448 MB,Data file size 7705 MB,Auto growth size is 100MB U.G and this is Web application project.

Error_log_error:

2009-02-02 00:00:47.21 backup Log backed up: Database: stdfqads, creation date(time): 2006/06/29(10:52:48), first LSN: 32270:9771:1, last LSN: 32538:27882:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'e:\mssql\datafiles\MSSQL

BACKUP\stdfqads_tlog_200902020000.TRN'}).

2009-02-02 02:17:17.49 spid1 SQL Server has encountered 1 occurrence(s) of IO requests taking longer than 15 seconds to complete on file [e:\mssql\datafiles\MSSQL\data\stdfqads_Data.MDF] in database [stdfqads] (26). The OS file handle is 0x00000664. The offset of the latest long IO is: 0x00000143e70000

2009-02-02 02:22:17.49 spid54 SQL Server has encountered 1 occurrence(s) of IO requests taking longer than 15 seconds to complete on file [e:\mssql\datafiles\MSSQL\data\stdfqads_Data.MDF] in database [stdfqads] (26). The OS file handle is 0x00000664. The offset of the latest long IO is: 0x000001d7d28000

2009-02-02 02:33:46.99 spid54 DBCC CHECKDB (stdfqads) executed by sa found 0 errors and repaired 0 errors. Elapsed time: 0 hours 3 minutes 46 seconds.

2009-02-02 03:04:04.93 backup Database backed up: Database: stdfqads, creation date(time): 2006/06/29(10:52:48), pages dumped: 865934, first LSN: 32794:11746:1, last LSN: 32794:11783:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK:{'e:\mssql\datafiles\MSSQL\BACKUP\stdfqads_db_200902020300.BAK'}

I couldn't finout the reason yet now.Help me...

Tanks&Regards,

Muthuuu.

Muthukkumaran Kaliyamoorthy
https://www.sqlserverblogforum.com/

Nikhil-843675 SSC Eights! Points: 945 More actions · Answer 3

Hi,

Tou may find your solution over here...

Please go through following

http://blogs.msdn.com/sqlserverstorageengine/archive/2006/06/21/642314.aspx

Nikhil-843675 SSC Eights! Points: 945 More actions · Answer 4

What does the “I/O request” error below represent?

2008-04-21 13:26:42.480 spid364 Microsoft SQL Server 2005 - 9.00.3177.00 (Intel X86)

2008-04-22 16:30:02.140 spid6s SQL Server has encountered 2 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [F:\sql data files\xxx.MDF] in database [xxx] (5).

2008-04-22 16:32:08.780 spid6s SQL Server has encountered 2 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [H:\sql data files\xxx_data_4.NDF] in database [xxx] (5).

Research and Findings

---------------------------------

These errors may occur as result of “CPU Drift” and can be ignored and disabled, howerver, first verify both SQL DMV sys.dm_io_pending_io_requests and Windows Performance counters don’t indicate any IO delays.

On computers with multiple CPUs, the CPUs are designed to “sleep” during periods of low workload. When CPUs sleep, SQL may not accurately determine CPUs overall workload and incorrectly report this as IO WARNING shown above, however, this does not represent an actual CPU performance problem.

To confirm if the CPUs entered low-power state, SQL Server Escalation Services created RDTSC (Read Time Stamp Counter) utility to report total CPU sleep time. The report confirmed the CPUs were sleeping up to 24 seconds. This would be enough for SQL Server to incorrectly report this a slow IO. Both AMD’s and INTEL’s web sites describe the ability for CPUs to sleep.

RDTSCTest.exe [-md|-mt]

-md Detailed output (default)

-mt CPU speeds in table format

-- Current CPU Speeds --

Runtime CPU ExpectedMHz ActualMHz RDTSCTicks DriftMS

-------------------- ---- ----------- --------- -------------------- ----------------

2008-04-22 17:53:36 0 3502 3503 0x0001564772F87FA72 16123.4

2008-04-22 17:53:36 8 3502 3506 0x00015647D8B7AE21D 23922.5

2008-04-22 17:53:36 16 3502 3507 0x00015647B5FEB4A39 21260.9

For more information on RDTSC can be found at

http://blogs.msdn.com/psssql/archive/2007/08/19/sql-server-2005-rdtsc-truths-and-myths-discussed.aspx

Starting with SQL 2005 SP2 we’ve included two trace flags to disable the reporting of CPU Drift errors in the SQL Server errorlog.

Disable this error using Trace Flag 8033

The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.

Disable this error using Trace Flag 830

SQL Server has encountered 2 occurrence(s) of I/O requests taking longer than 15 seconds to complete

muthukkumaran Kaliyamoorthy SSCoach Points: 19026 More actions · Answer 5

Nikhil,

I run the following DMV query

sys.dm_io_pending_io_requests.I am using 2-node cluster .

io_typeIo_pending_ms_ticks io_pending

disk3431

disk3121

disk2501

disk311

disk151

disk01

disk4210

disk2181

disk1401

disk931

disk151

disk4061

disk3751

disk2031

disk781

disk3281

disk1091

disk461

disk151

disk2181

disk1091

disk931

disk621

disk151

disk01

disk2181

disk01

disk931

disk311

disk3431

disk1871

In this situation what can i do.

Muthukkumaran Kaliyamoorthy
https://www.sqlserverblogforum.com/