Otdfbt

Notation of last measure of a song with a pickup measure

Payment instructions from HomeAway look fishy to me

What does the "c." listed under weapon length mean?

Average spam confidence

Russian equivalents of "no love lost"

Cause of continuous spectral lines

How did students remember what to practise between lessons without any sheet music?

Smooth switching between 12v batteries, with toggle switch

Avoiding cliches when writing gods

Is it possible to (7 day) schedule sleep time of a hard drive?

What is the advantage of carrying a tripod and ND-filters when you could use image stacking instead?

Was the Tamarian language in "Darmok" inspired by Jack Vance's "The Asutra"?

Do simulator games use a realistic trajectory to get into orbit?

Why does the Schrödinger equation work so well for the Hydrogen atom despite the relativistic boundary at the nucleus?

How would a aircraft visually signal in distress?

What's the right way to purge recursively with apt?

How to generate random points without duplication?

Why is the relationship between frequency and pitch exponential?

Why doesn’t a normal window produce an apparent rainbow?

When conversion from Integer to Single may lose precision

Is any name of Vishnu Siva?

Do the English have an ancient (obsolete) verb for the action of the book opening?

Phone number to a lounge, or lounges generally

Select items in a list that contain criteria #2

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.6k14292465

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.6k14292465

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.6k14292465

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.6k14292465

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.6k14292465

asked May 20 at 11:20

Andrzej BłochAndrzej Błoch

886

edited May 20 at 12:46

Paul White♦

55.6k14292465

edited May 20 at 12:46

Paul White♦

55.6k14292465

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.8k1375120

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.8k1375120

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.8k1375120

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.8k1375120

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.8k1375120

answered May 20 at 16:36

Erik DarlingErik Darling

23.8k1375120

answered May 20 at 16:36

Erik DarlingErik Darling

23.8k1375120