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
 General SQL Server Forums
 Data Corruption Issues
 checkdb errors

Author  Topic 

albertkohl
Aged Yak Warrior

740 Posts
Posted - 2011-03-03 : 00:33:07
select * from table =

Msg 605, Level 21, State 3, Line 1
Attempt to fetch logical page (1:13544296) in database 19 failed. It belongs to allocation unit 72057595663810560 not to 72057595525988352.

dbcc checkdb =

Msg 2533, Level 16, State 1, Line 1
Table error: page (1:13544296) allocated to object ID 919114465, index ID 0, partition ID 72057594718846976, alloc unit ID 72057595525988352 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.

so my question is, is there any way for me to get the data out of the table? or am i burnt? (or atleast what's still good)

also, can i run: repair_allow_data_loss on JUST the table?

Thanks!

GilaMonster
Master Smack Fu Yak Hacker

4507 Posts
Posted - 2011-03-03 : 02:01:41
Do you have a clean backup?

Please run the following and post the full and complete output. Do nothing else at this point.
DBCC CheckDB(<Database name>) WITH No_INFOMSGS, ALL_ERRORMSGS



--
Gail Shaw
SQL Server MVP
Go to Top of Page

albertkohl
Aged Yak Warrior

740 Posts
Posted - 2011-03-03 : 08:21:26
no i dont have a clean backup, this database is fairly disposable, this is probably the only item in it i give two craps about. if i have to scrap this table entirely as well, so be it, but if i can just get rid of the bad pages, i'd prefer to do so.


Msg 2533, Level 16, State 1, Line 1
Table error: page (1:13544296) allocated to object ID 919114465, index ID 0, partition ID 72057594718846976, alloc unit ID 72057595525988352 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:13544297) allocated to object ID 919114465, index ID 0, partition ID 72057594718846976, alloc unit ID 72057595525988352 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:13544298) allocated to object ID 919114465, index ID 0, partition ID 72057594718846976, alloc unit ID 72057595525988352 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:13544299) allocated to object ID 919114465, index ID 0, partition ID 72057594718846976, alloc unit ID 72057595525988352 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:13544300) allocated to object ID 919114465, index ID 0, partition ID 72057594718846976, alloc unit ID 72057595525988352 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:13544301) allocated to object ID 919114465, index ID 0, partition ID 72057594718846976, alloc unit ID 72057595525988352 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:13544302) allocated to object ID 919114465, index ID 0, partition ID 72057594718846976, alloc unit ID 72057595525988352 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:13544303) allocated to object ID 919114465, index ID 0, partition ID 72057594718846976, alloc unit ID 72057595525988352 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:13544304) allocated to object ID 919114465, index ID 0, partition ID 72057594718846976, alloc unit ID 72057595525988352 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:13544305) allocated to object ID 919114465, index ID 0, partition ID 72057594718846976, alloc unit ID 72057595525988352 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:13544306) allocated to object ID 919114465, index ID 0, partition ID 72057594718846976, alloc unit ID 72057595525988352 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:13544307) allocated to object ID 919114465, index ID 0, partition ID 72057594718846976, alloc unit ID 72057595525988352 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:13544308) allocated to object ID 919114465, index ID 0, partition ID 72057594718846976, alloc unit ID 72057595525988352 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:13544309) allocated to object ID 919114465, index ID 0, partition ID 72057594718846976, alloc unit ID 72057595525988352 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:13544310) allocated to object ID 919114465, index ID 0, partition ID 72057594718846976, alloc unit ID 72057595525988352 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:13544311) allocated to object ID 919114465, index ID 0, partition ID 72057594718846976, alloc unit ID 72057595525988352 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:15339672) allocated to object ID 919114465, index ID 0, partition ID 72057594718846976, alloc unit ID 72057595525988352 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:15339673) allocated to object ID 919114465, index ID 0, partition ID 72057594718846976, alloc unit ID 72057595525988352 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:15339674) allocated to object ID 919114465, index ID 0, partition ID 72057594718846976, alloc unit ID 72057595525988352 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:15339675) allocated to object ID 919114465, index ID 0, partition ID 72057594718846976, alloc unit ID 72057595525988352 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:15339676) allocated to object ID 919114465, index ID 0, partition ID 72057594718846976, alloc unit ID 72057595525988352 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:15339677) allocated to object ID 919114465, index ID 0, partition ID 72057594718846976, alloc unit ID 72057595525988352 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:15339678) allocated to object ID 919114465, index ID 0, partition ID 72057594718846976, alloc unit ID 72057595525988352 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:15339679) allocated to object ID 919114465, index ID 0, partition ID 72057594718846976, alloc unit ID 72057595525988352 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:15831496) allocated to object ID 919114465, index ID 0, partition ID 72057594718846976, alloc unit ID 72057595525988352 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:15831497) allocated to object ID 919114465, index ID 0, partition ID 72057594718846976, alloc unit ID 72057595525988352 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:15831498) allocated to object ID 919114465, index ID 0, partition ID 72057594718846976, alloc unit ID 72057595525988352 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:15831499) allocated to object ID 919114465, index ID 0, partition ID 72057594718846976, alloc unit ID 72057595525988352 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:15831500) allocated to object ID 919114465, index ID 0, partition ID 72057594718846976, alloc unit ID 72057595525988352 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:15831501) allocated to object ID 919114465, index ID 0, partition ID 72057594718846976, alloc unit ID 72057595525988352 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:15831502) allocated to object ID 919114465, index ID 0, partition ID 72057594718846976, alloc unit ID 72057595525988352 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:15831503) allocated to object ID 919114465, index ID 0, partition ID 72057594718846976, alloc unit ID 72057595525988352 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:15831504) allocated to object ID 919114465, index ID 0, partition ID 72057594718846976, alloc unit ID 72057595525988352 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:15831505) allocated to object ID 919114465, index ID 0, partition ID 72057594718846976, alloc unit ID 72057595525988352 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:15831506) allocated to object ID 919114465, index ID 0, partition ID 72057594718846976, alloc unit ID 72057595525988352 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:15831507) allocated to object ID 919114465, index ID 0, partition ID 72057594718846976, alloc unit ID 72057595525988352 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:15831508) allocated to object ID 919114465, index ID 0, partition ID 72057594718846976, alloc unit ID 72057595525988352 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:15831509) allocated to object ID 919114465, index ID 0, partition ID 72057594718846976, alloc unit ID 72057595525988352 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:15831510) allocated to object ID 919114465, index ID 0, partition ID 72057594718846976, alloc unit ID 72057595525988352 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:15831511) allocated to object ID 919114465, index ID 0, partition ID 72057594718846976, alloc unit ID 72057595525988352 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
CHECKDB found 0 allocation errors and 40 consistency errors in table 'Net.joecav' (object ID 919114465).
CHECKDB found 0 allocation errors and 430 consistency errors in database 'MAIN'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (MAIN).
Go to Top of Page

