Tempdb dbcc checkdb errors

Hi
I'm having errors (lvl 16) on tempdb :
...
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:3781) with latch type UP. 2(The system cannot find the file specified.) failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:3782) with latch type UP. 2(The system cannot find the file specified.) failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:3788) with latch type UP. 2(The system cannot find the file specified.) failed.
....
any info on what might cause this? and how to prevent these.. restarting the sql service will reset the db but it's a live system that can't be shut down..
it's a clustered system with sql server 2000
LVL 20
Michel SakrAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Brendt HessSenior DBACommented:
Try a DBCC CHECKDB on tempDB and see what it reports.
0
arbertCommented:
ummm, why would you do a CHECKDB against the tempdb?  You should only checkdb a database that isn't in use--tempdb for the most part is always in use.  Shutdown SQL server and restart--it rebuilds the tempdb....

Brett
0
Brendt HessSenior DBACommented:
arbert - read Silvers5 comments -- "...it's a live system that can't be shut down..."  Thus, I recommended the CheckDB as the only option that I could see.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

arbertCommented:
chill I can read, thanks for the check though.  Although books online says that you can run CHECKDB on a "live system" if you are running 2000 (you couldn't do it on 7.0), you still can encounter errors from CHECKDB when they don't exist--it's still not very reliable.

If you are running a cluster, issue a checkpoint, fail your cluster over and restart the node after the failover.

Brett
0
Michel SakrAuthor Commented:
I failed over the cluster.. and restarted the sql service.. it was rebuilt.. now I am facing a problem.. the tempdb is not growing.. even if I try to grow it manually the physical file grows but the db doesn't show the growth.. If I add an extra file it grows.. but the main datafile doesn't..
0
Michel SakrAuthor Commented:
arbert I'll post 250 points for you for the first issue..
0
arbertCommented:
And when you look at properties of tempdb, it definately is setup to auto grow?  is there anything in the SQL Server log?
0
Michel SakrAuthor Commented:
It was a hardware problem.. After upgrading the raid firmware it went ok..
0
PashaModCommented:
Closed, 250 points refunded.
PashaMod
Community Support Moderator
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.