Database page Could not be processed?

Question

Database page Could not be processed?

Viewing 7 posts - 16 through 21 (of 21 total)

You must be logged in to reply to this topic. Login to reply

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 1

I can't see why that is a repair_allow_data_loss for a nonclustered index. Is that the complete, unedited output?

Are you sure you ran the DROP from the correct database? It looks, from the name, like there might be multiple DBs with the same name.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

crazy_new SSCarpal Tunnel Points: 4804 More actions · Answer 2

Hi Gila,

I scripted this DB out and renamed the original one to old..This is where I have dropped the index..I am 100% sure that I ran it against the correct DB. I did not tun a repair on it.

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 3

I didn't say you'd run repair. I said I can't see *why* repair allow data loss is recommended. Is that the exact, complete output from CheckDB with no changes, no edits, nothing left out?

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

crazy_new SSCarpal Tunnel Points: 4804 More actions · Answer 4

I only removed the peoples ID numbers, but nothing else

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 5

Err, what? There are no personal ID numbers in a checkDB output, just page numbers, allocation units, partition IDs, table IDs.

Please paste the entire thing without any editing.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

crazy_new SSCarpal Tunnel Points: 4804 More actions · Answer 6

LOL sorry, I didn't read properly and it looked like ID numbers.

Msg 8928, Level 16, State 1, Line 1

Object ID 53575229, index ID 9, partition ID 72057594110935040, alloc unit ID 72057594121158656 (type In-row data): Page (1:1400911) could not be processed. See other errors for details.

Msg 8939, Level 16, State 98, Line 1

Table error: Object ID 53575229, index ID 9, partition ID 72057594110935040, alloc unit ID 72057594121158656 (type In-row data), page (1:1400911). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 63047689 and -4.

Msg 8976, Level 16, State 1, Line 1

Table error: Object ID 53575229, index ID 9, partition ID 72057594110935040, alloc unit ID 72057594121158656 (type In-row data). Page (1:1400911) was not seen in the scan although its parent (1:688650) and previous (1:1400910) refer to it. Check any previous errors.

Msg 8978, Level 16, State 1, Line 1

Table error: Object ID 53575229, index ID 9, partition ID 72057594110935040, alloc unit ID 72057594121158656 (type In-row data). Page (1:1400912) is missing a reference from previous page (1:1400911). Possible chain linkage problem.

Msg 8928, Level 16, State 1, Line 1

Object ID 53575229, index ID 9, partition ID 72057594110935040, alloc unit ID 72057594121158656 (type In-row data): Page (1:1401483) could not be processed. See other errors for details.

Msg 8939, Level 16, State 98, Line 1

Table error: Object ID 53575229, index ID 9, partition ID 72057594110935040, alloc unit ID 72057594121158656 (type In-row data), page (1:1401483). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 63047689 and -4.

Msg 8976, Level 16, State 1, Line 1

Table error: Object ID 53575229, index ID 9, partition ID 72057594110935040, alloc unit ID 72057594121158656 (type In-row data). Page (1:1401483) was not seen in the scan although its parent (1:660528) and previous (1:1401482) refer to it. Check any previous errors.

Msg 8978, Level 16, State 1, Line 1

Table error: Object ID 53575229, index ID 9, partition ID 72057594110935040, alloc unit ID 72057594121158656 (type In-row data). Page (1:1401484) is missing a reference from previous page (1:1401483). Possible chain linkage problem.

CHECKDB found 0 allocation errors and 8 consistency errors in table 'ep_ACTION_track_Archive_20150819' (object ID 53575229).

CHECKDB found 0 allocation errors and 8 consistency errors in database 'epTracking_dbOld'.

repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (epTracking_dbOld).

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 7

Please post exact results of:

USE epTracking_dbOld

GO

SELECT i.object_id, i.name, i.index_id, i.type, i.is_unique, i.is_hypothetical, i.is_disabled, i.has_filter FROM sys.indexes AS i

WHERE i.object_id = 53575229 AND i.index_id = 9

SELECT ps.partition_id, ps.object_id, ps.index_id, ps.partition_number, ps.row_count FROM sys.dm_db_partition_stats AS ps

WHERE ps.object_id = 53575229 AND ps.index_id = 9

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass