• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1453
  • Last Modified:

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
0
Michel Sakr
Asked:
Michel Sakr
  • 3
  • 3
  • 2
  • +1
1 Solution
 
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
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
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

Featured Post

Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

  • 3
  • 3
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now