Inconsistencies in tempdb

8 May 2007 10:03 AM

LaurenceT

Hi folks
have been getting this error recently. We've swapped-out a disk which
looked to be faulty but this hasn't done the trick so we think that it
may not be a hardware issue but may be due to a problem in tempdb
itself. I have read elsewhere that if the server is restarted, that
the temp db will be recreated, but having done this, the mdf and ldf
still have Craeted dates from way before the restart happened, so that
can't have worked, so I guess my questions are...

1) Is there any way that I can check if the temp db is corrupt?
2) Should the tempdb be recreated from scratch by restarting the
server and if not how should I do this?

any further comments/suggestions would be very welcome

Event Type:    Error
Event Source:    MSSQLSERVER
Event Category:    (2)
Event ID:    5242
Description:
An inconsistency was detected during an internal operation in database
'tempdb'(ID:2) on page (1:5193). Please contact technical support.
Reference number 3.

many thanks
LT

8 May 2007 10:10 AM

Uri Dimant

Hi
Restart SQL Server. TempDB is rebuilt from scratch each time you restart sql
server.

Show quoteHide quote

"LaurenceT" <laurencetru***@gmail.com> wrote in message
news:1178618605.338639.275140@w5g2000hsg.googlegroups.com...
> Hi folks
> have been getting this error recently. We've swapped-out a disk which
> looked to be faulty but this hasn't done the trick so we think that it
> may not be a hardware issue but may be due to a problem in tempdb
> itself. I have read elsewhere that if the server is restarted, that
> the temp db will be recreated, but having done this, the mdf and ldf
> still have Craeted dates from way before the restart happened, so that
> can't have worked, so I guess my questions are...
>
> 1) Is there any way that I can check if the temp db is corrupt?
> 2) Should the tempdb be recreated from scratch by restarting the
> server and if not how should I do this?
>
> any further comments/suggestions would be very welcome
>
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 5242
> Description:
> An inconsistency was detected during an internal operation in database
> 'tempdb'(ID:2) on page (1:5193). Please contact technical support.
> Reference number 3.
>
> many thanks
> LT
>

8 May 2007 6:04 PM

Linchi Shea

If you look at the tempdb files in the file system, the Date Modified
property should reflect the date/time when the instance is recycled. You can
run DBCC CHECKDB on tempdb.

Linchi

Show quoteHide quote

"LaurenceT" wrote:

> Hi folks
> have been getting this error recently. We've swapped-out a disk which
> looked to be faulty but this hasn't done the trick so we think that it
> may not be a hardware issue but may be due to a problem in tempdb
> itself. I have read elsewhere that if the server is restarted, that
> the temp db will be recreated, but having done this, the mdf and ldf
> still have Craeted dates from way before the restart happened, so that
> can't have worked, so I guess my questions are...
>
> 1) Is there any way that I can check if the temp db is corrupt?
> 2) Should the tempdb be recreated from scratch by restarting the
> server and if not how should I do this?
>
> any further comments/suggestions would be very welcome
>
> Event Type:    Error
> Event Source:    MSSQLSERVER
> Event Category:    (2)
> Event ID:    5242
> Description:
> An inconsistency was detected during an internal operation in database
> 'tempdb'(ID:2) on page (1:5193). Please contact technical support.
> Reference number 3.
>
> many thanks
> LT
>
>