GilaMonster
Master Smack Fu Yak Hacker

4507 Posts
Posted - 2011-03-03 : 10:08:35
Are you sure that's the complete output? End message says 430 errors, but there are not 430 errors listed there.

--
Gail Shaw
SQL Server MVP
Go to Top of Page

albertkohl
Aged Yak Warrior

740 Posts
Posted - 2011-03-03 : 10:49:45
that's the whole sha-bang. there were just as many errors when i ran it before, but they were off indexes on some tables. i dropped the index, and stopped getting errors on it.

maybe it's omitting them because the object no longer exists?
Go to Top of Page

GilaMonster
Master Smack Fu Yak Hacker

4507 Posts
Posted - 2011-03-04 : 03:28:58
It's repairable, but by the looks of things you'll lose a lot of data in that table.

Take the DB into single user mode and run
DBCC CheckDB(<database name>, REPAIR_ALLOW_DATA_LOSS)

Run another checkDB (without repair) afterwards to be sure everything bad has gone.

--
Gail Shaw
SQL Server MVP
Go to Top of Page

albertkohl
Aged Yak Warrior

740 Posts
Posted - 2011-03-04 : 12:23:58
worked perfectly, thanks...

so last thing, what do i do, when this crap happens:

dbcc checkdb (mydb) with no_infomsgs,all_errormsgs
Msg 0, Level 11, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.


i think i have a failing drive :(
Go to Top of Page

jeffw8713
Aged Yak Warrior

819 Posts
Posted - 2011-03-04 : 17:41:23
quote:
worked perfectly, thanks...

so last thing, what do i do, when this crap happens:

dbcc checkdb (mydb) with no_infomsgs,all_errormsgs
Msg 0, Level 11, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.


i think i have a failing drive :(


Hope you have a good backup to restore from. I know you don't have one, but that is the best way to recover from corruption. With the above error, and no backups - there really isn't anything you can do.

Jeff
Go to Top of Page

GilaMonster
Master Smack Fu Yak Hacker

4507 Posts
Posted - 2011-03-04 : 19:30:00
quote:
Originally posted by albertkohl

so last thing, what do i do, when this crap happens:

dbcc checkdb (mydb) with no_infomsgs,all_errormsgs
Msg 0, Level 11, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.


run diagnostics on the IO subsystem and restore from last good backup

--
Gail Shaw
SQL Server MVP
Go to Top of Page

albertkohl
Aged Yak Warrior

740 Posts
Posted - 2011-03-05 : 12:47:21
any recommendation on tools for the diag?
Go to Top of Page

GilaMonster
Master Smack Fu Yak Hacker

4507 Posts
Posted - 2011-03-05 : 14:46:10
No. totally depends on what you have as an IO subsystem. Consult with your hardware/storage vendors

--
Gail Shaw
SQL Server MVP
Go to Top of Page
   

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources

Articles

Forums

Blogs

Contact Us

About the Site