Ttdfjt

Plot twist where the antagonist wins

Why colon to denote that a value belongs to a type?

Why did David Cameron offer a referendum on the European Union?

Why are C64 games inconsistent with which joystick port they use?

Crossing US border with music files I'm legally allowed to possess

Should I disclose a colleague's illness (that I should not know) when others badmouth him

Is it possible to play as a necromancer skeleton?

Can I install both XCode & Android Studio on MacBook Air with only 8 GB of Ram

Is there a way to make it so the cursor is included when I prtscr key?

Should one buy new hardware after a system compromise?

Why aren't space telescopes put in GEO?

Does Nitrogen inside commercial airliner wheels prevent blowouts on touchdown?

Where is the logic in castrating fighters?

Have 1.5% of all nuclear reactors ever built melted down?

How to use " shadow " in pstricks?

What does the view outside my ship traveling at light speed look like?

A steel cutting sword?

Is it rude to call a professor by their last name with no prefix in a non-academic setting?

How strong are Wi-Fi signals?

Construct a word ladder

Image processing: Removal of two spots in fundus images

Why doesn't the Earth accelerate towards the Moon?

Why were helmets and other body armour not commonplace in the 1800s?

Did people go back to where they were?

Physical only checkdb is failing, but full one is completed successfully

Found errors in table after executing DBCC CHECKTABLE commandDBCC CHECKDB Results: page ID contains an incorrect page ID in its page headerCorrupt DB for a noobdatabase corruptionDBCC InconsistencyError in table 'sys.sysbinobjs' on master databaseHow to fix errors reported by DBCC CHECKDBMy database got in to suspect mode, I repaired it using dbcc, but I want to know causeMS SQL DBCC CHECKDB page ID (1:xxx) contains an incorrect page IDGetting error running DBCC Checktable(tablename, repair_allow_data_loss)

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;

13

I am executing checkdb with physical_only option and it fails with multiple errors like below:

Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 1557580587,
index ID 1, partition ID 72057594088456192, alloc unit ID
72057594177454080 (type In-row data). The off-row data node at page
(1:13282192), slot 3, text ID 6370769698816 is referenced by page
(0:0), slot 0, but was not seen in the scan.
Msg 8965, Level 16, State
1, Line 1
Table error: Object ID 1557580587, index ID 1, partition ID
72057594088456192, alloc unit ID 72057594177454080 (type In-row data).
The off-row data node at page (1:13282192), slot 5, text ID
6370769764352 is referenced by page (0:0), slot 0, but was not seen in
the scan.
CHECKDB found 0 allocation errors and 5255 consistency
errors in table 'TableX' (object ID
1557580587).
CHECKDB found 0 allocation errors and 5255 consistency
errors in database 'DatabaseX'. repair_allow_data_loss is the minimum
repair level for the errors found by DBCC CHECKDB (DWH_LAND).

However full checkdb is successfull:

CHECKDB found 0 allocation errors and 0 consistency errors in database
'DatabaseX'. DBCC execution completed. If DBCC printed error messages,
contact your system administrator.

TableX has around 200 000 rows and has clustered columnstore index on it.

We are using following version of SQL Server:

Microsoft SQL Server 2017 (RTM-CU13) (KB4466404) - 14.0.3048.4


Should I be worried?

sql-server sql-server-2017 dbcc-checkdb

share|improve this question

edited May 20 at 12:46

Paul White♦

55.2k14291463

asked May 20 at 11:20

Andrzej BłochAndrzej Błoch

886

add a comment | 

13

I am executing checkdb with physical_only option and it fails with multiple errors like below:

Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 1557580587,
index ID 1, partition ID 72057594088456192, alloc unit ID
72057594177454080 (type In-row data). The off-row data node at page
(1:13282192), slot 3, text ID 6370769698816 is referenced by page
(0:0), slot 0, but was not seen in the scan.
Msg 8965, Level 16, State
1, Line 1
Table error: Object ID 1557580587, index ID 1, partition ID
72057594088456192, alloc unit ID 72057594177454080 (type In-row data).
The off-row data node at page (1:13282192), slot 5, text ID
6370769764352 is referenced by page (0:0), slot 0, but was not seen in
the scan.
CHECKDB found 0 allocation errors and 5255 consistency
errors in table 'TableX' (object ID
1557580587).
CHECKDB found 0 allocation errors and 5255 consistency
errors in database 'DatabaseX'. repair_allow_data_loss is the minimum
repair level for the errors found by DBCC CHECKDB (DWH_LAND).

However full checkdb is successfull:

CHECKDB found 0 allocation errors and 0 consistency errors in database
'DatabaseX'. DBCC execution completed. If DBCC printed error messages,
contact your system administrator.

TableX has around 200 000 rows and has clustered columnstore index on it.

We are using following version of SQL Server:

Microsoft SQL Server 2017 (RTM-CU13) (KB4466404) - 14.0.3048.4


Should I be worried?

sql-server sql-server-2017 dbcc-checkdb

share|improve this question

edited May 20 at 12:46

Paul White♦

55.2k14291463

asked May 20 at 11:20

Andrzej BłochAndrzej Błoch

886

add a comment | 

I am executing checkdb with physical_only option and it fails with multiple errors like below:

Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 1557580587,
index ID 1, partition ID 72057594088456192, alloc unit ID
72057594177454080 (type In-row data). The off-row data node at page
(1:13282192), slot 3, text ID 6370769698816 is referenced by page
(0:0), slot 0, but was not seen in the scan.
Msg 8965, Level 16, State
1, Line 1
Table error: Object ID 1557580587, index ID 1, partition ID
72057594088456192, alloc unit ID 72057594177454080 (type In-row data).
The off-row data node at page (1:13282192), slot 5, text ID
6370769764352 is referenced by page (0:0), slot 0, but was not seen in
the scan.
CHECKDB found 0 allocation errors and 5255 consistency
errors in table 'TableX' (object ID
1557580587).
CHECKDB found 0 allocation errors and 5255 consistency
errors in database 'DatabaseX'. repair_allow_data_loss is the minimum
repair level for the errors found by DBCC CHECKDB (DWH_LAND).

