SqlDumpExceptionHandler Never seen this before? - SQL Server Forums

Home | Weblogs | Forums

Site Sponsored By: SQLDSC - SQL Server Desired State Configuration

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.

All Forums

SQL Server 2000 Forums

SQL Server Administration (2000)

SqlDumpExceptionHandler Never seen this before?

Author

Topic

rikleo2001
Posting Yak Master

185 Posts

Posted - 2007-01-15 : 14:29:58

Hello experts,

I am running SQL Server 2000 with sp4. This server is installed on VMWARE.
Suddenly from last 3 weeks I started getting strange type of messages, never seen them before.

Please give me an idea about those....Thanks in Advance...

Here is Detail of error log.

-***************************************
SQL Server has encountered 1 occurrence(s) of IO requests taking longer than 15 seconds to complete on file [d:\Program Files\Microsoft SQL Server\MSSQL\data\tempdb.mdf] in database [tempdb] (2). The OS file handle is 0x00000480. The offset of the latest long IO is: 0x00000027c78000

SQL Server has encountered 1 occurrence(s) of IO requests taking longer than 15 seconds to complete on file [d:\Program Files\Microsoft SQL Server\MSSQL\data\templog.ldf] in database [tempdb] (2). The OS file handle is 0x00000468. The offset of the latest long IO is: 0x00000000bdf000

Sort read failure (bad page ID). pageid = (0x1:0x2646e), dbid = 2, file = d:\Program Files\Microsoft SQL Server\MSSQL\data\tempdb.mdf. Retrying.

I/O error (bad page ID) detected during read at offset 0x0000004c8dc000 in file 'd:\Program Files\Microsoft SQL Server\MSSQL\data\tempdb.mdf'..

Using 'dbghelp.dll' version '4.0.5'
*Stack Dump being sent to d:\Program Files\Microsoft SQL Server\MSSQL\log\SQLDump0007.txt

SqlDumpExceptionHandler: Process 53 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process..
* *********************************************************

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2007-01-15 : 14:37:12

It looks like you may have disk problems.

I'd run DBCC CHECKDB on all of the databases to determine if you have any corruption due to it.

I'd also check the Event Log to see if you can find any IO events.

You may want to think about moving your databases to another server until the problem can be corrected on this server.

Tara Kizer

rikleo2001
Posting Yak Master

185 Posts

Posted - 2007-01-15 : 14:49:48

Thanks Tara.

I will run DBCC shortly to see that.
I did check application event, which notify same error mentioned in SQL Error log, I did picked up one of the foloowing error.
Error: 5180, Severity: 22, State: 1
Could not open FCB for invalid file ID 80 in database 'tempdb'.
Does it make any sense?

It is complicated to move this database to other server as it is 24/7 production Server. so you are saying that it is relating with Physical Disk?

I think I have to run CHECKDB command first, is there any problem if I use it on live DB in low peek hours?

Thanks again

Kaff

SKR

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2007-01-15 : 14:54:37

I would run DBCC CHECKDB as soon as possible as if there's any corruption, you need to get that fixed quickly.

And yes it appears you've got disk problems. I'd open a ticket with Microsoft to be sure though.

Tara Kizer

rikleo2001
Posting Yak Master

185 Posts

Posted - 2007-01-15 : 17:49:56

Here you go, ran DBCC CHECKDB

CHECKDB found 0 allocation errors and 54 consistency errors in database 'dbS_CoreData'.
repair_fast is the minimum repair level for the errors found by DBCC CHECKDB (dbS_CoreData).
DBCC execution completed. If DBCC printed error messages, contact your system administrator.

Any suggestion to get rid of these errors?

Thanks in advance

SKR

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2007-01-15 : 17:59:39

You'll want to post the entire output of the DBCC CHECKDB command in the Data Corruption forum here. Microsoft Engineers frequent that forum and help out there.

You should know that these problems may appear again even after fixed if you don't correct what caused this problem in the first place. Data corruption is typically caused by disk issues, which is what I suspected based upon the IO errors that you posted.

Tara Kizer

rikleo2001
Posting Yak Master

185 Posts

Posted - 2007-01-15 : 18:10:22

Thanks Tara.

Posted under following ID
http://sqlteam.com/forums/topic.asp?TOPIC_ID=77612

Thanks heaps and let me know if you can provide further guidelines on that.

SKR

rikleo2001
Posting Yak Master

185 Posts

Posted - 2007-01-21 : 19:40:46

Thanks All.
Sorry for Late reply..
I Done index rebuilding. Got error.
Then I executed CHECKDB with Repair_Fast option, and It worked this time., I then re-built all Indexes again.

I take it as my luck. Many Thanks to Paul and Tara for their help.

It would be really great that I can have any guideline about how to regularly perform tuning on my production database?
Much appreciated.

SKR

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources