DB Check Error - DB SolarWindsOrion

Hello All,

i hope somebody can help me with my DBCheck Error of the SolarWindsOrion DB.

Detials of my Solarwinds Infrastructure
Solarwinds Product Version: Orion Platform HF3, SRM, IPAM, SAM HF3, NCM HF1, VMAN HF3, NPM HF3, NTA HF2, UDT HF3: 2020.2.6 
OS: Windows Server 2016
SQL: MS SQL 2016 13.0.5081.1 Edition: Standard Edition (64-bit)
SQL Script: DBCHECK running with the local SA Account what have full access to the Database.
DBCHECK Script run following Command: exec spr_ExecDatabaseIntegrityCheck

I hope already open a case by Solarwinds and they told me to ignore the issue, because you don't have jet any impact of your monitoring.
May somebody have any idea how to solve that issue?

Error Message during DBCHECK.

Executed as user: *Company*. ... 13.0.5081.1 Edition: Standard Edition (64-bit) Procedure: [AdminDB].[dbo].[DatabaseIntegrityCheck] Parameters: @Databases = 'ALL_DATABASES', @CheckCommands = 'CHECKDB', @PhysicalOnly = 'N', @NoIndex = 'N', @ExtendedLogicalChecks = 'N', @TabLock = 'N', @FileGroups = NULL, @Objects = NULL, @MaxDOP = NULL, @AvailabilityGroups = NULL, @AvailabilityGroupReplicas = 'SECONDARY', @Updateability = 'ALL', @LockTimeout = NULL, @LogToTable = 'Y', @Execute = 'Y' Source: https://ola.hallengren.com [SQLSTATE 01000] (Message 50000) Date and time: 2022-01-02 13:00:00 Database: [AdminDB] Status: ONLINE Standby: No Updateability: READ_WRITE User access: MULTI_USER Is accessible: Yes Recovery model: FULL [SQLSTATE 01000] (Message 50000) Date and time: 2022-01-02 13:00:00 Command: DBCC CHECKDB ([AdminDB]) WITH NO_INFOMSGS, ALL_ERRORMSGS, DATA_PURITY [SQLSTATE 01000] (Message 50000) Outcome: Succeeded Duration: 00:00:03 Date and time: 2022-01-02 13:00:03 [SQLSTATE 01000] (Message 50000) Date and time: 2022-01-02 13:00:03 Database: [master] Status: ONLINE Standby: No Updateability: READ_WRITE User access: MULTI_USER Is accessible: Yes Recovery model: SIMPLE [SQLSTATE 01000] (Message 50000) Date and time: 2022-01-02 13:00:03 Command: DBCC CHECKDB ([master]) WITH NO_INFOMSGS, ALL_ERRORMSGS, DATA_PURITY [SQLSTATE 01000] (Message 50000) Outcome: Succeeded Duration: 00:00:03 Date and time: 2022-01-02 13:00:06 [SQLSTATE 01000] (Message 50000) Date and time: 2022-01-02 13:00:06 Database: [model] Status: ONLINE Standby: No Updateability: READ_WRITE User access: MULTI_USER Is accessible: Yes Recovery model: FULL [SQLSTATE 01000] (Message 50000) Date and time: 2022-01-02 13:00:06 Command: DBCC CHECKDB ([model]) WITH NO_INFOMSGS, ALL_ERRORMSGS, DATA_PURITY [SQLSTATE 01000] (Message 50000) Outcome: Succeeded Duration: 00:00:01 Date and time: 2022-01-02 13:00:07 [SQLSTATE 01000] (Message 50000) Date and time: 2022-01-02 13:00:07 Database: [msdb] Status: ONLINE Standby: No Updateability: READ_WRITE User access: MULTI_USER Is accessible: Yes Recovery model: SIMPLE [SQLSTATE 01000] (Message 50000) Date and time: 2022-01-02 13:00:07 Command: DBCC CHECKDB ([msdb]) WITH NO_INFOMSGS, ALL_ERRORMSGS, DATA_PURITY [SQLSTATE 01000] (Message 50000) Outcome: Succeeded Duration: 00:00:03 Date and time: 2022-01-02 13:00:10 [SQLSTATE 01000] (Message 50000) Date and time: 2022-01-02 13:00:10 Database: [SolarWindsOrion] Status: ONLINE Standby: No Updateability: READ_WRITE User access: MULTI_USER Is accessible: Yes Recovery model: SIMPLE [SQLSTATE 01000] (Message 50000) Date and time: 2022-01-02 13:00:10 Command: DBCC CHECKDB ([SolarWindsOrion]) WITH NO_INFOMSGS, ALL_ERRORMSGS, DATA_PURITY [SQLSTATE 01000] (Message 50000) Table error: Object ID 299148111, index ID 1, partition ID 72057927228391424, alloc unit ID 72057594050510848 (type LOB data). The off-row data node at page (1:125497), slot 0, text ID 703193562284032 does not match its reference from page (1:5377146), slot 1. [SQLSTATE 42000] (Error 8961) Object ID 299148111, index ID 1, partition ID 72057927228391424, alloc unit ID 72057927413858304 (type In-row data): Errors found in off-row data with ID 140243608862720 owned by data record identified by RID = (1:5377146:1) [SQLSTATE 42000] (Error 8929) Table error: Object ID 1717581157, index ID 1, partition ID 72057948151152640, alloc unit ID 72057594043367424 (type LOB data). The off-row data node at page (1:115932), slot 15, text ID 853606362906624 does not match its reference from page (1:3064465), slot 0. [SQLSTATE 42000] (Error 8961) Table error: Object ID 1717581157, index ID 1, partition ID 72057948151152640, alloc unit ID 72057594043367424 (type LOB data). The off-row data node at page (1:145114), slot 0, text ID 876682188029952 does not match its reference from page (1:2566700), slot 1. [SQLSTATE 42000] (Error 8961) Table error:... The step failed.

Thank you in advances for your help.

Top Replies

  • Hi, this is the interesting part:

    Table error: Object ID 299148111, index ID 1, partition ID 72057927228391424, alloc unit ID 72057594050510848 (type LOB data). The off-row data node at page (1:125497), slot 0, text ID 703193562284032 does not match its reference from page (1:5377146), slot 1. [SQLSTATE 42000] (Error 8961) Object ID 299148111, index ID 1, partition ID 72057927228391424, alloc unit ID 72057927413858304 (type In-row data): Errors found in off-row data with ID 140243608862720 owned by data record identified by RID = (1:5377146:1) [SQLSTATE 42000] (Error 8929) Table error: Object ID 1717581157, index ID 1, partition ID 72057948151152640, alloc unit ID 72057594043367424 (type LOB data). The off-row data node at page (1:115932), slot 15, text ID 853606362906624 does not match its reference from page (1:3064465), slot 0. [SQLSTATE 42000] (Error 8961) Table error: Object ID 1717581157, index ID 1, partition ID 72057948151152640, alloc unit ID 72057594043367424 (type LOB data). The off-row data node at page (1:145114), slot 0, text ID 876682188029952 does not match its reference from page (1:2566700), slot 1. [SQLSTATE 42000] (Error 8961) Table error:... The step failed.

    It tells you that you have corrupt parts in the database. You need a SQL DBA to look closer into that, preferably sooner than later. Might be that you have to restore parts of the database, or the whole database. 

    Also check the disk for corruptions so you don't try to fix the issue on a bad disk.

  • Thank you for your replay Seashore, i will have a deeper look with my SQL DBA.