Errors in tempdb???? 3

[Will192]

I ran the following command:

DBCC CHECKDB(tempdb)

and got the following output:

Msg 8999, Sev 16: Database tempdb allocation errors prevent further CHECKDB processing. [SQLSTATE 42000]
Msg 8905, Sev 16: Extent (3:497504) in database ID 2 is marked allocated in the GAM, but no SGAM or IAM has allocated it. [SQLSTATE 42000]
Msg 8905, Sev 16: Extent (3:510640) in database ID 2 is marked allocated in the GAM, but no SGAM or IAM has allocated it. [SQLSTATE 42000]
Msg 8905, Sev 16: Extent (3:510648) in database ID 2 is marked allocated in the GAM, but no SGAM or IAM has allocated it. [SQLSTATE 42000]
Msg 8905, Sev 16: Extent (3:510656) in database ID 2 is marked allocated in the GAM, but no SGAM or IAM has allocated it. [SQLSTATE 42000]
Msg 8905, Sev 16: Extent (3:510664) in database ID 2 is marked allocated in the GAM, but no SGAM or IAM has allocated it. [SQLSTATE 42000]
Msg 8905, Sev 16: Extent (3:510672) in database ID 2 is marked allocated in the GAM, but no SGAM or IAM has allocated it. [SQLSTATE 42000]
Msg 8905, Sev 16: Extent (3:510680) in database ID 2 is marked allocated in the GAM, but no SGAM or IAM has allocated it. [SQLSTATE 42000]
Msg 8905, Sev 16: Extent (3:510688) in database ID 2 is marked allocated in the GAM, but no SGAM or IAM has allocated it. [SQLSTATE 42000]
Msg 8905, Sev 16: Extent (3:510696) in database ID 2 is marked allocated in the GAM, but no SGAM or IAM has allocated it. [SQLSTATE 42000]
Msg 8905, Sev 16: Extent (3:510704) in database ID 2 is marked allocated in the GAM, but no SGAM or IAM has allocated it. [SQLSTATE 42000]
Msg 8905, Sev 16: Extent (3:510720) in database ID 2 is marked allocated in the GAM, but no SGAM or IAM has allocated it. [SQLSTATE 42000]
Msg 8905, Sev 16: Extent (3:510728) in database ID 2 is marked allocated in the GAM, but no SGAM or IAM has allocated it. [SQLSTATE 42000]
Msg 8905, Sev 16: Extent (3:510736) in database ID 2 is marked allocated in the GAM, but no SGAM or IAM has allocated it. [SQLSTATE 42000]
Msg 8905, Sev 16: Extent (3:510752) in database ID 2 is marked allocated in the GAM, but no SGAM or IAM has allocated it. [SQLSTATE 42000]
Msg 8905, Sev 16: Extent (3:510776) in database ID 2 is marked allocated in the GAM, but no SGAM or IAM has allocated it. [SQLSTATE 42000]
Msg 8905, Sev 16: Extent (3:510800) in database ID 2 is marked allocated in the GAM, but no SGAM or IAM has allocated it. [SQLSTATE 42000]
Msg 8905, Sev 16: Extent (3:510824) in database ID 2 is marked allocated in the GAM, but no SGAM or IAM has allocated it. [SQLSTATE 42000]
Msg 8905, Sev 16: Extent (3:510848) in database ID 2 is marked allocated in the GAM, but no SGAM or IAM has allocated it. [SQLSTATE 42000]
Msg 8905, Sev 16: Extent (3:510872) in database ID 2 is marked allocated in the GAM, but no SGAM or IAM has allocated it. [SQLSTATE 42000]
Msg 2536, Sev 16: DBCC results for 'tempdb'. [SQLSTATE 01000]
Msg 8954, Sev 16: CHECKDB found 19 allocation errors and 0 consistency errors not associated with any single object. [SQLSTATE 01000]
CHECKDB found 19 allocation errors and 0 consistency errors in database 'tempdb'. [SQLSTATE 01000]
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (tempdb ). [SQLSTATE 01000]
DBCC execution completed. If DBCC printed error messages, contact your system administrator. [SQLSTATE 01000]


I am going to run the following command tonight:

DBCC CHECKDB(tempdb, REPAIR_REBUILD)

Is this going to fix the problem?

Thanks in advance for any responses to this post.

Will Summers

 

[ccuster]

When you restart the SQL Server the Model Database overwrites the Tempdb. This may help.

 

[Will192]

I know that the tempdb is rebuilt every time that SQL Server is restarted. I cannot reboot the server till this weekend. I was just looking for a quick fix till then.

Thanks for your response

Will Summers

 

[SQLBill]

Have you ever tried this (DBCC CHECKDB(tempdb) before? I'm thinking that since the command DBCC CHECKDB makes use of the tempdb while it (the command) is running, it may not work on the tempdb.

-SQLBill

 

[SQLBill]

I just read the BOL, DBCC CHECKDB and it appears that the command puts a lock on the database/table that it is checking
"In SQL Server 2000, DBCC CHECKDB holds a schema lock on the table to prevent meta data changes while the table is being checked, "

and needs to use the tempdb.
"DBCC CHECKDB uses tempdb to do sorting."

I don't think it can lock the tempdb when it needs it to do the sorting and other functions of DBCC CHECKDB.

BTW: the quoted parts are from the BOL.

-SQLBill

 

[tlbroadbent]

Microsoft says, "You may see the 8905 error occur if you run CHECKDB on the tempdb database while there is activity on the system, which is not indicative of a problem."

There is a known bug that will give that error. See the the following knowledgebase article.
[ignore]

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q262019

[/ignore]

FYI: We don't run DBCC on tempdb. There is usually no reason to run it because most of the time DBCC CHECKDB will return meaningless errors. Terry L. Broadbent - DBA
Computing Links:

http://tlbroadbent.home.attbi.com/prog.htm

faq183-874 contains "Suggestions for Getting Quick and Appropriate Answers" to your questions.

 

[Will192]

Thank you all for your replies.

I kinda figured that the errors were meanless. I knew in 6.5 some DBCC errors were meanless if there was activity on the system.

Thanks for all of your responses.

Will Summers