Physical only checkdb is failing, but full one is completed successfully
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
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
edited May 20 at 12:46
Paul White♦
58.2k16 gold badges306 silver badges480 bronze badges
asked May 20 at 11:20
Andrzej BłochAndrzej Błoch
886 bronze badges
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
edited May 20 at 12:46
Paul White♦
58.2k16 gold badges306 silver badges480 bronze badges
asked May 20 at 11:20
Andrzej BłochAndrzej Błoch
886 bronze badges
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
edited May 20 at 12:46
Paul White♦
58.2k16 gold badges306 silver badges480 bronze badges
asked May 20 at 11:20
Andrzej BłochAndrzej Błoch
886 bronze badges
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
sql-server sql-server-2017 dbcc-checkdb
edited May 20 at 12:46
Paul White♦
58.2k16 gold badges306 silver badges480 bronze badges
asked May 20 at 11:20
Andrzej BłochAndrzej Błoch
886 bronze badges
edited May 20 at 12:46
Paul White♦
58.2k16 gold badges306 silver badges480 bronze badges
asked May 20 at 11:20
Andrzej BłochAndrzej Błoch
886 bronze badges
edited May 20 at 12:46
Paul White♦
58.2k16 gold badges306 silver badges480 bronze badges
edited May 20 at 12:46
Paul White♦
58.2k16 gold badges306 silver badges480 bronze badges
edited May 20 at 12:46
Paul White♦
58.2k16 gold badges306 silver badges480 bronze badges
58.2k16 gold badges306 silver badges480 bronze badges
asked May 20 at 11:20
Andrzej BłochAndrzej Błoch
886 bronze badges
asked May 20 at 11:20
Andrzej BłochAndrzej Błoch
886 bronze badges
asked May 20 at 11:20
Andrzej BłochAndrzej Błoch
886 bronze badges
886 bronze badges
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
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;
answered May 20 at 16:36
Erik DarlingErik Darling
26k13 gold badges79 silver badges128 bronze badges
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
});
}
});
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
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
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
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;
answered May 20 at 16:36
Erik DarlingErik Darling
26k13 gold badges79 silver badges128 bronze badges
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;
answered May 20 at 16:36
Erik DarlingErik Darling
26k13 gold badges79 silver badges128 bronze badges
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;
answered May 20 at 16:36
Erik DarlingErik Darling
26k13 gold badges79 silver badges128 bronze badges
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;
answered May 20 at 16:36
Erik DarlingErik Darling
26k13 gold badges79 silver badges128 bronze badges
answered May 20 at 16:36
Erik DarlingErik Darling
26k13 gold badges79 silver badges128 bronze badges
answered May 20 at 16:36
Erik DarlingErik Darling
26k13 gold badges79 silver badges128 bronze badges
answered May 20 at 16:36
Erik DarlingErik Darling
26k13 gold badges79 silver badges128 bronze badges
26k13 gold badges79 silver badges128 bronze badges
add a comment |
add a comment |
Thanks for contributing an answer to Database Administrators Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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
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
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