However full checkdb is successfull:

CHECKDB found 0 allocation errors and 0 consistency errors in database
'DatabaseX'. DBCC execution completed. If DBCC printed error messages,
contact your system administrator.

TableX has around 200 000 rows and has clustered columnstore index on it.

We are using following version of SQL Server:

Microsoft SQL Server 2017 (RTM-CU13) (KB4466404) - 14.0.3048.4


Should I be worried?

sql-server sql-server-2017 dbcc-checkdb

share|improve this question

edited May 20 at 12:46

Paul White♦

55.2k14291463

asked May 20 at 11:20

Andrzej BłochAndrzej Błoch

886

share|improve this question

edited May 20 at 12:46

Paul White♦

55.2k14291463

asked May 20 at 11:20

Andrzej BłochAndrzej Błoch

886

share|improve this question

edited May 20 at 12:46

Paul White♦

55.2k14291463

asked May 20 at 11:20

Andrzej BłochAndrzej Błoch

886

edited May 20 at 12:46

Paul White♦

55.2k14291463

edited May 20 at 12:46

Paul White♦

55.2k14291463

asked May 20 at 11:20

Andrzej BłochAndrzej Błoch

886

asked May 20 at 11:20

Andrzej BłochAndrzej Błoch

886

1 Answer
1

active

oldest

votes

13

Yes, this a defect in SQL Server 2017 up to CU14. There was a similar issue with nonclustered columnstore indexes in SQL Server 2016.

It's detailed in this video: CHECKDB Bug With SQL Server 2017 And ColumnStore Indexes

A more portable repro of the issue is this:

SELECT *, CONVERT(NVARCHAR(MAX), m.text + m.text + m.text + m.text + m.text) AS texty
INTO dbo.corrupt
FROM sys.messages AS m;

CREATE CLUSTERED COLUMNSTORE INDEX cx_corrupt ON dbo.corrupt;

DBCC CHECKDB WITH PHYSICAL_ONLY;

DROP TABLE dbo.corrupt;

share|improve this answer

answered May 20 at 16:36

Erik DarlingErik Darling

23.6k1374118

add a comment | 

Your Answer

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "182"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f238567%2fphysical-only-checkdb-is-failing-but-full-one-is-completed-successfully%23new-answer', 'question_page');

);

Post as a guest

Name

Email

Required, but never shown

13

Yes, this a defect in SQL Server 2017 up to CU14. There was a similar issue with nonclustered columnstore indexes in SQL Server 2016.

It's detailed in this video: CHECKDB Bug With SQL Server 2017 And ColumnStore Indexes

A more portable repro of the issue is this:

SELECT *, CONVERT(NVARCHAR(MAX), m.text + m.text + m.text + m.text + m.text) AS texty
INTO dbo.corrupt
FROM sys.messages AS m;

CREATE CLUSTERED COLUMNSTORE INDEX cx_corrupt ON dbo.corrupt;

DBCC CHECKDB WITH PHYSICAL_ONLY;

DROP TABLE dbo.corrupt;

share|improve this answer

answered May 20 at 16:36

Erik DarlingErik Darling

23.6k1374118

add a comment | 

13

Yes, this a defect in SQL Server 2017 up to CU14. There was a similar issue with nonclustered columnstore indexes in SQL Server 2016.

It's detailed in this video: CHECKDB Bug With SQL Server 2017 And ColumnStore Indexes

A more portable repro of the issue is this:

SELECT *, CONVERT(NVARCHAR(MAX), m.text + m.text + m.text + m.text + m.text) AS texty
INTO dbo.corrupt
FROM sys.messages AS m;

CREATE CLUSTERED COLUMNSTORE INDEX cx_corrupt ON dbo.corrupt;

DBCC CHECKDB WITH PHYSICAL_ONLY;

DROP TABLE dbo.corrupt;

share|improve this answer

answered May 20 at 16:36

Erik DarlingErik Darling

23.6k1374118

add a comment | 

Yes, this a defect in SQL Server 2017 up to CU14. There was a similar issue with nonclustered columnstore indexes in SQL Server 2016.

It's detailed in this video: CHECKDB Bug With SQL Server 2017 And ColumnStore Indexes

A more portable repro of the issue is this:

SELECT *, CONVERT(NVARCHAR(MAX), m.text + m.text + m.text + m.text + m.text) AS texty
INTO dbo.corrupt
FROM sys.messages AS m;

CREATE CLUSTERED COLUMNSTORE INDEX cx_corrupt ON dbo.corrupt;

DBCC CHECKDB WITH PHYSICAL_ONLY;

DROP TABLE dbo.corrupt;

share|improve this answer

answered May 20 at 16:36

Erik DarlingErik Darling

23.6k1374118

SELECT *, CONVERT(NVARCHAR(MAX), m.text + m.text + m.text + m.text + m.text) AS texty
INTO dbo.corrupt
FROM sys.messages AS m;

CREATE CLUSTERED COLUMNSTORE INDEX cx_corrupt ON dbo.corrupt;

DBCC CHECKDB WITH PHYSICAL_ONLY;

DROP TABLE dbo.corrupt;

share|improve this answer

answered May 20 at 16:36

Erik DarlingErik Darling

23.6k1374118

answered May 20 at 16:36

Erik DarlingErik Darling

23.6k1374118

answered May 20 at 16:36

Erik DarlingErik Darling

23.6k1374118