Msg 5244: Repair statement not processed

Question

Msg 5244: Repair statement not processed

SQL_ME_RICH

SSChampion

Points: 11200
More actions
June 24, 2015 at 9:40 pm

#318504

A few databases in one of my company's instances got whacked with allocation and consistency errors.
So - now I am trying to run DBCC CHECKDB (with REPAIR_REBUILD, or even REPAIR_ALLOW_DATA_LOSS) to do what I can...so I run the following...
USE <Database Name>
GO
ALTER DATABASE <Database Name> SET SINGLE_USER
GO
DBCC CHECKDB('<Database Name>', REPAIR_REBUILD)
GO
ALTER DATABASE <Database Name> SET MULTI_USER
GO
But I get the following error...
Msg 5244, Level 16, State 1, Line 1
Repair statement not processed. One or more files in the database are read-only and must be made writeable in order to run repair.
Happens whether I step through or run the commands together. I can assure you that none of the Filegroups in the database are read only, nor is the database itself. Additionally - I do not have a recent backup to go to (long story so please do not ask).
Any insight on this would be appreciated.
June 25, 2015 at 4:18 am

This was removed by the editor as SPAM
June 25, 2015 at 10:35 pm

This was removed by the editor as SPAM

Viewing 8 posts - 1 through 7 (of 7 total)

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

JManuelN SSCommitted Points: 1708 More actions · Answer 1

Hi,

Did you perform a DBCC CHECK CATALOG or CHECKTABLE on the affected databases? Did those command return any other details?

https://msdn.microsoft.com/en-us/library/ms186720.aspx

I hope this helps.

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

Please run the following and post the full and unedited output. Not all corruptions are repairable.

DBCC CheckDB ('<Database name>') WITH NO_INFOMSGS, ALL_ERRORMSGS

Also can you run:

SELECT name, df.state_desc, df.is_read_only FROM sys.database_files AS df

in the affected database?

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

SQL_ME_RICH SSChampion Points: 11200 More actions · Answer 3

As a sort of group answer - here is the output to 2 of the databases that got whacked:

DBCC CHECKTABLE

I did run this previously (to see if I couldn't run REPARIR_REBUILD that way against a single table), but it gave me the same sort of error message as with CHECKDB.

DBCC CHECKCATALOG ***Syntax*** DBCC CHECKCATALOG (<Database Name>)

Database 1

DBCC execution completed. If DBCC printed error messages, contact your system administrator.

Database 2

DBCC execution completed. If DBCC printed error messages, contact your system administrator.

READ ONLY VERIFICATION ***Syntax*** SELECT name, df.state_desc, df.is_read_only FROM sys.database_files AS df

Database 1

namestate_descis_read_only

Cache_HUMONLINE0

Cache_HUM_logONLINE0

CoreData_01ONLINE0

CoreIndex_01ONLINE0

EtlData_01ONLINE0

EtlIndex_01ONLINE0

Database 2

namestate_descis_read_only

EDW_ShoreTelONLINE0

EDW_ShoreTel_logONLINE0

CoreData_01ONLINE0

CoreIndex_01ONLINE0

EtlData_01ONLINE0

EtlIndex_01ONLINE0

DBCC CHECKDB ***Syntax*** DBCC CHECKDB ('<Database Name>') WITH NO_INFOMSGS, ALL_ERRORMSGS

Database 1

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:41) in object ID 0, index ID -1, partition ID 0, alloc unit ID 72057594274709504 (type Unknown), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:819) in object ID 0, index ID -1, partition ID 0, alloc unit ID 72057594274381824 (type Unknown), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:10164) in object ID 0, index ID -1, partition ID 0, alloc unit ID 72057594274578432 (type Unknown), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:22232) in object ID 0, index ID -1, partition ID 0, alloc unit ID 72057594274447360 (type Unknown), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:20) in object ID 0, index ID -1, partition ID 0, alloc unit ID 72057594274512896 (type Unknown), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:5801) in object ID 0, index ID -1, partition ID 0, alloc unit ID 72057594274643968 (type Unknown), but it was not detected in the scan.

CHECKDB found 6 allocation errors and 0 consistency errors not associated with any single object.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:51) in object ID 14623095, index ID 0, partition ID 72057594105102336, alloc unit ID 72057594215268352 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:171) is pointed to by the next pointer of IAM page (0:0) in object ID 14623095, index ID 0, partition ID 72057594105102336, alloc unit ID 72057594215268352 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:322) is pointed to by the next pointer of IAM page (0:0) in object ID 14623095, index ID 2, partition ID 72057594105233408, alloc unit ID 72057594215530496 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:1107) in object ID 14623095, index ID 2, partition ID 72057594105233408, alloc unit ID 72057594215530496 (type In-row data), but it was not detected in the scan.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 14623095, index ID 0, partition ID 72057594105102336, alloc unit ID 72057594215268352 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:322) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 14623095, index ID 2, partition ID 72057594105233408, alloc unit ID 72057594215530496 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 4 allocation errors and 3 consistency errors in table 'HUM_ETL.GHIS_Regimen_Table_b_RegimenHistory' (object ID 14623095).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:1213) in object ID 30623152, index ID 0, partition ID 72057594105430016, alloc unit ID 72057594215596032 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:1221) is pointed to by the next pointer of IAM page (0:0) in object ID 30623152, index ID 0, partition ID 72057594105430016, alloc unit ID 72057594215596032 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:203) is pointed to by the next pointer of IAM page (0:0) in object ID 30623152, index ID 2, partition ID 72057594105561088, alloc unit ID 72057594215792640 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:255) in object ID 30623152, index ID 2, partition ID 72057594105561088, alloc unit ID 72057594215792640 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:1221) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 30623152, index ID 0, partition ID 72057594105430016, alloc unit ID 72057594215596032 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:203) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 30623152, index ID 2, partition ID 72057594105561088, alloc unit ID 72057594215792640 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:17) for object ID 30623152, index ID 0, partition ID 72057594105430016, alloc unit ID 72057594215596032 (type In-row data) is linked in the IAM chain for object ID 2146106686, index ID 0, partition ID 72057594104774656, alloc unit ID 72057594214940672 (type In-row data) by page (0:0).

CHECKDB found 4 allocation errors and 5 consistency errors in table 'HUM_ETL.GHIS_Regimen_Table_b_RegimenProcedureCode' (object ID 30623152).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:9907) is pointed to by the next pointer of IAM page (0:0) in object ID 46623209, index ID 0, partition ID 72057594105757696, alloc unit ID 72057594215858176 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:10207) in object ID 46623209, index ID 0, partition ID 72057594105757696, alloc unit ID 72057594215858176 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:1390) in object ID 46623209, index ID 2, partition ID 72057594105888768, alloc unit ID 72057594216054784 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:9907) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 46623209, index ID 0, partition ID 72057594105757696, alloc unit ID 72057594215858176 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 46623209, index ID 2, partition ID 72057594105888768, alloc unit ID 72057594216054784 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 3 allocation errors and 3 consistency errors in table 'HUM_ETL.GHIS_Regimen_Table_b_RegimenProcedureCodeHistory' (object ID 46623209).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:384) in object ID 62623266, index ID 2, partition ID 72057594106216448, alloc unit ID 72057594216316928 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:1522) is pointed to by the next pointer of IAM page (0:0) in object ID 62623266, index ID 2, partition ID 72057594106216448, alloc unit ID 72057594216316928 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:1522) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 62623266, index ID 2, partition ID 72057594106216448, alloc unit ID 72057594216316928 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'HUM_ETL.GHIS_Regimen_Table_b_RegProcCodeFixedDoseFreq' (object ID 62623266).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:8) in object ID 78623323, index ID 0, partition ID 72057594106413056, alloc unit ID 72057594216382464 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:23752) is pointed to by the next pointer of IAM page (0:0) in object ID 78623323, index ID 0, partition ID 72057594106413056, alloc unit ID 72057594216382464 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:380) is pointed to by the next pointer of IAM page (0:0) in object ID 78623323, index ID 2, partition ID 72057594106544128, alloc unit ID 72057594216579072 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:1050) in object ID 78623323, index ID 2, partition ID 72057594106544128, alloc unit ID 72057594216579072 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:23752) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 78623323, index ID 0, partition ID 72057594106413056, alloc unit ID 72057594216382464 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:380) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 78623323, index ID 2, partition ID 72057594106544128, alloc unit ID 72057594216579072 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:170) for object ID 78623323, index ID 0, partition ID 72057594106413056, alloc unit ID 72057594216382464 (type In-row data) is linked in the IAM chain for object ID 2066106401, index ID 0, partition ID 72057594103136256, alloc unit ID 72057594213433344 (type In-row data) by page (0:0).

CHECKDB found 4 allocation errors and 5 consistency errors in table 'HUM_ETL.GHIS_Regimen_Table_b_RegProcCodeMaxDoseFreq' (object ID 78623323).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:515) in object ID 238623893, index ID 0, partition ID 72057594109689856, alloc unit ID 72057594219200512 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:10005) is pointed to by the next pointer of IAM page (0:0) in object ID 238623893, index ID 0, partition ID 72057594109689856, alloc unit ID 72057594219200512 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:327) is pointed to by the next pointer of IAM page (0:0) in object ID 238623893, index ID 2, partition ID 72057594109820928, alloc unit ID 72057594219397120 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:2184) in object ID 238623893, index ID 2, partition ID 72057594109820928, alloc unit ID 72057594219397120 (type In-row data), but it was not detected in the scan.

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:171) for object ID 238623893, index ID 0, partition ID 72057594109689856, alloc unit ID 72057594219200512 (type In-row data) is linked in the IAM chain for object ID 14623095, index ID 0, partition ID 72057594105102336, alloc unit ID 72057594215268352 (type In-row data) by page (0:0).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:10005) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 238623893, index ID 0, partition ID 72057594109689856, alloc unit ID 72057594219200512 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:327) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 238623893, index ID 2, partition ID 72057594109820928, alloc unit ID 72057594219397120 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 4 allocation errors and 5 consistency errors in table 'HUM_ETL.GHIS_Tables_b_AccountType' (object ID 238623893).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:1161) is pointed to by the next pointer of IAM page (0:0) in object ID 254623950, index ID 0, partition ID 72057594110017536, alloc unit ID 72057594219462656 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:9964) in object ID 254623950, index ID 0, partition ID 72057594110017536, alloc unit ID 72057594219462656 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:291) in object ID 254623950, index ID 2, partition ID 72057594110148608, alloc unit ID 72057594219724800 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:1224) is pointed to by the next pointer of IAM page (0:0) in object ID 254623950, index ID 2, partition ID 72057594110148608, alloc unit ID 72057594219724800 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:1161) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 254623950, index ID 0, partition ID 72057594110017536, alloc unit ID 72057594219462656 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:1224) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 254623950, index ID 2, partition ID 72057594110148608, alloc unit ID 72057594219724800 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 4 allocation errors and 4 consistency errors in table 'HUM_ETL.GHIS_Tables_b_Authorization' (object ID 254623950).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:113) in object ID 286624064, index ID 2, partition ID 72057594110803968, alloc unit ID 72057594220314624 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:117) is pointed to by the next pointer of IAM page (0:0) in object ID 286624064, index ID 2, partition ID 72057594110803968, alloc unit ID 72057594220314624 (type In-row data), but it was not detected in the scan.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 286624064, index ID 0, partition ID 72057594110672896, alloc unit ID 72057594275168256 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:117) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 286624064, index ID 2, partition ID 72057594110803968, alloc unit ID 72057594220314624 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (6:1109) for object ID 286624064, index ID 2, partition ID 72057594110803968, alloc unit ID 72057594220314624 (type In-row data) is linked in the IAM chain for object ID 2114106572, index ID 2, partition ID 72057594104250368, alloc unit ID 72057594214612992 (type In-row data) by page (0:0).

CHECKDB found 2 allocation errors and 4 consistency errors in table 'HUM_ETL.GHIS_Tables_b_AuthorizationHistory' (object ID 286624064).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:513) is pointed to by the next pointer of IAM page (0:0) in object ID 318624178, index ID 0, partition ID 72057594111328256, alloc unit ID 72057594220642304 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:1222) in object ID 318624178, index ID 0, partition ID 72057594111328256, alloc unit ID 72057594220642304 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:2423) in object ID 318624178, index ID 2, partition ID 72057594111459328, alloc unit ID 72057594220838912 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:513) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 318624178, index ID 0, partition ID 72057594111328256, alloc unit ID 72057594220642304 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 318624178, index ID 2, partition ID 72057594111459328, alloc unit ID 72057594220838912 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 3 allocation errors and 3 consistency errors in table 'HUM_ETL.GHIS_Tables_b_AuthorizationMedication' (object ID 318624178).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:9432) in object ID 382624406, index ID 0, partition ID 72057594112638976, alloc unit ID 72057594221690880 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:22468) is pointed to by the next pointer of IAM page (0:0) in object ID 382624406, index ID 0, partition ID 72057594112638976, alloc unit ID 72057594221690880 (type In-row data), but it was not detected in the scan.

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (6:345) for object ID 382624406, index ID 2, partition ID 72057594112770048, alloc unit ID 72057594221887488 (type In-row data) is linked in the IAM chain for object ID 574625090, index ID 2, partition ID 72057594116702208, alloc unit ID 72057594275102720 (type In-row data) by page (0:0).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:1299) is pointed to by the next pointer of IAM page (0:0) in object ID 382624406, index ID 2, partition ID 72057594112770048, alloc unit ID 72057594221887488 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:22468) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 382624406, index ID 0, partition ID 72057594112638976, alloc unit ID 72057594221690880 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:1299) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 382624406, index ID 2, partition ID 72057594112770048, alloc unit ID 72057594221887488 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (6:345) for object ID 382624406, index ID 2, partition ID 72057594112770048, alloc unit ID 72057594221887488 (type In-row data) is linked in the IAM chain for object ID 574625090, index ID 2, partition ID 72057594116702208, alloc unit ID 72057594275102720 (type In-row data) by page (0:0).

CHECKDB found 4 allocation errors and 5 consistency errors in table 'HUM_ETL.GHIS_Tables_b_AuthorizationServices' (object ID 382624406).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:517) is pointed to by the next pointer of IAM page (0:0) in object ID 398624463, index ID 0, partition ID 72057594112966656, alloc unit ID 72057594221953024 (type In-row data), but it was not detected in the scan.

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:817) for object ID 398624463, index ID 0, partition ID 72057594112966656, alloc unit ID 72057594221953024 (type In-row data) is linked in the IAM chain for object ID 958626458, index ID 0, partition ID 72057594124435456, alloc unit ID 72057594231521280 (type In-row data) by page (0:0).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:401) is pointed to by the next pointer of IAM page (0:0) in object ID 398624463, index ID 2, partition ID 72057594113097728, alloc unit ID 72057594222149632 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:2419) in object ID 398624463, index ID 2, partition ID 72057594113097728, alloc unit ID 72057594222149632 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:517) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 398624463, index ID 0, partition ID 72057594112966656, alloc unit ID 72057594221953024 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:401) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 398624463, index ID 2, partition ID 72057594113097728, alloc unit ID 72057594222149632 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:817) for object ID 398624463, index ID 0, partition ID 72057594112966656, alloc unit ID 72057594221953024 (type In-row data) is linked in the IAM chain for object ID 958626458, index ID 0, partition ID 72057594124435456, alloc unit ID 72057594231521280 (type In-row data) by page (0:0).

CHECKDB found 4 allocation errors and 5 consistency errors in table 'HUM_ETL.GHIS_Tables_b_Carrier' (object ID 398624463).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:9934) in object ID 478624748, index ID 0, partition ID 72057594114605056, alloc unit ID 72057594223329280 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:10004) is pointed to by the next pointer of IAM page (0:0) in object ID 478624748, index ID 0, partition ID 72057594114605056, alloc unit ID 72057594223329280 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:10004) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 478624748, index ID 0, partition ID 72057594114605056, alloc unit ID 72057594223329280 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'HUM_ETL.GHIS_Tables_b_CodeDirectory' (object ID 478624748).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:1718) is pointed to by the next pointer of IAM page (0:0) in object ID 558625033, index ID 0, partition ID 72057594116243456, alloc unit ID 72057594274971648 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:1158) is pointed to by the next pointer of IAM page (0:0) in object ID 558625033, index ID 2, partition ID 72057594116374528, alloc unit ID 72057594225033216 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:2148) in object ID 558625033, index ID 2, partition ID 72057594116374528, alloc unit ID 72057594225033216 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:1718) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 558625033, index ID 0, partition ID 72057594116243456, alloc unit ID 72057594274971648 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:1158) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 558625033, index ID 2, partition ID 72057594116374528, alloc unit ID 72057594225033216 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (6:1229) for object ID 558625033, index ID 2, partition ID 72057594116374528, alloc unit ID 72057594225033216 (type In-row data) is linked in the IAM chain for object ID 1922105888, index ID 2, partition ID 72057594100318208, alloc unit ID 72057594211205120 (type In-row data) by page (0:0).

CHECKDB found 3 allocation errors and 5 consistency errors in table 'HUM_ETL.GHIS_Tables_b_MemberDemographics' (object ID 558625033).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:14733) is pointed to by the next pointer of IAM page (0:0) in object ID 574625090, index ID 0, partition ID 72057594116571136, alloc unit ID 72057594275037184 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:14733) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 574625090, index ID 0, partition ID 72057594116571136, alloc unit ID 72057594275037184 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 574625090, index ID 2, partition ID 72057594116702208, alloc unit ID 72057594275102720 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 1 allocation errors and 3 consistency errors in table 'HUM_ETL.GHIS_Tables_b_MemberPolicy' (object ID 574625090).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:14728) is pointed to by the next pointer of IAM page (0:0) in object ID 590625147, index ID 0, partition ID 72057594116898816, alloc unit ID 72057594275233792 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:1821) is pointed to by the next pointer of IAM page (0:0) in object ID 590625147, index ID 2, partition ID 72057594117029888, alloc unit ID 72057594275299328 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:14728) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 590625147, index ID 0, partition ID 72057594116898816, alloc unit ID 72057594275233792 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:1821) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 590625147, index ID 2, partition ID 72057594117029888, alloc unit ID 72057594275299328 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:9910) for object ID 590625147, index ID 0, partition ID 72057594116898816, alloc unit ID 72057594275233792 (type In-row data) is linked in the IAM chain for object ID 2114106572, index ID 0, partition ID 72057594104119296, alloc unit ID 72057594214350848 (type In-row data) by page (0:0).

CHECKDB found 2 allocation errors and 5 consistency errors in table 'HUM_ETL.GHIS_Tables_b_MemberPolicyCoveragePeriod' (object ID 590625147).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:1218) is pointed to by the next pointer of IAM page (0:0) in object ID 606625204, index ID 0, partition ID 72057594117226496, alloc unit ID 72057594225623040 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:7646) in object ID 606625204, index ID 0, partition ID 72057594117226496, alloc unit ID 72057594225623040 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:1303) in object ID 606625204, index ID 2, partition ID 72057594117357568, alloc unit ID 72057594225819648 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:2151) is pointed to by the next pointer of IAM page (0:0) in object ID 606625204, index ID 2, partition ID 72057594117357568, alloc unit ID 72057594225819648 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:1218) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 606625204, index ID 0, partition ID 72057594117226496, alloc unit ID 72057594225623040 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:2151) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 606625204, index ID 2, partition ID 72057594117357568, alloc unit ID 72057594225819648 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (6:1302) for object ID 606625204, index ID 2, partition ID 72057594117357568, alloc unit ID 72057594225819648 (type In-row data) is linked in the IAM chain for object ID 2002106173, index ID 2, partition ID 72057594101956608, alloc unit ID 72057594212515840 (type In-row data) by page (0:0).

CHECKDB found 4 allocation errors and 5 consistency errors in table 'HUM_ETL.GHIS_Tables_b_NameLookup' (object ID 606625204).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:9908) in object ID 622625261, index ID 0, partition ID 72057594117554176, alloc unit ID 72057594225885184 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:1595) is pointed to by the next pointer of IAM page (0:0) in object ID 622625261, index ID 2, partition ID 72057594117685248, alloc unit ID 72057594226081792 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:2378) in object ID 622625261, index ID 2, partition ID 72057594117685248, alloc unit ID 72057594226081792 (type In-row data), but it was not detected in the scan.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 622625261, index ID 0, partition ID 72057594117554176, alloc unit ID 72057594225885184 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:1595) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 622625261, index ID 2, partition ID 72057594117685248, alloc unit ID 72057594226081792 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 3 allocation errors and 3 consistency errors in table 'HUM_ETL.GHIS_Tables_b_Network' (object ID 622625261).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:9929) in object ID 638625318, index ID 0, partition ID 72057594117881856, alloc unit ID 72057594226147328 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:4013) in object ID 638625318, index ID 2, partition ID 72057594118012928, alloc unit ID 72057594226343936 (type In-row data), but it was not detected in the scan.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 638625318, index ID 0, partition ID 72057594117881856, alloc unit ID 72057594226147328 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 638625318, index ID 2, partition ID 72057594118012928, alloc unit ID 72057594226343936 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'HUM_ETL.GHIS_Tables_b_PCP' (object ID 638625318).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:4690) is pointed to by the next pointer of IAM page (0:0) in object ID 654625375, index ID 0, partition ID 72057594118209536, alloc unit ID 72057594226409472 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:10001) in object ID 654625375, index ID 0, partition ID 72057594118209536, alloc unit ID 72057594226409472 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:1216) is pointed to by the next pointer of IAM page (0:0) in object ID 654625375, index ID 2, partition ID 72057594118340608, alloc unit ID 72057594226606080 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:5557) in object ID 654625375, index ID 2, partition ID 72057594118340608, alloc unit ID 72057594226606080 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:4690) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 654625375, index ID 0, partition ID 72057594118209536, alloc unit ID 72057594226409472 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:1216) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 654625375, index ID 2, partition ID 72057594118340608, alloc unit ID 72057594226606080 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 4 allocation errors and 4 consistency errors in table 'HUM_ETL.GHIS_Tables_b_PCPDemographics' (object ID 654625375).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:519) is pointed to by the next pointer of IAM page (0:0) in object ID 814625945, index ID 0, partition ID 72057594121486336, alloc unit ID 72057594229096448 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:4143) in object ID 814625945, index ID 0, partition ID 72057594121486336, alloc unit ID 72057594229096448 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:289) in object ID 814625945, index ID 2, partition ID 72057594121617408, alloc unit ID 72057594229293056 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:1159) is pointed to by the next pointer of IAM page (0:0) in object ID 814625945, index ID 2, partition ID 72057594121617408, alloc unit ID 72057594229293056 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:519) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 814625945, index ID 0, partition ID 72057594121486336, alloc unit ID 72057594229096448 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:1159) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 814625945, index ID 2, partition ID 72057594121617408, alloc unit ID 72057594229293056 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 4 allocation errors and 4 consistency errors in table 'HUM_ETL.GHIS_Tables_b_Provider' (object ID 814625945).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:4472) in object ID 830626002, index ID 0, partition ID 72057594121814016, alloc unit ID 72057594229358592 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:382) in object ID 830626002, index ID 2, partition ID 72057594121945088, alloc unit ID 72057594229555200 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:1599) is pointed to by the next pointer of IAM page (0:0) in object ID 830626002, index ID 2, partition ID 72057594121945088, alloc unit ID 72057594229555200 (type In-row data), but it was not detected in the scan.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 830626002, index ID 0, partition ID 72057594121814016, alloc unit ID 72057594229358592 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:1599) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 830626002, index ID 2, partition ID 72057594121945088, alloc unit ID 72057594229555200 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 3 allocation errors and 3 consistency errors in table 'HUM_ETL.GHIS_Tables_b_ProviderMultiOffice' (object ID 830626002).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:299) is pointed to by the next pointer of IAM page (0:0) in object ID 846626059, index ID 0, partition ID 72057594122141696, alloc unit ID 72057594229620736 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:10065) in object ID 846626059, index ID 0, partition ID 72057594122141696, alloc unit ID 72057594229620736 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:1154) in object ID 846626059, index ID 2, partition ID 72057594122272768, alloc unit ID 72057594229817344 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:4014) is pointed to by the next pointer of IAM page (0:0) in object ID 846626059, index ID 2, partition ID 72057594122272768, alloc unit ID 72057594229817344 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:299) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 846626059, index ID 0, partition ID 72057594122141696, alloc unit ID 72057594229620736 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:4014) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 846626059, index ID 2, partition ID 72057594122272768, alloc unit ID 72057594229817344 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 4 allocation errors and 4 consistency errors in table 'HUM_ETL.GHIS_Tables_b_ProviderOffice' (object ID 846626059).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:753) is pointed to by the next pointer of IAM page (0:0) in object ID 862626116, index ID 0, partition ID 72057594122469376, alloc unit ID 72057594229882880 (type In-row data), but it was not detected in the scan.

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:4008) for object ID 862626116, index ID 0, partition ID 72057594122469376, alloc unit ID 72057594229882880 (type In-row data) is linked in the IAM chain for object ID 622625261, index ID 0, partition ID 72057594117554176, alloc unit ID 72057594225885184 (type In-row data) by page (0:0).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:1296) is pointed to by the next pointer of IAM page (0:0) in object ID 862626116, index ID 2, partition ID 72057594122600448, alloc unit ID 72057594230079488 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:5554) in object ID 862626116, index ID 2, partition ID 72057594122600448, alloc unit ID 72057594230079488 (type In-row data), but it was not detected in the scan.

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:4008) for object ID 862626116, index ID 0, partition ID 72057594122469376, alloc unit ID 72057594229882880 (type In-row data) is linked in the IAM chain for object ID 622625261, index ID 0, partition ID 72057594117554176, alloc unit ID 72057594225885184 (type In-row data) by page (0:0).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:753) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 862626116, index ID 0, partition ID 72057594122469376, alloc unit ID 72057594229882880 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:1296) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 862626116, index ID 2, partition ID 72057594122600448, alloc unit ID 72057594230079488 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 4 allocation errors and 5 consistency errors in table 'HUM_ETL.GHIS_Tables_b_ReferringProvider' (object ID 862626116).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:4012) for object ID 894626230, index ID 0, partition ID 72057594123124736, alloc unit ID 72057594230407168 (type In-row data) is linked in the IAM chain for object ID 830626002, index ID 0, partition ID 72057594121814016, alloc unit ID 72057594229358592 (type In-row data) by page (0:0).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:4311) is pointed to by the next pointer of IAM page (0:0) in object ID 894626230, index ID 0, partition ID 72057594123124736, alloc unit ID 72057594230407168 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:259) in object ID 894626230, index ID 2, partition ID 72057594123255808, alloc unit ID 72057594230603776 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:1823) is pointed to by the next pointer of IAM page (0:0) in object ID 894626230, index ID 2, partition ID 72057594123255808, alloc unit ID 72057594230603776 (type In-row data), but it was not detected in the scan.

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:4012) for object ID 894626230, index ID 0, partition ID 72057594123124736, alloc unit ID 72057594230407168 (type In-row data) is linked in the IAM chain for object ID 830626002, index ID 0, partition ID 72057594121814016, alloc unit ID 72057594229358592 (type In-row data) by page (0:0).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:4311) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 894626230, index ID 0, partition ID 72057594123124736, alloc unit ID 72057594230407168 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:1823) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 894626230, index ID 2, partition ID 72057594123255808, alloc unit ID 72057594230603776 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 4 allocation errors and 5 consistency errors in table 'HUM_ETL.GHIS_Tables_b_TaxId' (object ID 894626230).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:301) is pointed to by the next pointer of IAM page (0:0) in object ID 926626344, index ID 0, partition ID 72057594123780096, alloc unit ID 72057594230996992 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:4139) in object ID 926626344, index ID 0, partition ID 72057594123780096, alloc unit ID 72057594230996992 (type In-row data), but it was not detected in the scan.

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (6:270) for object ID 926626344, index ID 2, partition ID 72057594123911168, alloc unit ID 72057594231193600 (type In-row data) is linked in the IAM chain for object ID 1102626971, index ID 2, partition ID 72057594127515648, alloc unit ID 72057594234208256 (type In-row data) by page (0:0).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:5067) is pointed to by the next pointer of IAM page (0:0) in object ID 926626344, index ID 2, partition ID 72057594123911168, alloc unit ID 72057594231193600 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:301) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 926626344, index ID 0, partition ID 72057594123780096, alloc unit ID 72057594230996992 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:5067) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 926626344, index ID 2, partition ID 72057594123911168, alloc unit ID 72057594231193600 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (6:270) for object ID 926626344, index ID 2, partition ID 72057594123911168, alloc unit ID 72057594231193600 (type In-row data) is linked in the IAM chain for object ID 1102626971, index ID 2, partition ID 72057594127515648, alloc unit ID 72057594234208256 (type In-row data) by page (0:0).

CHECKDB found 4 allocation errors and 5 consistency errors in table 'HUM_ETL.GHIS_Tables_b_User' (object ID 926626344).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:200) is pointed to by the next pointer of IAM page (0:0) in object ID 942626401, index ID 0, partition ID 72057594124107776, alloc unit ID 72057594231259136 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:4688) in object ID 942626401, index ID 0, partition ID 72057594124107776, alloc unit ID 72057594231259136 (type In-row data), but it was not detected in the scan.

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (6:661) for object ID 942626401, index ID 2, partition ID 72057594124238848, alloc unit ID 72057594231455744 (type In-row data) is linked in the IAM chain for object ID 638625318, index ID 2, partition ID 72057594118012928, alloc unit ID 72057594226343936 (type In-row data) by page (0:0).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:1049) is pointed to by the next pointer of IAM page (0:0) in object ID 942626401, index ID 2, partition ID 72057594124238848, alloc unit ID 72057594231455744 (type In-row data), but it was not detected in the scan.

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (6:661) for object ID 942626401, index ID 2, partition ID 72057594124238848, alloc unit ID 72057594231455744 (type In-row data) is linked in the IAM chain for object ID 638625318, index ID 2, partition ID 72057594118012928, alloc unit ID 72057594226343936 (type In-row data) by page (0:0).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:200) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 942626401, index ID 0, partition ID 72057594124107776, alloc unit ID 72057594231259136 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:1049) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 942626401, index ID 2, partition ID 72057594124238848, alloc unit ID 72057594231455744 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 4 allocation errors and 5 consistency errors in table 'HUM_ETL.GHIS_Tables_b_UserPracticeAddress' (object ID 942626401).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:7641) in object ID 958626458, index ID 0, partition ID 72057594124435456, alloc unit ID 72057594231521280 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:1111) in object ID 958626458, index ID 2, partition ID 72057594124566528, alloc unit ID 72057594231717888 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:1520) is pointed to by the next pointer of IAM page (0:0) in object ID 958626458, index ID 2, partition ID 72057594124566528, alloc unit ID 72057594231717888 (type In-row data), but it was not detected in the scan.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 958626458, index ID 0, partition ID 72057594124435456, alloc unit ID 72057594231521280 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:1520) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 958626458, index ID 2, partition ID 72057594124566528, alloc unit ID 72057594231717888 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:9874) for object ID 958626458, index ID 0, partition ID 72057594124435456, alloc unit ID 72057594231521280 (type In-row data) is linked in the IAM chain for object ID 2098106515, index ID 0, partition ID 72057594103791616, alloc unit ID 72057594214088704 (type In-row data) by page (0:0).

CHECKDB found 3 allocation errors and 4 consistency errors in table 'HUM_ETL.GHIS_Tables_b_VisitSite' (object ID 958626458).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:10069) is pointed to by the next pointer of IAM page (0:0) in object ID 974626515, index ID 0, partition ID 72057594124763136, alloc unit ID 72057594231783424 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:10163) in object ID 974626515, index ID 0, partition ID 72057594124763136, alloc unit ID 72057594231783424 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:1156) in object ID 974626515, index ID 2, partition ID 72057594124894208, alloc unit ID 72057594231980032 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:1909) is pointed to by the next pointer of IAM page (0:0) in object ID 974626515, index ID 2, partition ID 72057594124894208, alloc unit ID 72057594231980032 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:10069) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 974626515, index ID 0, partition ID 72057594124763136, alloc unit ID 72057594231783424 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:1909) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 974626515, index ID 2, partition ID 72057594124894208, alloc unit ID 72057594231980032 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 4 allocation errors and 4 consistency errors in table 'HUM_ETL.GHIS_Tables_b_VisitType' (object ID 974626515).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:48) for object ID 1102626971, index ID 0, partition ID 72057594127384576, alloc unit ID 72057594233946112 (type In-row data) is linked in the IAM chain for object ID 638625318, index ID 0, partition ID 72057594117881856, alloc unit ID 72057594226147328 (type In-row data) by page (0:0).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:970) is pointed to by the next pointer of IAM page (0:0) in object ID 1102626971, index ID 0, partition ID 72057594127384576, alloc unit ID 72057594233946112 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:1192) in object ID 1102626971, index ID 2, partition ID 72057594127515648, alloc unit ID 72057594234208256 (type In-row data), but it was not detected in the scan.

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:48) for object ID 1102626971, index ID 0, partition ID 72057594127384576, alloc unit ID 72057594233946112 (type In-row data) is linked in the IAM chain for object ID 638625318, index ID 0, partition ID 72057594117881856, alloc unit ID 72057594226147328 (type In-row data) by page (0:0).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:970) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1102626971, index ID 0, partition ID 72057594127384576, alloc unit ID 72057594233946112 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1102626971, index ID 2, partition ID 72057594127515648, alloc unit ID 72057594234208256 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 3 allocation errors and 4 consistency errors in table 'HUM_ETL.GHIS_User_b_AccountHistory' (object ID 1102626971).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:514) in object ID 1150627142, index ID 0, partition ID 72057594128367616, alloc unit ID 72057594234798080 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:10067) is pointed to by the next pointer of IAM page (0:0) in object ID 1150627142, index ID 0, partition ID 72057594128367616, alloc unit ID 72057594234798080 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:1594) in object ID 1150627142, index ID 2, partition ID 72057594128498688, alloc unit ID 72057594235060224 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:2377) is pointed to by the next pointer of IAM page (0:0) in object ID 1150627142, index ID 2, partition ID 72057594128498688, alloc unit ID 72057594235060224 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:10067) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1150627142, index ID 0, partition ID 72057594128367616, alloc unit ID 72057594234798080 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:2377) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1150627142, index ID 2, partition ID 72057594128498688, alloc unit ID 72057594235060224 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 4 allocation errors and 4 consistency errors in table 'HUM_ETL.GHIS_User_Table_b_Account' (object ID 1150627142).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:968) in object ID 1166627199, index ID 0, partition ID 72057594128695296, alloc unit ID 72057594235125760 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:1234) is pointed to by the next pointer of IAM page (0:0) in object ID 1166627199, index ID 0, partition ID 72057594128695296, alloc unit ID 72057594235125760 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:263) in object ID 1166627199, index ID 2, partition ID 72057594128826368, alloc unit ID 72057594235322368 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:320) is pointed to by the next pointer of IAM page (0:0) in object ID 1166627199, index ID 2, partition ID 72057594128826368, alloc unit ID 72057594235322368 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:1234) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1166627199, index ID 0, partition ID 72057594128695296, alloc unit ID 72057594235125760 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:320) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1166627199, index ID 2, partition ID 72057594128826368, alloc unit ID 72057594235322368 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 4 allocation errors and 4 consistency errors in table 'HUM_ETL.GHIS_User_Table_b_AccountGroup' (object ID 1166627199).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:4473) in object ID 1182627256, index ID 0, partition ID 72057594129022976, alloc unit ID 72057594235387904 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:1155) is pointed to by the next pointer of IAM page (0:0) in object ID 1182627256, index ID 2, partition ID 72057594129154048, alloc unit ID 72057594235650048 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:1217) in object ID 1182627256, index ID 2, partition ID 72057594129154048, alloc unit ID 72057594235650048 (type In-row data), but it was not detected in the scan.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1182627256, index ID 0, partition ID 72057594129022976, alloc unit ID 72057594235387904 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:1155) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1182627256, index ID 2, partition ID 72057594129154048, alloc unit ID 72057594235650048 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 3 allocation errors and 3 consistency errors in table 'HUM_ETL.GHIS_User_Table_b_AccountHistory' (object ID 1182627256).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:240) in object ID 1198627313, index ID 0, partition ID 72057594129350656, alloc unit ID 72057594235715584 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:516) is pointed to by the next pointer of IAM page (0:0) in object ID 1198627313, index ID 0, partition ID 72057594129350656, alloc unit ID 72057594235715584 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:252) is pointed to by the next pointer of IAM page (0:0) in object ID 1198627313, index ID 2, partition ID 72057594129481728, alloc unit ID 72057594235912192 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:1197) in object ID 1198627313, index ID 2, partition ID 72057594129481728, alloc unit ID 72057594235912192 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:516) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1198627313, index ID 0, partition ID 72057594129350656, alloc unit ID 72057594235715584 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:252) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1198627313, index ID 2, partition ID 72057594129481728, alloc unit ID 72057594235912192 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 4 allocation errors and 4 consistency errors in table 'HUM_ETL.GHIS_User_Table_b_AccountProvider' (object ID 1198627313).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:245) is pointed to by the next pointer of IAM page (0:0) in object ID 1214627370, index ID 0, partition ID 72057594129678336, alloc unit ID 72057594235977728 (type In-row data), but it was not detected in the scan.

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:821) for object ID 1214627370, index ID 0, partition ID 72057594129678336, alloc unit ID 72057594235977728 (type In-row data) is linked in the IAM chain for object ID 1182627256, index ID 0, partition ID 72057594129022976, alloc unit ID 72057594235387904 (type In-row data) by page (0:0).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:251) in object ID 1214627370, index ID 2, partition ID 72057594129809408, alloc unit ID 72057594236174336 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:1153) is pointed to by the next pointer of IAM page (0:0) in object ID 1214627370, index ID 2, partition ID 72057594129809408, alloc unit ID 72057594236174336 (type In-row data), but it was not detected in the scan.

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:821) for object ID 1214627370, index ID 0, partition ID 72057594129678336, alloc unit ID 72057594235977728 (type In-row data) is linked in the IAM chain for object ID 1182627256, index ID 0, partition ID 72057594129022976, alloc unit ID 72057594235387904 (type In-row data) by page (0:0).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:245) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1214627370, index ID 0, partition ID 72057594129678336, alloc unit ID 72057594235977728 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:1153) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1214627370, index ID 2, partition ID 72057594129809408, alloc unit ID 72057594236174336 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 4 allocation errors and 5 consistency errors in table 'HUM_ETL.GHIS_User_Table_b_Group' (object ID 1214627370).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:4226) in object ID 1230627427, index ID 0, partition ID 72057594130006016, alloc unit ID 72057594236239872 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:4692) is pointed to by the next pointer of IAM page (0:0) in object ID 1230627427, index ID 0, partition ID 72057594130006016, alloc unit ID 72057594236239872 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:674) in object ID 1230627427, index ID 2, partition ID 72057594130137088, alloc unit ID 72057594236436480 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:1225) is pointed to by the next pointer of IAM page (0:0) in object ID 1230627427, index ID 2, partition ID 72057594130137088, alloc unit ID 72057594236436480 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:4692) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1230627427, index ID 0, partition ID 72057594130006016, alloc unit ID 72057594236239872 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:1225) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1230627427, index ID 2, partition ID 72057594130137088, alloc unit ID 72057594236436480 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 4 allocation errors and 4 consistency errors in table 'HUM_ETL.MyFax_b_Account' (object ID 1230627427).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:4230) in object ID 1246627484, index ID 0, partition ID 72057594130333696, alloc unit ID 72057594236502016 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:10000) is pointed to by the next pointer of IAM page (0:0) in object ID 1246627484, index ID 0, partition ID 72057594130333696, alloc unit ID 72057594236502016 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:1110) in object ID 1246627484, index ID 2, partition ID 72057594130464768, alloc unit ID 72057594236764160 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:1297) is pointed to by the next pointer of IAM page (0:0) in object ID 1246627484, index ID 2, partition ID 72057594130464768, alloc unit ID 72057594236764160 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:10000) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1246627484, index ID 0, partition ID 72057594130333696, alloc unit ID 72057594236502016 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:1297) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1246627484, index ID 2, partition ID 72057594130464768, alloc unit ID 72057594236764160 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 4 allocation errors and 4 consistency errors in table 'HUM_ETL.MyFax_b_StatusMessages' (object ID 1246627484).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:4697) is pointed to by the next pointer of IAM page (0:0) in object ID 1570104634, index ID 0, partition ID 72057594092978176, alloc unit ID 72057594204717056 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:22469) in object ID 1570104634, index ID 0, partition ID 72057594092978176, alloc unit ID 72057594204717056 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:1230) is pointed to by the next pointer of IAM page (0:0) in object ID 1570104634, index ID 2, partition ID 72057594093109248, alloc unit ID 72057594204913664 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:1388) in object ID 1570104634, index ID 2, partition ID 72057594093109248, alloc unit ID 72057594204913664 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:4697) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1570104634, index ID 0, partition ID 72057594092978176, alloc unit ID 72057594204717056 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:1230) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1570104634, index ID 2, partition ID 72057594093109248, alloc unit ID 72057594204913664 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 4 allocation errors and 4 consistency errors in table 'HUM_ETL.GHIS_Authorization_Table_b_AuthorizationPhoneCallComment' (object ID 1570104634).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:426) in object ID 1586104691, index ID 0, partition ID 72057594093305856, alloc unit ID 72057594204979200 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:1177) is pointed to by the next pointer of IAM page (0:0) in object ID 1586104691, index ID 0, partition ID 72057594093305856, alloc unit ID 72057594204979200 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:1199) in object ID 1586104691, index ID 2, partition ID 72057594093436928, alloc unit ID 72057594205175808 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:1598) is pointed to by the next pointer of IAM page (0:0) in object ID 1586104691, index ID 2, partition ID 72057594093436928, alloc unit ID 72057594205175808 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:1177) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1586104691, index ID 0, partition ID 72057594093305856, alloc unit ID 72057594204979200 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:1598) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1586104691, index ID 2, partition ID 72057594093436928, alloc unit ID 72057594205175808 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 4 allocation errors and 4 consistency errors in table 'HUM_ETL.GHIS_Authorization_Table_b_AuthorizationReasonComment' (object ID 1586104691).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:1176) in object ID 1602104748, index ID 0, partition ID 72057594093633536, alloc unit ID 72057594205241344 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:1182) is pointed to by the next pointer of IAM page (0:0) in object ID 1602104748, index ID 0, partition ID 72057594093633536, alloc unit ID 72057594205241344 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:103) in object ID 1602104748, index ID 2, partition ID 72057594093764608, alloc unit ID 72057594205503488 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:5807) is pointed to by the next pointer of IAM page (0:0) in object ID 1602104748, index ID 2, partition ID 72057594093764608, alloc unit ID 72057594205503488 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:1182) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1602104748, index ID 0, partition ID 72057594093633536, alloc unit ID 72057594205241344 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:5807) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1602104748, index ID 2, partition ID 72057594093764608, alloc unit ID 72057594205503488 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 4 allocation errors and 4 consistency errors in table 'HUM_ETL.GHIS_Authorization_Table_b_Comment' (object ID 1602104748).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:18) is pointed to by the next pointer of IAM page (0:0) in object ID 1618104805, index ID 0, partition ID 72057594093961216, alloc unit ID 72057594205569024 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:46) in object ID 1618104805, index ID 0, partition ID 72057594093961216, alloc unit ID 72057594205569024 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:1171) in object ID 1618104805, index ID 2, partition ID 72057594094092288, alloc unit ID 72057594205765632 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:1910) is pointed to by the next pointer of IAM page (0:0) in object ID 1618104805, index ID 2, partition ID 72057594094092288, alloc unit ID 72057594205765632 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:18) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1618104805, index ID 0, partition ID 72057594093961216, alloc unit ID 72057594205569024 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:1910) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1618104805, index ID 2, partition ID 72057594094092288, alloc unit ID 72057594205765632 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 4 allocation errors and 4 consistency errors in table 'HUM_ETL.GHIS_Authorization_Table_b_HumanaReportDate' (object ID 1618104805).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:818) is pointed to by the next pointer of IAM page (0:0) in object ID 1634104862, index ID 0, partition ID 72057594094288896, alloc unit ID 72057594205831168 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:1282) in object ID 1634104862, index ID 0, partition ID 72057594094288896, alloc unit ID 72057594205831168 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:321) in object ID 1634104862, index ID 2, partition ID 72057594094419968, alloc unit ID 72057594206093312 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:2189) is pointed to by the next pointer of IAM page (0:0) in object ID 1634104862, index ID 2, partition ID 72057594094419968, alloc unit ID 72057594206093312 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:818) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1634104862, index ID 0, partition ID 72057594094288896, alloc unit ID 72057594205831168 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:2189) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1634104862, index ID 2, partition ID 72057594094419968, alloc unit ID 72057594206093312 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 4 allocation errors and 4 consistency errors in table 'HUM_ETL.GHIS_Authorization_Table_b_Note' (object ID 1634104862).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:518) in object ID 1650104919, index ID 0, partition ID 72057594094616576, alloc unit ID 72057594206158848 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:4702) is pointed to by the next pointer of IAM page (0:0) in object ID 1650104919, index ID 0, partition ID 72057594094616576, alloc unit ID 72057594206158848 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:1521) in object ID 1650104919, index ID 2, partition ID 72057594094747648, alloc unit ID 72057594206355456 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:4011) is pointed to by the next pointer of IAM page (0:0) in object ID 1650104919, index ID 2, partition ID 72057594094747648, alloc unit ID 72057594206355456 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:4702) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1650104919, index ID 0, partition ID 72057594094616576, alloc unit ID 72057594206158848 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:4011) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1650104919, index ID 2, partition ID 72057594094747648, alloc unit ID 72057594206355456 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 4 allocation errors and 4 consistency errors in table 'HUM_ETL.GHIS_Authorization_Table_b_RoleAccountAuthorization' (object ID 1650104919).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:4474) is pointed to by the next pointer of IAM page (0:0) in object ID 1666104976, index ID 0, partition ID 72057594094944256, alloc unit ID 72057594206420992 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:22238) in object ID 1666104976, index ID 0, partition ID 72057594094944256, alloc unit ID 72057594206420992 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:4015) in object ID 1666104976, index ID 2, partition ID 72057594095075328, alloc unit ID 72057594206683136 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:5552) is pointed to by the next pointer of IAM page (0:0) in object ID 1666104976, index ID 2, partition ID 72057594095075328, alloc unit ID 72057594206683136 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:4474) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1666104976, index ID 0, partition ID 72057594094944256, alloc unit ID 72057594206420992 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:5552) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1666104976, index ID 2, partition ID 72057594095075328, alloc unit ID 72057594206683136 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 4 allocation errors and 4 consistency errors in table 'HUM_ETL.GHIS_b_GenericFax' (object ID 1666104976).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:425) is pointed to by the next pointer of IAM page (0:0) in object ID 1682105033, index ID 0, partition ID 72057594095271936, alloc unit ID 72057594206748672 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:4136) in object ID 1682105033, index ID 0, partition ID 72057594095271936, alloc unit ID 72057594206748672 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:2383) is pointed to by the next pointer of IAM page (0:0) in object ID 1682105033, index ID 2, partition ID 72057594095403008, alloc unit ID 72057594207010816 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:5575) in object ID 1682105033, index ID 2, partition ID 72057594095403008, alloc unit ID 72057594207010816 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:425) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1682105033, index ID 0, partition ID 72057594095271936, alloc unit ID 72057594206748672 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:2383) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1682105033, index ID 2, partition ID 72057594095403008, alloc unit ID 72057594207010816 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 4 allocation errors and 4 consistency errors in table 'HUM_ETL.GHIS_ContentManagement_b_Article' (object ID 1682105033).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:427) is pointed to by the next pointer of IAM page (0:0) in object ID 1698105090, index ID 0, partition ID 72057594095599616, alloc unit ID 72057594207076352 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:10066) in object ID 1698105090, index ID 0, partition ID 72057594095599616, alloc unit ID 72057594207076352 (type In-row data), but it was not detected in the scan.

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (6:715) for object ID 1698105090, index ID 2, partition ID 72057594095730688, alloc unit ID 72057594207272960 (type In-row data) is linked in the IAM chain for object ID 318624178, index ID 2, partition ID 72057594111459328, alloc unit ID 72057594220838912 (type In-row data) by page (0:0).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:2417) is pointed to by the next pointer of IAM page (0:0) in object ID 1698105090, index ID 2, partition ID 72057594095730688, alloc unit ID 72057594207272960 (type In-row data), but it was not detected in the scan.

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (6:715) for object ID 1698105090, index ID 2, partition ID 72057594095730688, alloc unit ID 72057594207272960 (type In-row data) is linked in the IAM chain for object ID 318624178, index ID 2, partition ID 72057594111459328, alloc unit ID 72057594220838912 (type In-row data) by page (0:0).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:427) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1698105090, index ID 0, partition ID 72057594095599616, alloc unit ID 72057594207076352 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:2417) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1698105090, index ID 2, partition ID 72057594095730688, alloc unit ID 72057594207272960 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 4 allocation errors and 5 consistency errors in table 'HUM_ETL.GHIS_Diagnosis_Table_b_DiagnosisCode' (object ID 1698105090).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:758) for object ID 1730105204, index ID 0, partition ID 72057594096254976, alloc unit ID 72057594207600640 (type In-row data) is linked in the IAM chain for object ID 286624064, index ID 0, partition ID 72057594110672896, alloc unit ID 72057594275168256 (type In-row data) by page (0:0).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:4694) is pointed to by the next pointer of IAM page (0:0) in object ID 1730105204, index ID 0, partition ID 72057594096254976, alloc unit ID 72057594207600640 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:47) in object ID 1730105204, index ID 2, partition ID 72057594096386048, alloc unit ID 72057594207862784 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:98) is pointed to by the next pointer of IAM page (0:0) in object ID 1730105204, index ID 2, partition ID 72057594096386048, alloc unit ID 72057594207862784 (type In-row data), but it was not detected in the scan.

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:758) for object ID 1730105204, index ID 0, partition ID 72057594096254976, alloc unit ID 72057594207600640 (type In-row data) is linked in the IAM chain for object ID 286624064, index ID 0, partition ID 72057594110672896, alloc unit ID 72057594275168256 (type In-row data) by page (0:0).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:4694) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1730105204, index ID 0, partition ID 72057594096254976, alloc unit ID 72057594207600640 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:98) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1730105204, index ID 2, partition ID 72057594096386048, alloc unit ID 72057594207862784 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 4 allocation errors and 5 consistency errors in table 'HUM_ETL.GHIS_DocumentMgmt_b_Document' (object ID 1730105204).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:42) is pointed to by the next pointer of IAM page (0:0) in object ID 1746105261, index ID 0, partition ID 72057594096582656, alloc unit ID 72057594207928320 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:15748) in object ID 1746105261, index ID 0, partition ID 72057594096582656, alloc unit ID 72057594207928320 (type In-row data), but it was not detected in the scan.

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (6:214) for object ID 1746105261, index ID 2, partition ID 72057594096713728, alloc unit ID 72057594208124928 (type In-row data) is linked in the IAM chain for object ID 2066106401, index ID 2, partition ID 72057594103267328, alloc unit ID 72057594213695488 (type In-row data) by page (0:0).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:42) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1746105261, index ID 0, partition ID 72057594096582656, alloc unit ID 72057594207928320 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1746105261, index ID 2, partition ID 72057594096713728, alloc unit ID 72057594208124928 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (6:214) for object ID 1746105261, index ID 2, partition ID 72057594096713728, alloc unit ID 72057594208124928 (type In-row data) is linked in the IAM chain for object ID 2066106401, index ID 2, partition ID 72057594103267328, alloc unit ID 72057594213695488 (type In-row data) by page (0:0).

CHECKDB found 3 allocation errors and 4 consistency errors in table 'HUM_ETL.GHIS_DocumentMgmt_Table_b_RoleAccountDocument' (object ID 1746105261).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:1160) in object ID 1778105375, index ID 0, partition ID 72057594097238016, alloc unit ID 72057594208452608 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:22233) is pointed to by the next pointer of IAM page (0:0) in object ID 1778105375, index ID 0, partition ID 72057594097238016, alloc unit ID 72057594208452608 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:1054) is pointed to by the next pointer of IAM page (0:0) in object ID 1778105375, index ID 2, partition ID 72057594097369088, alloc unit ID 72057594208714752 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:5068) in object ID 1778105375, index ID 2, partition ID 72057594097369088, alloc unit ID 72057594208714752 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:22233) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1778105375, index ID 0, partition ID 72057594097238016, alloc unit ID 72057594208452608 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:1054) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1778105375, index ID 2, partition ID 72057594097369088, alloc unit ID 72057594208714752 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 4 allocation errors and 4 consistency errors in table 'HUM_ETL.GHIS_GenericFax_b_Transmittal' (object ID 1778105375).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:4477) is pointed to by the next pointer of IAM page (0:0) in object ID 1794105432, index ID 0, partition ID 72057594097565696, alloc unit ID 72057594208780288 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:4478) in object ID 1794105432, index ID 0, partition ID 72057594097565696, alloc unit ID 72057594208780288 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:208) is pointed to by the next pointer of IAM page (0:0) in object ID 1794105432, index ID 2, partition ID 72057594097696768, alloc unit ID 72057594208976896 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:800) in object ID 1794105432, index ID 2, partition ID 72057594097696768, alloc unit ID 72057594208976896 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:4477) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1794105432, index ID 0, partition ID 72057594097565696, alloc unit ID 72057594208780288 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:208) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1794105432, index ID 2, partition ID 72057594097696768, alloc unit ID 72057594208976896 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 4 allocation errors and 4 consistency errors in table 'HUM_ETL.GHIS_Log_Table_b_UserActionLog' (object ID 1794105432).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:43) in object ID 1858105660, index ID 0, partition ID 72057594098876416, alloc unit ID 72057594209959936 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:1773) is pointed to by the next pointer of IAM page (0:0) in object ID 1858105660, index ID 0, partition ID 72057594098876416, alloc unit ID 72057594209959936 (type In-row data), but it was not detected in the scan.

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (6:2379) for object ID 1858105660, index ID 2, partition ID 72057594099007488, alloc unit ID 72057594210156544 (type In-row data) is linked in the IAM chain for object ID 1746105261, index ID 2, partition ID 72057594096713728, alloc unit ID 72057594208124928 (type In-row data) by page (0:0).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (6:2379) for object ID 1858105660, index ID 2, partition ID 72057594099007488, alloc unit ID 72057594210156544 (type In-row data) is linked in the IAM chain for object ID 1746105261, index ID 2, partition ID 72057594096713728, alloc unit ID 72057594208124928 (type In-row data) by page (0:0).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:1773) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1858105660, index ID 0, partition ID 72057594098876416, alloc unit ID 72057594209959936 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1858105660, index ID 2, partition ID 72057594099007488, alloc unit ID 72057594210156544 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 3 allocation errors and 4 consistency errors in table 'HUM_ETL.GHIS_Phone_Table_b_PhoneCall' (object ID 1858105660).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:203) is pointed to by the next pointer of IAM page (0:0) in object ID 1890105774, index ID 0, partition ID 72057594099531776, alloc unit ID 72057594210484224 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:1770) in object ID 1890105774, index ID 0, partition ID 72057594099531776, alloc unit ID 72057594210484224 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:656) in object ID 1890105774, index ID 2, partition ID 72057594099662848, alloc unit ID 72057594210680832 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:5804) is pointed to by the next pointer of IAM page (0:0) in object ID 1890105774, index ID 2, partition ID 72057594099662848, alloc unit ID 72057594210680832 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:203) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1890105774, index ID 0, partition ID 72057594099531776, alloc unit ID 72057594210484224 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:5804) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1890105774, index ID 2, partition ID 72057594099662848, alloc unit ID 72057594210680832 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 4 allocation errors and 4 consistency errors in table 'HUM_ETL.GHIS_Procedure_Table_b_Dose' (object ID 1890105774).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:14) is pointed to by the next pointer of IAM page (0:0) in object ID 1922105888, index ID 0, partition ID 72057594100187136, alloc unit ID 72057594211008512 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:1712) in object ID 1922105888, index ID 0, partition ID 72057594100187136, alloc unit ID 72057594211008512 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:1229) is pointed to by the next pointer of IAM page (0:0) in object ID 1922105888, index ID 2, partition ID 72057594100318208, alloc unit ID 72057594211205120 (type In-row data), but it was not detected in the scan.

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (6:1907) for object ID 1922105888, index ID 2, partition ID 72057594100318208, alloc unit ID 72057594211205120 (type In-row data) is linked in the IAM chain for object ID 1858105660, index ID 2, partition ID 72057594099007488, alloc unit ID 72057594210156544 (type In-row data) by page (0:0).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (6:1907) for object ID 1922105888, index ID 2, partition ID 72057594100318208, alloc unit ID 72057594211205120 (type In-row data) is linked in the IAM chain for object ID 1858105660, index ID 2, partition ID 72057594099007488, alloc unit ID 72057594210156544 (type In-row data) by page (0:0).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:14) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1922105888, index ID 0, partition ID 72057594100187136, alloc unit ID 72057594211008512 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1922105888, index ID 2, partition ID 72057594100318208, alloc unit ID 72057594211205120 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 4 allocation errors and 4 consistency errors in table 'HUM_ETL.GHIS_Procedure_Table_b_ProcedureCode' (object ID 1922105888).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:204) in object ID 1938105945, index ID 0, partition ID 72057594100514816, alloc unit ID 72057594211270656 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:4306) is pointed to by the next pointer of IAM page (0:0) in object ID 1938105945, index ID 0, partition ID 72057594100514816, alloc unit ID 72057594211270656 (type In-row data), but it was not detected in the scan.

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (6:15) for object ID 1938105945, index ID 2, partition ID 72057594100645888, alloc unit ID 72057594211467264 (type In-row data) is linked in the IAM chain for object ID 2130106629, index ID 2, partition ID 72057594104578048, alloc unit ID 72057594214875136 (type In-row data) by page (0:0).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:2155) is pointed to by the next pointer of IAM page (0:0) in object ID 1938105945, index ID 2, partition ID 72057594100645888, alloc unit ID 72057594211467264 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:4306) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1938105945, index ID 0, partition ID 72057594100514816, alloc unit ID 72057594211270656 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:2155) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1938105945, index ID 2, partition ID 72057594100645888, alloc unit ID 72057594211467264 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (6:15) for object ID 1938105945, index ID 2, partition ID 72057594100645888, alloc unit ID 72057594211467264 (type In-row data) is linked in the IAM chain for object ID 2130106629, index ID 2, partition ID 72057594104578048, alloc unit ID 72057594214875136 (type In-row data) by page (0:0).

CHECKDB found 4 allocation errors and 5 consistency errors in table 'HUM_ETL.GHIS_Procedure_Table_b_ProcedureCodeDiagnosisCode' (object ID 1938105945).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:676) in object ID 1954106002, index ID 0, partition ID 72057594100842496, alloc unit ID 72057594211532800 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:4476) is pointed to by the next pointer of IAM page (0:0) in object ID 1954106002, index ID 0, partition ID 72057594100842496, alloc unit ID 72057594211532800 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:254) is pointed to by the next pointer of IAM page (0:0) in object ID 1954106002, index ID 2, partition ID 72057594100973568, alloc unit ID 72057594211729408 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:2186) in object ID 1954106002, index ID 2, partition ID 72057594100973568, alloc unit ID 72057594211729408 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:4476) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1954106002, index ID 0, partition ID 72057594100842496, alloc unit ID 72057594211532800 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:254) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1954106002, index ID 2, partition ID 72057594100973568, alloc unit ID 72057594211729408 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 4 allocation errors and 4 consistency errors in table 'HUM_ETL.GHIS_Procedure_Table_b_ProcedureCodeDose' (object ID 1954106002).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:441) is pointed to by the next pointer of IAM page (0:0) in object ID 2002106173, index ID 0, partition ID 72057594101825536, alloc unit ID 72057594212319232 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:4305) in object ID 2002106173, index ID 0, partition ID 72057594101825536, alloc unit ID 72057594212319232 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:1302) is pointed to by the next pointer of IAM page (0:0) in object ID 2002106173, index ID 2, partition ID 72057594101956608, alloc unit ID 72057594212515840 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:2150) in object ID 2002106173, index ID 2, partition ID 72057594101956608, alloc unit ID 72057594212515840 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:441) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 2002106173, index ID 0, partition ID 72057594101825536, alloc unit ID 72057594212319232 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 2002106173, index ID 2, partition ID 72057594101956608, alloc unit ID 72057594212515840 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 4 allocation errors and 3 consistency errors in table 'HUM_ETL.GHIS_Procedure_Table_b_ProcedureCodeNameKey' (object ID 2002106173).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:9477) is pointed to by the next pointer of IAM page (0:0) in object ID 2018106230, index ID 0, partition ID 72057594102153216, alloc unit ID 72057594212581376 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:9933) in object ID 2018106230, index ID 0, partition ID 72057594102153216, alloc unit ID 72057594212581376 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:267) is pointed to by the next pointer of IAM page (0:0) in object ID 2018106230, index ID 2, partition ID 72057594102284288, alloc unit ID 72057594212777984 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:718) in object ID 2018106230, index ID 2, partition ID 72057594102284288, alloc unit ID 72057594212777984 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:9477) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 2018106230, index ID 0, partition ID 72057594102153216, alloc unit ID 72057594212581376 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:267) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 2018106230, index ID 2, partition ID 72057594102284288, alloc unit ID 72057594212777984 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 4 allocation errors and 4 consistency errors in table 'HUM_ETL.GHIS_Procedure_Table_b_ProcedureCodePrompt' (object ID 2018106230).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:9442) is pointed to by the next pointer of IAM page (0:0) in object ID 2034106287, index ID 0, partition ID 72057594102480896, alloc unit ID 72057594212843520 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:10205) in object ID 2034106287, index ID 0, partition ID 72057594102480896, alloc unit ID 72057594212843520 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:264) is pointed to by the next pointer of IAM page (0:0) in object ID 2034106287, index ID 2, partition ID 72057594102611968, alloc unit ID 72057594213040128 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:1170) in object ID 2034106287, index ID 2, partition ID 72057594102611968, alloc unit ID 72057594213040128 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:9442) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 2034106287, index ID 0, partition ID 72057594102480896, alloc unit ID 72057594212843520 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:264) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 2034106287, index ID 2, partition ID 72057594102611968, alloc unit ID 72057594213040128 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 4 allocation errors and 4 consistency errors in table 'HUM_ETL.GHIS_Prompt_Table_b_Prompt' (object ID 2034106287).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:975) is pointed to by the next pointer of IAM page (0:0) in object ID 2050106344, index ID 0, partition ID 72057594102808576, alloc unit ID 72057594213105664 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:1127) in object ID 2050106344, index ID 0, partition ID 72057594102808576, alloc unit ID 72057594213105664 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:807) is pointed to by the next pointer of IAM page (0:0) in object ID 2050106344, index ID 2, partition ID 72057594102939648, alloc unit ID 72057594213367808 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:2416) in object ID 2050106344, index ID 2, partition ID 72057594102939648, alloc unit ID 72057594213367808 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:975) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 2050106344, index ID 0, partition ID 72057594102808576, alloc unit ID 72057594213105664 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:807) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 2050106344, index ID 2, partition ID 72057594102939648, alloc unit ID 72057594213367808 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 4 allocation errors and 4 consistency errors in table 'HUM_ETL.GHIS_Question_Table_b_BooleanQuestion' (object ID 2050106344).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:170) is pointed to by the next pointer of IAM page (0:0) in object ID 2066106401, index ID 0, partition ID 72057594103136256, alloc unit ID 72057594213433344 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:1285) in object ID 2066106401, index ID 0, partition ID 72057594103136256, alloc unit ID 72057594213433344 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:1905) in object ID 2066106401, index ID 2, partition ID 72057594103267328, alloc unit ID 72057594213695488 (type In-row data), but it was not detected in the scan.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 2066106401, index ID 0, partition ID 72057594103136256, alloc unit ID 72057594213433344 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 2066106401, index ID 2, partition ID 72057594103267328, alloc unit ID 72057594213695488 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 3 allocation errors and 2 consistency errors in table 'HUM_ETL.GHIS_Reason_Table_b_Reason' (object ID 2066106401).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:1284) is pointed to by the next pointer of IAM page (0:0) in object ID 2082106458, index ID 0, partition ID 72057594103463936, alloc unit ID 72057594213761024 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:9445) in object ID 2082106458, index ID 0, partition ID 72057594103463936, alloc unit ID 72057594213761024 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:294) is pointed to by the next pointer of IAM page (0:0) in object ID 2082106458, index ID 2, partition ID 72057594103595008, alloc unit ID 72057594214023168 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:2188) in object ID 2082106458, index ID 2, partition ID 72057594103595008, alloc unit ID 72057594214023168 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:1284) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 2082106458, index ID 0, partition ID 72057594103463936, alloc unit ID 72057594213761024 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:294) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 2082106458, index ID 2, partition ID 72057594103595008, alloc unit ID 72057594214023168 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 4 allocation errors and 4 consistency errors in table 'HUM_ETL.GHIS_Regimen_Table_b_Regimen' (object ID 2082106458).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:499) in object ID 2098106515, index ID 0, partition ID 72057594103791616, alloc unit ID 72057594214088704 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:9874) is pointed to by the next pointer of IAM page (0:0) in object ID 2098106515, index ID 0, partition ID 72057594103791616, alloc unit ID 72057594214088704 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:210) in object ID 2098106515, index ID 2, partition ID 72057594103922688, alloc unit ID 72057594214285312 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:806) is pointed to by the next pointer of IAM page (0:0) in object ID 2098106515, index ID 2, partition ID 72057594103922688, alloc unit ID 72057594214285312 (type In-row data), but it was not detected in the scan.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 2098106515, index ID 0, partition ID 72057594103791616, alloc unit ID 72057594214088704 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (6:806) has invalid IAM_PAGE page header values. Type is 2. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 2098106515, index ID 2, partition ID 72057594103922688, alloc unit ID 72057594214285312 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 4 allocation errors and 3 consistency errors in table 'HUM_ETL.GHIS_Regimen_Table_b_RegimenBooleanQuestion' (object ID 2098106515).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:1774) in object ID 2114106572, index ID 0, partition ID 72057594104119296, alloc unit ID 72057594214350848 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:9910) is pointed to by the next pointer of IAM page (0:0) in object ID 2114106572, index ID 0, partition ID 72057594104119296, alloc unit ID 72057594214350848 (type In-row data), but it was not detected in the scan.

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (6:676) for object ID 2114106572, index ID 2, partition ID 72057594104250368, alloc unit ID 72057594214612992 (type In-row data) is linked in the IAM chain for object ID 46623209, index ID 2, partition ID 72057594105888768, alloc unit ID 72057594216054784 (type In-row data) by page (0:0).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (6:1109) is pointed to by the next pointer of IAM page (0:0) in object ID 2114106572, index ID 2, partition ID 72057594104250368, alloc unit ID 72057594214612992 (type In-row data), but it was not detected in the scan.

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (6:676) for object ID 2114106572, index ID 2, partition ID 72057594104250368, alloc unit ID 72057594214612992 (type In-row data) is linked in the IAM chain for object ID 46623209, index ID 2, partition ID 72057594105888768, alloc unit ID 72057594216054784 (type In-row data) by page (0:0).

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 2114106572, index ID 0, partition ID 72057594104119296, alloc unit ID 72057594214350848 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 2114106572, index ID 2, partition ID 72057594104250368, alloc unit ID 72057594214612992 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 4 allocation errors and 3 consistency errors in table 'HUM_ETL.GHIS_Regimen_Table_b_RegimenBooleanQuestionHistory' (object ID 2114106572).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:241) is pointed to by the next pointer of IAM page (0:0) in object ID 2130106629, index ID 0, partition ID 72057594104446976, alloc unit ID 72057594214678528 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:7642) in object ID 2130106629, index ID 0, partition ID 72057594104446976, alloc unit ID 72057594214678528 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (6:5802) in object ID 2130106629, index ID 2, partition ID 72057594104578048, alloc unit ID 72057594214875136 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:241) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 2130106629, index ID 0, partition ID 72057594104446976, alloc unit ID 72057594214678528 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 2130106629, index ID 2, partition ID 72057594104578048, alloc unit ID 72057594214875136 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 3 allocation errors and 3 consistency errors in table 'HUM_ETL.GHIS_Regimen_Table_b_RegimenBooleanQuestionRegimen' (object ID 2130106629).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:17) is pointed to by the next pointer of IAM page (0:0) in object ID 2146106686, index ID 0, partition ID 72057594104774656, alloc unit ID 72057594214940672 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:15746) in object ID 2146106686, index ID 0, partition ID 72057594104774656, alloc unit ID 72057594214940672 (type In-row data), but it was not detected in the scan.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 2146106686, index ID 0, partition ID 72057594104774656, alloc unit ID 72057594214940672 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 1 consistency errors in table 'HUM_ETL.GHIS_Regimen_Table_b_RegimenGroup' (object ID 2146106686).

CHECKDB found 235 allocation errors and 250 consistency errors in database 'EDW_HUM_Cache'.

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

Database 2

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:664) for object ID 7671075, index ID 0, partition ID 72057594151763968, alloc unit ID 72057594238795776 (type In-row data) is linked in the IAM chain for object ID 1931153925, index ID 0, partition ID 72057594148093952, alloc unit ID 72057594236043264 (type In-row data) by page (0:0).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:4445) is pointed to by the next pointer of IAM page (0:0) in object ID 7671075, index ID 0, partition ID 72057594151763968, alloc unit ID 72057594238795776 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:4445) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 7671075, index ID 0, partition ID 72057594151763968, alloc unit ID 72057594238795776 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:664) for object ID 7671075, index ID 0, partition ID 72057594151763968, alloc unit ID 72057594238795776 (type In-row data) is linked in the IAM chain for object ID 1931153925, index ID 0, partition ID 72057594148093952, alloc unit ID 72057594236043264 (type In-row data) by page (0:0).

CHECKDB found 2 allocation errors and 3 consistency errors in table 'ShoreTel_ETL.Config_b_eventfilters' (object ID 7671075).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:163) is pointed to by the next pointer of IAM page (0:0) in object ID 23671132, index ID 0, partition ID 72057594152026112, alloc unit ID 72057594238992384 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:4325) in object ID 23671132, index ID 0, partition ID 72057594152026112, alloc unit ID 72057594238992384 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:163) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 23671132, index ID 0, partition ID 72057594152026112, alloc unit ID 72057594238992384 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_eventtypes' (object ID 23671132).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:165) is pointed to by the next pointer of IAM page (0:0) in object ID 39671189, index ID 0, partition ID 72057594152288256, alloc unit ID 72057594239188992 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:4329) in object ID 39671189, index ID 0, partition ID 72057594152288256, alloc unit ID 72057594239188992 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:165) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 39671189, index ID 0, partition ID 72057594152288256, alloc unit ID 72057594239188992 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_extensionlistitems' (object ID 39671189).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:161) is pointed to by the next pointer of IAM page (0:0) in object ID 55671246, index ID 0, partition ID 72057594152550400, alloc unit ID 72057594239385600 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:17770) in object ID 55671246, index ID 0, partition ID 72057594152550400, alloc unit ID 72057594239385600 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:161) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 55671246, index ID 0, partition ID 72057594152550400, alloc unit ID 72057594239385600 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_extensionlists' (object ID 55671246).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:424) in object ID 87671360, index ID 0, partition ID 72057594153074688, alloc unit ID 72057594239778816 (type In-row data), but it was not detected in the scan.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 87671360, index ID 0, partition ID 72057594153074688, alloc unit ID 72057594239778816 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 1 allocation errors and 1 consistency errors in table 'ShoreTel_ETL.Config_b_faxsupporttypes' (object ID 87671360).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:4294) for object ID 103671417, index ID 0, partition ID 72057594153336832, alloc unit ID 72057594239975424 (type In-row data) is linked in the IAM chain for object ID 2091154495, index ID 0, partition ID 72057594150715392, alloc unit ID 72057594238009344 (type In-row data) by page (0:0).

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 103671417, index ID 0, partition ID 72057594153336832, alloc unit ID 72057594239975424 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:4294) for object ID 103671417, index ID 0, partition ID 72057594153336832, alloc unit ID 72057594239975424 (type In-row data) is linked in the IAM chain for object ID 2091154495, index ID 0, partition ID 72057594150715392, alloc unit ID 72057594238009344 (type In-row data) by page (0:0).

CHECKDB found 1 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_framingtypes' (object ID 103671417).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:204) for object ID 119671474, index ID 0, partition ID 72057594153598976, alloc unit ID 72057594240172032 (type In-row data) is linked in the IAM chain for object ID 519672899, index ID 0, partition ID 72057594160152576, alloc unit ID 72057594245152768 (type In-row data) by page (0:0).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:3727) is pointed to by the next pointer of IAM page (0:0) in object ID 119671474, index ID 0, partition ID 72057594153598976, alloc unit ID 72057594240172032 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:3727) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 119671474, index ID 0, partition ID 72057594153598976, alloc unit ID 72057594240172032 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:204) for object ID 119671474, index ID 0, partition ID 72057594153598976, alloc unit ID 72057594240172032 (type In-row data) is linked in the IAM chain for object ID 519672899, index ID 0, partition ID 72057594160152576, alloc unit ID 72057594245152768 (type In-row data) by page (0:0).

CHECKDB found 2 allocation errors and 3 consistency errors in table 'ShoreTel_ETL.Config_b_functioncategories' (object ID 119671474).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:187) is pointed to by the next pointer of IAM page (0:0) in object ID 135671531, index ID 0, partition ID 72057594153861120, alloc unit ID 72057594240368640 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:4436) in object ID 135671531, index ID 0, partition ID 72057594153861120, alloc unit ID 72057594240368640 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:187) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 135671531, index ID 0, partition ID 72057594153861120, alloc unit ID 72057594240368640 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_functions' (object ID 135671531).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:339) for object ID 167671645, index ID 0, partition ID 72057594154385408, alloc unit ID 72057594240761856 (type In-row data) is linked in the IAM chain for object ID 727673640, index ID 0, partition ID 72057594163560448, alloc unit ID 72057594247708672 (type In-row data) by page (0:0).

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 167671645, index ID 0, partition ID 72057594154385408, alloc unit ID 72057594240761856 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:339) for object ID 167671645, index ID 0, partition ID 72057594154385408, alloc unit ID 72057594240761856 (type In-row data) is linked in the IAM chain for object ID 727673640, index ID 0, partition ID 72057594163560448, alloc unit ID 72057594247708672 (type In-row data) by page (0:0).

CHECKDB found 1 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_hardwareversions' (object ID 167671645).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:417) in object ID 183671702, index ID 0, partition ID 72057594154647552, alloc unit ID 72057594240958464 (type In-row data), but it was not detected in the scan.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 183671702, index ID 0, partition ID 72057594154647552, alloc unit ID 72057594240958464 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 1 allocation errors and 1 consistency errors in table 'ShoreTel_ETL.Config_b_huntandpagingfeatures' (object ID 183671702).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:176) in object ID 199671759, index ID 0, partition ID 72057594154909696, alloc unit ID 72057594241155072 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:4288) is pointed to by the next pointer of IAM page (0:0) in object ID 199671759, index ID 0, partition ID 72057594154909696, alloc unit ID 72057594241155072 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:4288) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 199671759, index ID 0, partition ID 72057594154909696, alloc unit ID 72057594241155072 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_huntgroupmembers' (object ID 199671759).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:407) in object ID 215671816, index ID 0, partition ID 72057594155171840, alloc unit ID 72057594241351680 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:4327) is pointed to by the next pointer of IAM page (0:0) in object ID 215671816, index ID 0, partition ID 72057594155171840, alloc unit ID 72057594241351680 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:4327) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 215671816, index ID 0, partition ID 72057594155171840, alloc unit ID 72057594241351680 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_huntpatterntypes' (object ID 215671816).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:4235) in object ID 231671873, index ID 0, partition ID 72057594155433984, alloc unit ID 72057594241548288 (type In-row data), but it was not detected in the scan.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 231671873, index ID 0, partition ID 72057594155433984, alloc unit ID 72057594241548288 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 1 allocation errors and 1 consistency errors in table 'ShoreTel_ETL.Config_b_improtocols' (object ID 231671873).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:17772) in object ID 263671987, index ID 0, partition ID 72057594155958272, alloc unit ID 72057594241941504 (type In-row data), but it was not detected in the scan.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 263671987, index ID 0, partition ID 72057594155958272, alloc unit ID 72057594241941504 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 1 allocation errors and 1 consistency errors in table 'ShoreTel_ETL.Config_b_imservertypeprotocolmap' (object ID 263671987).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:210) is pointed to by the next pointer of IAM page (0:0) in object ID 279672044, index ID 0, partition ID 72057594156220416, alloc unit ID 72057594242138112 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:227) in object ID 279672044, index ID 0, partition ID 72057594156220416, alloc unit ID 72057594242138112 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:210) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 279672044, index ID 0, partition ID 72057594156220416, alloc unit ID 72057594242138112 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_imservertypes' (object ID 279672044).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:354) for object ID 295672101, index ID 0, partition ID 72057594156482560, alloc unit ID 72057594242334720 (type In-row data) is linked in the IAM chain for object ID 87671360, index ID 0, partition ID 72057594153074688, alloc unit ID 72057594239778816 (type In-row data) by page (0:0).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:354) for object ID 295672101, index ID 0, partition ID 72057594156482560, alloc unit ID 72057594242334720 (type In-row data) is linked in the IAM chain for object ID 87671360, index ID 0, partition ID 72057594153074688, alloc unit ID 72057594239778816 (type In-row data) by page (0:0).

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 295672101, index ID 0, partition ID 72057594156482560, alloc unit ID 72057594242334720 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 1 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_keypadtypes' (object ID 295672101).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:419) is pointed to by the next pointer of IAM page (0:0) in object ID 311672158, index ID 0, partition ID 72057594156744704, alloc unit ID 72057594242531328 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:3877) in object ID 311672158, index ID 0, partition ID 72057594156744704, alloc unit ID 72057594242531328 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:419) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 311672158, index ID 0, partition ID 72057594156744704, alloc unit ID 72057594242531328 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_languages' (object ID 311672158).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:4279) is pointed to by the next pointer of IAM page (0:0) in object ID 327672215, index ID 0, partition ID 72057594157006848, alloc unit ID 72057594242727936 (type In-row data), but it was not detected in the scan.

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:4311) for object ID 327672215, index ID 0, partition ID 72057594157006848, alloc unit ID 72057594242727936 (type In-row data) is linked in the IAM chain for object ID 471672728, index ID 0, partition ID 72057594159366144, alloc unit ID 72057594244497408 (type In-row data) by page (0:0).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:4279) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 327672215, index ID 0, partition ID 72057594157006848, alloc unit ID 72057594242727936 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:4311) for object ID 327672215, index ID 0, partition ID 72057594157006848, alloc unit ID 72057594242727936 (type In-row data) is linked in the IAM chain for object ID 471672728, index ID 0, partition ID 72057594159366144, alloc unit ID 72057594244497408 (type In-row data) by page (0:0).

CHECKDB found 2 allocation errors and 3 consistency errors in table 'ShoreTel_ETL.Config_b_lbotypes' (object ID 327672215).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:297) for object ID 343672272, index ID 0, partition ID 72057594157268992, alloc unit ID 72057594242924544 (type In-row data) is linked in the IAM chain for object ID 615673241, index ID 0, partition ID 72057594161725440, alloc unit ID 72057594246332416 (type In-row data) by page (0:0).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:4320) is pointed to by the next pointer of IAM page (0:0) in object ID 343672272, index ID 0, partition ID 72057594157268992, alloc unit ID 72057594242924544 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:4320) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 343672272, index ID 0, partition ID 72057594157268992, alloc unit ID 72057594242924544 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:297) for object ID 343672272, index ID 0, partition ID 72057594157268992, alloc unit ID 72057594242924544 (type In-row data) is linked in the IAM chain for object ID 615673241, index ID 0, partition ID 72057594161725440, alloc unit ID 72057594246332416 (type In-row data) by page (0:0).

CHECKDB found 2 allocation errors and 3 consistency errors in table 'ShoreTel_ETL.Config_b_licensekeys' (object ID 343672272).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:395) in object ID 359672329, index ID 0, partition ID 72057594157531136, alloc unit ID 72057594243121152 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:17773) is pointed to by the next pointer of IAM page (0:0) in object ID 359672329, index ID 0, partition ID 72057594157531136, alloc unit ID 72057594243121152 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:17773) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 359672329, index ID 0, partition ID 72057594157531136, alloc unit ID 72057594243121152 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_licenses' (object ID 359672329).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:229) is pointed to by the next pointer of IAM page (0:0) in object ID 375672386, index ID 0, partition ID 72057594157793280, alloc unit ID 72057594243317760 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:524) in object ID 375672386, index ID 0, partition ID 72057594157793280, alloc unit ID 72057594243317760 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:229) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 375672386, index ID 0, partition ID 72057594157793280, alloc unit ID 72057594243317760 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_linecodingtypes' (object ID 375672386).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:216) is pointed to by the next pointer of IAM page (0:0) in object ID 423672557, index ID 0, partition ID 72057594158579712, alloc unit ID 72057594243907584 (type In-row data), but it was not detected in the scan.

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:337) for object ID 423672557, index ID 0, partition ID 72057594158579712, alloc unit ID 72057594243907584 (type In-row data) is linked in the IAM chain for object ID 295672101, index ID 0, partition ID 72057594156482560, alloc unit ID 72057594242334720 (type In-row data) by page (0:0).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:337) for object ID 423672557, index ID 0, partition ID 72057594158579712, alloc unit ID 72057594243907584 (type In-row data) is linked in the IAM chain for object ID 295672101, index ID 0, partition ID 72057594156482560, alloc unit ID 72057594242334720 (type In-row data) by page (0:0).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:216) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 423672557, index ID 0, partition ID 72057594158579712, alloc unit ID 72057594243907584 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 3 consistency errors in table 'ShoreTel_ETL.Config_b_mailboxes' (object ID 423672557).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:4266) is pointed to by the next pointer of IAM page (0:0) in object ID 455672671, index ID 0, partition ID 72057594159104000, alloc unit ID 72057594244300800 (type In-row data), but it was not detected in the scan.

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:4459) for object ID 455672671, index ID 0, partition ID 72057594159104000, alloc unit ID 72057594244300800 (type In-row data) is linked in the IAM chain for object ID 231671873, index ID 0, partition ID 72057594155433984, alloc unit ID 72057594241548288 (type In-row data) by page (0:0).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:4459) for object ID 455672671, index ID 0, partition ID 72057594159104000, alloc unit ID 72057594244300800 (type In-row data) is linked in the IAM chain for object ID 231671873, index ID 0, partition ID 72057594155433984, alloc unit ID 72057594241548288 (type In-row data) by page (0:0).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:4266) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 455672671, index ID 0, partition ID 72057594159104000, alloc unit ID 72057594244300800 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 3 consistency errors in table 'ShoreTel_ETL.Config_b_menus' (object ID 455672671).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:311) for object ID 471672728, index ID 0, partition ID 72057594159366144, alloc unit ID 72057594244497408 (type In-row data) is linked in the IAM chain for object ID 263671987, index ID 0, partition ID 72057594155958272, alloc unit ID 72057594241941504 (type In-row data) by page (0:0).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:311) for object ID 471672728, index ID 0, partition ID 72057594159366144, alloc unit ID 72057594244497408 (type In-row data) is linked in the IAM chain for object ID 263671987, index ID 0, partition ID 72057594155958272, alloc unit ID 72057594241941504 (type In-row data) by page (0:0).

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 471672728, index ID 0, partition ID 72057594159366144, alloc unit ID 72057594244497408 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 1 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_nearbyareacodes' (object ID 471672728).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:196) is pointed to by the next pointer of IAM page (0:0) in object ID 487672785, index ID 0, partition ID 72057594159628288, alloc unit ID 72057594311147520 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:328) in object ID 487672785, index ID 0, partition ID 72057594159628288, alloc unit ID 72057594311147520 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:196) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 487672785, index ID 0, partition ID 72057594159628288, alloc unit ID 72057594311147520 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_notificationdata' (object ID 487672785).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:406) for object ID 503672842, index ID 0, partition ID 72057594159890432, alloc unit ID 72057594244956160 (type In-row data) is linked in the IAM chain for object ID 551673013, index ID 0, partition ID 72057594160676864, alloc unit ID 72057594245545984 (type In-row data) by page (0:0).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:4440) is pointed to by the next pointer of IAM page (0:0) in object ID 503672842, index ID 0, partition ID 72057594159890432, alloc unit ID 72057594244956160 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:4440) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 503672842, index ID 0, partition ID 72057594159890432, alloc unit ID 72057594244956160 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:406) for object ID 503672842, index ID 0, partition ID 72057594159890432, alloc unit ID 72057594244956160 (type In-row data) is linked in the IAM chain for object ID 551673013, index ID 0, partition ID 72057594160676864, alloc unit ID 72057594245545984 (type In-row data) by page (0:0).

CHECKDB found 2 allocation errors and 3 consistency errors in table 'ShoreTel_ETL.Config_b_notificationtypes' (object ID 503672842).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:665) in object ID 519672899, index ID 0, partition ID 72057594160152576, alloc unit ID 72057594245152768 (type In-row data), but it was not detected in the scan.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 519672899, index ID 0, partition ID 72057594160152576, alloc unit ID 72057594245152768 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 1 allocation errors and 1 consistency errors in table 'ShoreTel_ETL.Config_b_offsystemextensions' (object ID 519672899).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:4243) for object ID 535672956, index ID 0, partition ID 72057594160414720, alloc unit ID 72057594245349376 (type In-row data) is linked in the IAM chain for object ID 759673754, index ID 0, partition ID 72057594164084736, alloc unit ID 72057594248101888 (type In-row data) by page (0:0).

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 535672956, index ID 0, partition ID 72057594160414720, alloc unit ID 72057594245349376 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:4243) for object ID 535672956, index ID 0, partition ID 72057594160414720, alloc unit ID 72057594245349376 (type In-row data) is linked in the IAM chain for object ID 759673754, index ID 0, partition ID 72057594164084736, alloc unit ID 72057594248101888 (type In-row data) by page (0:0).

CHECKDB found 1 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_opcodes' (object ID 535672956).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:4323) for object ID 551673013, index ID 0, partition ID 72057594160676864, alloc unit ID 72057594245545984 (type In-row data) is linked in the IAM chain for object ID 1175675236, index ID 0, partition ID 72057594170900480, alloc unit ID 72057594253410304 (type In-row data) by page (0:0).

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 551673013, index ID 0, partition ID 72057594160676864, alloc unit ID 72057594245545984 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:4323) for object ID 551673013, index ID 0, partition ID 72057594160676864, alloc unit ID 72057594245545984 (type In-row data) is linked in the IAM chain for object ID 1175675236, index ID 0, partition ID 72057594170900480, alloc unit ID 72057594253410304 (type In-row data) by page (0:0).

CHECKDB found 1 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_osetgmap' (object ID 551673013).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:231) in object ID 583673127, index ID 0, partition ID 72057594161201152, alloc unit ID 72057594245939200 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:4332) is pointed to by the next pointer of IAM page (0:0) in object ID 583673127, index ID 0, partition ID 72057594161201152, alloc unit ID 72057594245939200 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:4332) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 583673127, index ID 0, partition ID 72057594161201152, alloc unit ID 72057594245939200 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_pcmlanguagechoices' (object ID 583673127).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:180) is pointed to by the next pointer of IAM page (0:0) in object ID 599673184, index ID 0, partition ID 72057594161463296, alloc unit ID 72057594246135808 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:415) in object ID 599673184, index ID 0, partition ID 72057594161463296, alloc unit ID 72057594246135808 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:180) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 599673184, index ID 0, partition ID 72057594161463296, alloc unit ID 72057594246135808 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_personaldistributionlistitems' (object ID 599673184).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:4289) for object ID 615673241, index ID 0, partition ID 72057594161725440, alloc unit ID 72057594246332416 (type In-row data) is linked in the IAM chain for object ID 1303675692, index ID 0, partition ID 72057594172997632, alloc unit ID 72057594254983168 (type In-row data) by page (0:0).

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 615673241, index ID 0, partition ID 72057594161725440, alloc unit ID 72057594246332416 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:4289) for object ID 615673241, index ID 0, partition ID 72057594161725440, alloc unit ID 72057594246332416 (type In-row data) is linked in the IAM chain for object ID 1303675692, index ID 0, partition ID 72057594172997632, alloc unit ID 72057594254983168 (type In-row data) by page (0:0).

CHECKDB found 1 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_personaldistributionlists' (object ID 615673241).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:179) for object ID 631673298, index ID 0, partition ID 72057594161987584, alloc unit ID 72057594246529024 (type In-row data) is linked in the IAM chain for object ID 919674324, index ID 0, partition ID 72057594166706176, alloc unit ID 72057594250067968 (type In-row data) by page (0:0).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:398) is pointed to by the next pointer of IAM page (0:0) in object ID 631673298, index ID 0, partition ID 72057594161987584, alloc unit ID 72057594246529024 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:398) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 631673298, index ID 0, partition ID 72057594161987584, alloc unit ID 72057594246529024 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:179) for object ID 631673298, index ID 0, partition ID 72057594161987584, alloc unit ID 72057594246529024 (type In-row data) is linked in the IAM chain for object ID 919674324, index ID 0, partition ID 72057594166706176, alloc unit ID 72057594250067968 (type In-row data) by page (0:0).

CHECKDB found 2 allocation errors and 3 consistency errors in table 'ShoreTel_ETL.Config_b_phonetypes' (object ID 631673298).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:346) for object ID 647673355, index ID 0, partition ID 72057594162249728, alloc unit ID 72057594246725632 (type In-row data) is linked in the IAM chain for object ID 1335675806, index ID 0, partition ID 72057594173521920, alloc unit ID 72057594255441920 (type In-row data) by page (0:0).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:418) is pointed to by the next pointer of IAM page (0:0) in object ID 647673355, index ID 0, partition ID 72057594162249728, alloc unit ID 72057594246725632 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:418) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 647673355, index ID 0, partition ID 72057594162249728, alloc unit ID 72057594246725632 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:346) for object ID 647673355, index ID 0, partition ID 72057594162249728, alloc unit ID 72057594246725632 (type In-row data) is linked in the IAM chain for object ID 1335675806, index ID 0, partition ID 72057594173521920, alloc unit ID 72057594255441920 (type In-row data) by page (0:0).

CHECKDB found 2 allocation errors and 3 consistency errors in table 'ShoreTel_ETL.Config_b_ports' (object ID 647673355).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:455) in object ID 663673412, index ID 0, partition ID 72057594162511872, alloc unit ID 72057594246922240 (type In-row data), but it was not detected in the scan.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 663673412, index ID 0, partition ID 72057594162511872, alloc unit ID 72057594246922240 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 1 allocation errors and 1 consistency errors in table 'ShoreTel_ETL.Config_b_porttypes' (object ID 663673412).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:362) is pointed to by the next pointer of IAM page (0:0) in object ID 711673583, index ID 0, partition ID 72057594163298304, alloc unit ID 72057594247512064 (type In-row data), but it was not detected in the scan.

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:4302) for object ID 711673583, index ID 0, partition ID 72057594163298304, alloc unit ID 72057594247512064 (type In-row data) is linked in the IAM chain for object ID 1623676832, index ID 0, partition ID 72057594178240512, alloc unit ID 72057594259111936 (type In-row data) by page (0:0).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:362) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 711673583, index ID 0, partition ID 72057594163298304, alloc unit ID 72057594247512064 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:4302) for object ID 711673583, index ID 0, partition ID 72057594163298304, alloc unit ID 72057594247512064 (type In-row data) is linked in the IAM chain for object ID 1623676832, index ID 0, partition ID 72057594178240512, alloc unit ID 72057594259111936 (type In-row data) by page (0:0).

CHECKDB found 2 allocation errors and 3 consistency errors in table 'ShoreTel_ETL.Config_b_privateipaddressranges' (object ID 711673583).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:341) for object ID 727673640, index ID 0, partition ID 72057594163560448, alloc unit ID 72057594247708672 (type In-row data) is linked in the IAM chain for object ID 871674153, index ID 0, partition ID 72057594165919744, alloc unit ID 72057594249478144 (type In-row data) by page (0:0).

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 727673640, index ID 0, partition ID 72057594163560448, alloc unit ID 72057594247708672 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:341) for object ID 727673640, index ID 0, partition ID 72057594163560448, alloc unit ID 72057594247708672 (type In-row data) is linked in the IAM chain for object ID 871674153, index ID 0, partition ID 72057594165919744, alloc unit ID 72057594249478144 (type In-row data) by page (0:0).

CHECKDB found 1 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_prompts' (object ID 727673640).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:408) is pointed to by the next pointer of IAM page (0:0) in object ID 743673697, index ID 0, partition ID 72057594163822592, alloc unit ID 72057594247905280 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:527) in object ID 743673697, index ID 0, partition ID 72057594163822592, alloc unit ID 72057594247905280 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:408) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 743673697, index ID 0, partition ID 72057594163822592, alloc unit ID 72057594247905280 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_protocoltypes' (object ID 743673697).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:4434) for object ID 759673754, index ID 0, partition ID 72057594164084736, alloc unit ID 72057594248101888 (type In-row data) is linked in the IAM chain for object ID 663673412, index ID 0, partition ID 72057594162511872, alloc unit ID 72057594246922240 (type In-row data) by page (0:0).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:4434) for object ID 759673754, index ID 0, partition ID 72057594164084736, alloc unit ID 72057594248101888 (type In-row data) is linked in the IAM chain for object ID 663673412, index ID 0, partition ID 72057594162511872, alloc unit ID 72057594246922240 (type In-row data) by page (0:0).

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 759673754, index ID 0, partition ID 72057594164084736, alloc unit ID 72057594248101888 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 1 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_pstnactivationtypes' (object ID 759673754).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:646) in object ID 807673925, index ID 0, partition ID 72057594164871168, alloc unit ID 72057594248691712 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:4275) is pointed to by the next pointer of IAM page (0:0) in object ID 807673925, index ID 0, partition ID 72057594164871168, alloc unit ID 72057594248691712 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:4275) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 807673925, index ID 0, partition ID 72057594164871168, alloc unit ID 72057594248691712 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_ringtones' (object ID 807673925).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:4225) for object ID 823673982, index ID 0, partition ID 72057594165133312, alloc unit ID 72057594248888320 (type In-row data) is linked in the IAM chain for object ID 1687677060, index ID 0, partition ID 72057594179289088, alloc unit ID 72057594259898368 (type In-row data) by page (0:0).

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 823673982, index ID 0, partition ID 72057594165133312, alloc unit ID 72057594248888320 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:4225) for object ID 823673982, index ID 0, partition ID 72057594165133312, alloc unit ID 72057594248888320 (type In-row data) is linked in the IAM chain for object ID 1687677060, index ID 0, partition ID 72057594179289088, alloc unit ID 72057594259898368 (type In-row data) by page (0:0).

CHECKDB found 1 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_scheduleitems' (object ID 823673982).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:4293) in object ID 839674039, index ID 0, partition ID 72057594165395456, alloc unit ID 72057594249084928 (type In-row data), but it was not detected in the scan.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 839674039, index ID 0, partition ID 72057594165395456, alloc unit ID 72057594249084928 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 1 allocation errors and 1 consistency errors in table 'ShoreTel_ETL.Config_b_schedules' (object ID 839674039).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:4351) in object ID 855674096, index ID 0, partition ID 72057594165657600, alloc unit ID 72057594249281536 (type In-row data), but it was not detected in the scan.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 855674096, index ID 0, partition ID 72057594165657600, alloc unit ID 72057594249281536 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 1 allocation errors and 1 consistency errors in table 'ShoreTel_ETL.Config_b_schemetypes' (object ID 855674096).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:221) for object ID 871674153, index ID 0, partition ID 72057594165919744, alloc unit ID 72057594249478144 (type In-row data) is linked in the IAM chain for object ID 1095674951, index ID 0, partition ID 72057594169589760, alloc unit ID 72057594252361728 (type In-row data) by page (0:0).

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 871674153, index ID 0, partition ID 72057594165919744, alloc unit ID 72057594249478144 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:221) for object ID 871674153, index ID 0, partition ID 72057594165919744, alloc unit ID 72057594249478144 (type In-row data) is linked in the IAM chain for object ID 1095674951, index ID 0, partition ID 72057594169589760, alloc unit ID 72057594252361728 (type In-row data) by page (0:0).

CHECKDB found 1 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_scopetypes' (object ID 871674153).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:439) in object ID 903674267, index ID 0, partition ID 72057594166444032, alloc unit ID 72057594249871360 (type In-row data), but it was not detected in the scan.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 903674267, index ID 0, partition ID 72057594166444032, alloc unit ID 72057594249871360 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 1 allocation errors and 1 consistency errors in table 'ShoreTel_ETL.Config_b_sendemailforvmtypes' (object ID 903674267).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:3874) in object ID 919674324, index ID 0, partition ID 72057594166706176, alloc unit ID 72057594250067968 (type In-row data), but it was not detected in the scan.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 919674324, index ID 0, partition ID 72057594166706176, alloc unit ID 72057594250067968 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 1 allocation errors and 1 consistency errors in table 'ShoreTel_ETL.Config_b_shoreteleventcategories' (object ID 919674324).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:449) is pointed to by the next pointer of IAM page (0:0) in object ID 935674381, index ID 0, partition ID 72057594166968320, alloc unit ID 72057594250264576 (type In-row data), but it was not detected in the scan.

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:4278) for object ID 935674381, index ID 0, partition ID 72057594166968320, alloc unit ID 72057594250264576 (type In-row data) is linked in the IAM chain for object ID 951674438, index ID 0, partition ID 72057594167230464, alloc unit ID 72057594250526720 (type In-row data) by page (0:0).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:449) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 935674381, index ID 0, partition ID 72057594166968320, alloc unit ID 72057594250264576 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:4278) for object ID 935674381, index ID 0, partition ID 72057594166968320, alloc unit ID 72057594250264576 (type In-row data) is linked in the IAM chain for object ID 951674438, index ID 0, partition ID 72057594167230464, alloc unit ID 72057594250526720 (type In-row data) by page (0:0).

CHECKDB found 2 allocation errors and 3 consistency errors in table 'ShoreTel_ETL.Config_b_sipprofiles' (object ID 935674381).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:4310) for object ID 951674438, index ID 0, partition ID 72057594167230464, alloc unit ID 72057594250526720 (type In-row data) is linked in the IAM chain for object ID 1383675977, index ID 0, partition ID 72057594174308352, alloc unit ID 72057594256031744 (type In-row data) by page (0:0).

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 951674438, index ID 0, partition ID 72057594167230464, alloc unit ID 72057594250526720 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:4310) for object ID 951674438, index ID 0, partition ID 72057594167230464, alloc unit ID 72057594250526720 (type In-row data) is linked in the IAM chain for object ID 1383675977, index ID 0, partition ID 72057594174308352, alloc unit ID 72057594256031744 (type In-row data) by page (0:0).

CHECKDB found 1 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_sipservers' (object ID 951674438).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:24227) for object ID 967674495, index ID 0, partition ID 72057594167492608, alloc unit ID 72057594250723328 (type In-row data) is linked in the IAM chain for object ID 1639676889, index ID 0, partition ID 72057594178502656, alloc unit ID 72057594259308544 (type In-row data) by page (0:0).

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 967674495, index ID 0, partition ID 72057594167492608, alloc unit ID 72057594250723328 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:24227) for object ID 967674495, index ID 0, partition ID 72057594167492608, alloc unit ID 72057594250723328 (type In-row data) is linked in the IAM chain for object ID 1639676889, index ID 0, partition ID 72057594178502656, alloc unit ID 72057594259308544 (type In-row data) by page (0:0).

CHECKDB found 1 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_sites' (object ID 967674495).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:4454) in object ID 1003150619, index ID 0, partition ID 72057594132889600, alloc unit ID 72057594224574464 (type In-row data), but it was not detected in the scan.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1003150619, index ID 0, partition ID 72057594132889600, alloc unit ID 72057594224574464 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 1 allocation errors and 1 consistency errors in table 'ShoreTel_ETL.Config_b_accountcodetypes' (object ID 1003150619).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:309) for object ID 1015674666, index ID 0, partition ID 72057594168279040, alloc unit ID 72057594251378688 (type In-row data) is linked in the IAM chain for object ID 1207675350, index ID 0, partition ID 72057594171424768, alloc unit ID 72057594253803520 (type In-row data) by page (0:0).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:391) is pointed to by the next pointer of IAM page (0:0) in object ID 1015674666, index ID 0, partition ID 72057594168279040, alloc unit ID 72057594251378688 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:391) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1015674666, index ID 0, partition ID 72057594168279040, alloc unit ID 72057594251378688 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:309) for object ID 1015674666, index ID 0, partition ID 72057594168279040, alloc unit ID 72057594251378688 (type In-row data) is linked in the IAM chain for object ID 1207675350, index ID 0, partition ID 72057594171424768, alloc unit ID 72057594253803520 (type In-row data) by page (0:0).

CHECKDB found 2 allocation errors and 3 consistency errors in table 'ShoreTel_ETL.Config_b_smdiaccesstypes' (object ID 1015674666).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:312) is pointed to by the next pointer of IAM page (0:0) in object ID 1019150676, index ID 0, partition ID 72057594133151744, alloc unit ID 72057594224771072 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:49166) in object ID 1019150676, index ID 0, partition ID 72057594133151744, alloc unit ID 72057594224771072 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:312) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1019150676, index ID 0, partition ID 72057594133151744, alloc unit ID 72057594224771072 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_adminroleattributes' (object ID 1019150676).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:413) is pointed to by the next pointer of IAM page (0:0) in object ID 1031674723, index ID 0, partition ID 72057594168541184, alloc unit ID 72057594251575296 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:421) in object ID 1031674723, index ID 0, partition ID 72057594168541184, alloc unit ID 72057594251575296 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:413) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1031674723, index ID 0, partition ID 72057594168541184, alloc unit ID 72057594251575296 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_smdimodetypes' (object ID 1031674723).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:188) in object ID 1035150733, index ID 0, partition ID 72057594133413888, alloc unit ID 72057594224967680 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:370) is pointed to by the next pointer of IAM page (0:0) in object ID 1035150733, index ID 0, partition ID 72057594133413888, alloc unit ID 72057594224967680 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:370) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1035150733, index ID 0, partition ID 72057594133413888, alloc unit ID 72057594224967680 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_adminroleattributessetting' (object ID 1035150733).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:651) in object ID 1047674780, index ID 0, partition ID 72057594168803328, alloc unit ID 72057594251771904 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:4231) is pointed to by the next pointer of IAM page (0:0) in object ID 1047674780, index ID 0, partition ID 72057594168803328, alloc unit ID 72057594251771904 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:4231) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1047674780, index ID 0, partition ID 72057594168803328, alloc unit ID 72057594251771904 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_smdiusertypes' (object ID 1047674780).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:217) in object ID 1051150790, index ID 0, partition ID 72057594133676032, alloc unit ID 72057594225164288 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:453) is pointed to by the next pointer of IAM page (0:0) in object ID 1051150790, index ID 0, partition ID 72057594133676032, alloc unit ID 72057594225164288 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:453) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1051150790, index ID 0, partition ID 72057594133676032, alloc unit ID 72057594225164288 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_adminrolepermissions' (object ID 1051150790).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:303) in object ID 1067150847, index ID 0, partition ID 72057594133938176, alloc unit ID 72057594225360896 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:3721) is pointed to by the next pointer of IAM page (0:0) in object ID 1067150847, index ID 0, partition ID 72057594133938176, alloc unit ID 72057594225360896 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:3721) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1067150847, index ID 0, partition ID 72057594133938176, alloc unit ID 72057594225360896 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_adminroles' (object ID 1067150847).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:4448) for object ID 1095674951, index ID 0, partition ID 72057594169589760, alloc unit ID 72057594252361728 (type In-row data) is linked in the IAM chain for object ID 1271675578, index ID 0, partition ID 72057594172473344, alloc unit ID 72057594254589952 (type In-row data) by page (0:0).

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1095674951, index ID 0, partition ID 72057594169589760, alloc unit ID 72057594252361728 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:4448) for object ID 1095674951, index ID 0, partition ID 72057594169589760, alloc unit ID 72057594252361728 (type In-row data) is linked in the IAM chain for object ID 1271675578, index ID 0, partition ID 72057594172473344, alloc unit ID 72057594254589952 (type In-row data) by page (0:0).

CHECKDB found 1 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_speeddials' (object ID 1095674951).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:330) for object ID 1111675008, index ID 0, partition ID 72057594169851904, alloc unit ID 72057594252558336 (type In-row data) is linked in the IAM chain for object ID 823673982, index ID 0, partition ID 72057594165133312, alloc unit ID 72057594248888320 (type In-row data) by page (0:0).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:388) is pointed to by the next pointer of IAM page (0:0) in object ID 1111675008, index ID 0, partition ID 72057594169851904, alloc unit ID 72057594252558336 (type In-row data), but it was not detected in the scan.

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:330) for object ID 1111675008, index ID 0, partition ID 72057594169851904, alloc unit ID 72057594252558336 (type In-row data) is linked in the IAM chain for object ID 823673982, index ID 0, partition ID 72057594165133312, alloc unit ID 72057594248888320 (type In-row data) by page (0:0).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:388) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1111675008, index ID 0, partition ID 72057594169851904, alloc unit ID 72057594252558336 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 3 consistency errors in table 'ShoreTel_ETL.Config_b_submenuitems' (object ID 1111675008).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:529) in object ID 1127675065, index ID 0, partition ID 72057594170114048, alloc unit ID 72057594252754944 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:3725) is pointed to by the next pointer of IAM page (0:0) in object ID 1127675065, index ID 0, partition ID 72057594170114048, alloc unit ID 72057594252754944 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:3725) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1127675065, index ID 0, partition ID 72057594170114048, alloc unit ID 72057594252754944 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_submenus' (object ID 1127675065).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:353) is pointed to by the next pointer of IAM page (0:0) in object ID 1131151075, index ID 0, partition ID 72057594134986752, alloc unit ID 72057594226147328 (type In-row data), but it was not detected in the scan.

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:4305) for object ID 1131151075, index ID 0, partition ID 72057594134986752, alloc unit ID 72057594226147328 (type In-row data) is linked in the IAM chain for object ID 1227151417, index ID 0, partition ID 72057594136559616, alloc unit ID 72057594227326976 (type In-row data) by page (0:0).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:353) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1131151075, index ID 0, partition ID 72057594134986752, alloc unit ID 72057594226147328 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:4305) for object ID 1131151075, index ID 0, partition ID 72057594134986752, alloc unit ID 72057594226147328 (type In-row data) is linked in the IAM chain for object ID 1227151417, index ID 0, partition ID 72057594136559616, alloc unit ID 72057594227326976 (type In-row data) by page (0:0).

CHECKDB found 2 allocation errors and 3 consistency errors in table 'ShoreTel_ETL.Config_b_adminrolessitesmap' (object ID 1131151075).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:327) in object ID 1143675122, index ID 0, partition ID 72057594170376192, alloc unit ID 72057594253017088 (type In-row data), but it was not detected in the scan.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1143675122, index ID 0, partition ID 72057594170376192, alloc unit ID 72057594253017088 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 1 allocation errors and 1 consistency errors in table 'ShoreTel_ETL.Config_b_switches' (object ID 1143675122).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:390) in object ID 1159675179, index ID 0, partition ID 72057594170638336, alloc unit ID 72057594253213696 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:416) is pointed to by the next pointer of IAM page (0:0) in object ID 1159675179, index ID 0, partition ID 72057594170638336, alloc unit ID 72057594253213696 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:416) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1159675179, index ID 0, partition ID 72057594170638336, alloc unit ID 72057594253213696 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_switchgroupipaddressranges' (object ID 1159675179).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:526) is pointed to by the next pointer of IAM page (0:0) in object ID 1163151189, index ID 0, partition ID 72057594135511040, alloc unit ID 72057594226540544 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:49164) in object ID 1163151189, index ID 0, partition ID 72057594135511040, alloc unit ID 72057594226540544 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:526) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1163151189, index ID 0, partition ID 72057594135511040, alloc unit ID 72057594226540544 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_adminrolesusersmap' (object ID 1163151189).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:451) in object ID 1175675236, index ID 0, partition ID 72057594170900480, alloc unit ID 72057594253410304 (type In-row data), but it was not detected in the scan.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1175675236, index ID 0, partition ID 72057594170900480, alloc unit ID 72057594253410304 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 1 allocation errors and 1 consistency errors in table 'ShoreTel_ETL.Config_b_switchgroups' (object ID 1175675236).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:3726) in object ID 1191675293, index ID 0, partition ID 72057594171162624, alloc unit ID 72057594253606912 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:17771) is pointed to by the next pointer of IAM page (0:0) in object ID 1191675293, index ID 0, partition ID 72057594171162624, alloc unit ID 72057594253606912 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:17771) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1191675293, index ID 0, partition ID 72057594171162624, alloc unit ID 72057594253606912 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_switchinterfaces' (object ID 1191675293).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:4284) for object ID 1207675350, index ID 0, partition ID 72057594171424768, alloc unit ID 72057594253803520 (type In-row data) is linked in the IAM chain for object ID 1255675521, index ID 0, partition ID 72057594172211200, alloc unit ID 72057594254393344 (type In-row data) by page (0:0).

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1207675350, index ID 0, partition ID 72057594171424768, alloc unit ID 72057594253803520 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:4284) for object ID 1207675350, index ID 0, partition ID 72057594171424768, alloc unit ID 72057594253803520 (type In-row data) is linked in the IAM chain for object ID 1255675521, index ID 0, partition ID 72057594172211200, alloc unit ID 72057594254393344 (type In-row data) by page (0:0).

CHECKDB found 1 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_switchinterfacetypecotypemap' (object ID 1207675350).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:302) in object ID 1211151360, index ID 0, partition ID 72057594136297472, alloc unit ID 72057594227130368 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:4297) is pointed to by the next pointer of IAM page (0:0) in object ID 1211151360, index ID 0, partition ID 72057594136297472, alloc unit ID 72057594227130368 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:4297) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1211151360, index ID 0, partition ID 72057594136297472, alloc unit ID 72057594227130368 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_areacodeexceptions' (object ID 1211151360).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:438) is pointed to by the next pointer of IAM page (0:0) in object ID 1223675407, index ID 0, partition ID 72057594171686912, alloc unit ID 72057594254000128 (type In-row data), but it was not detected in the scan.

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:4346) for object ID 1223675407, index ID 0, partition ID 72057594171686912, alloc unit ID 72057594254000128 (type In-row data) is linked in the IAM chain for object ID 1143675122, index ID 0, partition ID 72057594170376192, alloc unit ID 72057594253017088 (type In-row data) by page (0:0).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:4346) for object ID 1223675407, index ID 0, partition ID 72057594171686912, alloc unit ID 72057594254000128 (type In-row data) is linked in the IAM chain for object ID 1143675122, index ID 0, partition ID 72057594170376192, alloc unit ID 72057594253017088 (type In-row data) by page (0:0).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:438) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1223675407, index ID 0, partition ID 72057594171686912, alloc unit ID 72057594254000128 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 3 consistency errors in table 'ShoreTel_ETL.Config_b_switchinterfacetypeframingtypemap' (object ID 1223675407).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:325) in object ID 1227151417, index ID 0, partition ID 72057594136559616, alloc unit ID 72057594227326976 (type In-row data), but it was not detected in the scan.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1227151417, index ID 0, partition ID 72057594136559616, alloc unit ID 72057594227326976 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 1 allocation errors and 1 consistency errors in table 'ShoreTel_ETL.Config_b_audiopathtypes' (object ID 1227151417).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:177) for object ID 1239675464, index ID 0, partition ID 72057594171949056, alloc unit ID 72057594254196736 (type In-row data) is linked in the IAM chain for object ID 967674495, index ID 0, partition ID 72057594167492608, alloc unit ID 72057594250723328 (type In-row data) by page (0:0).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:667) is pointed to by the next pointer of IAM page (0:0) in object ID 1239675464, index ID 0, partition ID 72057594171949056, alloc unit ID 72057594254196736 (type In-row data), but it was not detected in the scan.

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:177) for object ID 1239675464, index ID 0, partition ID 72057594171949056, alloc unit ID 72057594254196736 (type In-row data) is linked in the IAM chain for object ID 967674495, index ID 0, partition ID 72057594167492608, alloc unit ID 72057594250723328 (type In-row data) by page (0:0).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:667) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1239675464, index ID 0, partition ID 72057594171949056, alloc unit ID 72057594254196736 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 3 consistency errors in table 'ShoreTel_ETL.Config_b_switchinterfacetypelinecodingtypemap' (object ID 1239675464).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:410) in object ID 1255675521, index ID 0, partition ID 72057594172211200, alloc unit ID 72057594254393344 (type In-row data), but it was not detected in the scan.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1255675521, index ID 0, partition ID 72057594172211200, alloc unit ID 72057594254393344 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 1 allocation errors and 1 consistency errors in table 'ShoreTel_ETL.Config_b_switchinterfacetypeprotocoltypemap' (object ID 1255675521).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:442) for object ID 1271675578, index ID 0, partition ID 72057594172473344, alloc unit ID 72057594254589952 (type In-row data) is linked in the IAM chain for object ID 1527676490, index ID 0, partition ID 72057594176667648, alloc unit ID 72057594257866752 (type In-row data) by page (0:0).

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1271675578, index ID 0, partition ID 72057594172473344, alloc unit ID 72057594254589952 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:442) for object ID 1271675578, index ID 0, partition ID 72057594172473344, alloc unit ID 72057594254589952 (type In-row data) is linked in the IAM chain for object ID 1527676490, index ID 0, partition ID 72057594176667648, alloc unit ID 72057594257866752 (type In-row data) by page (0:0).

CHECKDB found 1 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_switchinterfacetypes' (object ID 1271675578).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:203) is pointed to by the next pointer of IAM page (0:0) in object ID 1275151588, index ID 0, partition ID 72057594137346048, alloc unit ID 72057594227916800 (type In-row data), but it was not detected in the scan.

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:4343) for object ID 1275151588, index ID 0, partition ID 72057594137346048, alloc unit ID 72057594227916800 (type In-row data) is linked in the IAM chain for object ID 1787153412, index ID 0, partition ID 72057594145734656, alloc unit ID 72057594234273792 (type In-row data) by page (0:0).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:203) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1275151588, index ID 0, partition ID 72057594137346048, alloc unit ID 72057594227916800 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:4343) for object ID 1275151588, index ID 0, partition ID 72057594137346048, alloc unit ID 72057594227916800 (type In-row data) is linked in the IAM chain for object ID 1787153412, index ID 0, partition ID 72057594145734656, alloc unit ID 72057594234273792 (type In-row data) by page (0:0).

CHECKDB found 2 allocation errors and 3 consistency errors in table 'ShoreTel_ETL.Config_b_bridgetypes' (object ID 1275151588).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:324) is pointed to by the next pointer of IAM page (0:0) in object ID 1287675635, index ID 0, partition ID 72057594172735488, alloc unit ID 72057594254786560 (type In-row data), but it was not detected in the scan.

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:652) for object ID 1287675635, index ID 0, partition ID 72057594172735488, alloc unit ID 72057594254786560 (type In-row data) is linked in the IAM chain for object ID 1671677003, index ID 0, partition ID 72057594179026944, alloc unit ID 72057594259701760 (type In-row data) by page (0:0).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:324) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1287675635, index ID 0, partition ID 72057594172735488, alloc unit ID 72057594254786560 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:652) for object ID 1287675635, index ID 0, partition ID 72057594172735488, alloc unit ID 72057594254786560 (type In-row data) is linked in the IAM chain for object ID 1671677003, index ID 0, partition ID 72057594179026944, alloc unit ID 72057594259701760 (type In-row data) by page (0:0).

CHECKDB found 2 allocation errors and 3 consistency errors in table 'ShoreTel_ETL.Config_b_switchtypes' (object ID 1287675635).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:4460) in object ID 1291151645, index ID 0, partition ID 72057594137608192, alloc unit ID 72057594228113408 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:49161) is pointed to by the next pointer of IAM page (0:0) in object ID 1291151645, index ID 0, partition ID 72057594137608192, alloc unit ID 72057594228113408 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:49161) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1291151645, index ID 0, partition ID 72057594137608192, alloc unit ID 72057594228113408 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_buddies' (object ID 1291151645).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:437) in object ID 1303675692, index ID 0, partition ID 72057594172997632, alloc unit ID 72057594254983168 (type In-row data), but it was not detected in the scan.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1303675692, index ID 0, partition ID 72057594172997632, alloc unit ID 72057594254983168 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 1 allocation errors and 1 consistency errors in table 'ShoreTel_ETL.Config_b_system' (object ID 1303675692).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:3722) in object ID 1319675749, index ID 0, partition ID 72057594173259776, alloc unit ID 72057594255245312 (type In-row data), but it was not detected in the scan.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1319675749, index ID 0, partition ID 72057594173259776, alloc unit ID 72057594255245312 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 1 allocation errors and 1 consistency errors in table 'ShoreTel_ETL.Config_b_systemex' (object ID 1319675749).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:193) is pointed to by the next pointer of IAM page (0:0) in object ID 1323151759, index ID 0, partition ID 72057594138132480, alloc unit ID 72057594228506624 (type In-row data), but it was not detected in the scan.

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:219) for object ID 1323151759, index ID 0, partition ID 72057594138132480, alloc unit ID 72057594228506624 (type In-row data) is linked in the IAM chain for object ID 1851153640, index ID 0, partition ID 72057594146783232, alloc unit ID 72057594235060224 (type In-row data) by page (0:0).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:193) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1323151759, index ID 0, partition ID 72057594138132480, alloc unit ID 72057594228506624 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:219) for object ID 1323151759, index ID 0, partition ID 72057594138132480, alloc unit ID 72057594228506624 (type In-row data) is linked in the IAM chain for object ID 1851153640, index ID 0, partition ID 72057594146783232, alloc unit ID 72057594235060224 (type In-row data) by page (0:0).

CHECKDB found 2 allocation errors and 3 consistency errors in table 'ShoreTel_ETL.Config_b_buddygroups' (object ID 1323151759).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:4269) for object ID 1335675806, index ID 0, partition ID 72057594173521920, alloc unit ID 72057594255441920 (type In-row data) is linked in the IAM chain for object ID 1367675920, index ID 0, partition ID 72057594174046208, alloc unit ID 72057594255835136 (type In-row data) by page (0:0).

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1335675806, index ID 0, partition ID 72057594173521920, alloc unit ID 72057594255441920 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:4269) for object ID 1335675806, index ID 0, partition ID 72057594173521920, alloc unit ID 72057594255441920 (type In-row data) is linked in the IAM chain for object ID 1367675920, index ID 0, partition ID 72057594174046208, alloc unit ID 72057594255835136 (type In-row data) by page (0:0).

CHECKDB found 1 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_tabaddresses' (object ID 1335675806).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:323) is pointed to by the next pointer of IAM page (0:0) in object ID 1339151816, index ID 0, partition ID 72057594138394624, alloc unit ID 72057594228703232 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:333) in object ID 1339151816, index ID 0, partition ID 72057594138394624, alloc unit ID 72057594228703232 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:323) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1339151816, index ID 0, partition ID 72057594138394624, alloc unit ID 72057594228703232 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_callhandlingmodes' (object ID 1339151816).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:454) is pointed to by the next pointer of IAM page (0:0) in object ID 1351675863, index ID 0, partition ID 72057594173784064, alloc unit ID 72057594255638528 (type In-row data), but it was not detected in the scan.

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:4348) for object ID 1351675863, index ID 0, partition ID 72057594173784064, alloc unit ID 72057594255638528 (type In-row data) is linked in the IAM chain for object ID 1495676376, index ID 0, partition ID 72057594176143360, alloc unit ID 72057594257473536 (type In-row data) by page (0:0).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:454) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1351675863, index ID 0, partition ID 72057594173784064, alloc unit ID 72057594255638528 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:4348) for object ID 1351675863, index ID 0, partition ID 72057594173784064, alloc unit ID 72057594255638528 (type In-row data) is linked in the IAM chain for object ID 1495676376, index ID 0, partition ID 72057594176143360, alloc unit ID 72057594257473536 (type In-row data) by page (0:0).

CHECKDB found 2 allocation errors and 3 consistency errors in table 'ShoreTel_ETL.Config_b_themetypes' (object ID 1351675863).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:642) is pointed to by the next pointer of IAM page (0:0) in object ID 1355151873, index ID 0, partition ID 72057594138656768, alloc unit ID 72057594228899840 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:649) in object ID 1355151873, index ID 0, partition ID 72057594138656768, alloc unit ID 72057594228899840 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:642) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1355151873, index ID 0, partition ID 72057594138656768, alloc unit ID 72057594228899840 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_callstoshowinredialtypes' (object ID 1355151873).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:211) for object ID 1367675920, index ID 0, partition ID 72057594174046208, alloc unit ID 72057594255835136 (type In-row data) is linked in the IAM chain for object ID 1399676034, index ID 0, partition ID 72057594174570496, alloc unit ID 72057594256228352 (type In-row data) by page (0:0).

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1367675920, index ID 0, partition ID 72057594174046208, alloc unit ID 72057594255835136 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:211) for object ID 1367675920, index ID 0, partition ID 72057594174046208, alloc unit ID 72057594255835136 (type In-row data) is linked in the IAM chain for object ID 1399676034, index ID 0, partition ID 72057594174570496, alloc unit ID 72057594256228352 (type In-row data) by page (0:0).

CHECKDB found 1 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_timetypes' (object ID 1367675920).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:676) in object ID 1371151930, index ID 0, partition ID 72057594138918912, alloc unit ID 72057594229096448 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:4240) is pointed to by the next pointer of IAM page (0:0) in object ID 1371151930, index ID 0, partition ID 72057594138918912, alloc unit ID 72057594229096448 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:4240) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1371151930, index ID 0, partition ID 72057594138918912, alloc unit ID 72057594229096448 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_cfconditiontypes' (object ID 1371151930).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:422) in object ID 1383675977, index ID 0, partition ID 72057594174308352, alloc unit ID 72057594256031744 (type In-row data), but it was not detected in the scan.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1383675977, index ID 0, partition ID 72057594174308352, alloc unit ID 72057594256031744 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 1 allocation errors and 1 consistency errors in table 'ShoreTel_ETL.Config_b_toolbarbuttons' (object ID 1383675977).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:4268) in object ID 1387151987, index ID 0, partition ID 72057594139181056, alloc unit ID 72057594229293056 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:4455) is pointed to by the next pointer of IAM page (0:0) in object ID 1387151987, index ID 0, partition ID 72057594139181056, alloc unit ID 72057594229293056 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:4455) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1387151987, index ID 0, partition ID 72057594139181056, alloc unit ID 72057594229293056 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_cfenscopetypes' (object ID 1387151987).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:448) in object ID 1399676034, index ID 0, partition ID 72057594174570496, alloc unit ID 72057594256228352 (type In-row data), but it was not detected in the scan.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1399676034, index ID 0, partition ID 72057594174570496, alloc unit ID 72057594256228352 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 1 allocation errors and 1 consistency errors in table 'ShoreTel_ETL.Config_b_toolbars' (object ID 1399676034).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:679) for object ID 1415676091, index ID 0, partition ID 72057594174832640, alloc unit ID 72057594256424960 (type In-row data) is linked in the IAM chain for object ID 1879677744, index ID 0, partition ID 72057594182434816, alloc unit ID 72057594262257664 (type In-row data) by page (0:0).

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1415676091, index ID 0, partition ID 72057594174832640, alloc unit ID 72057594256424960 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:679) for object ID 1415676091, index ID 0, partition ID 72057594174832640, alloc unit ID 72057594256424960 (type In-row data) is linked in the IAM chain for object ID 1879677744, index ID 0, partition ID 72057594182434816, alloc unit ID 72057594262257664 (type In-row data) by page (0:0).

CHECKDB found 1 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_trunkgroups' (object ID 1415676091).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:4336) for object ID 1419152101, index ID 0, partition ID 72057594139705344, alloc unit ID 72057594229686272 (type In-row data) is linked in the IAM chain for object ID 1643152899, index ID 0, partition ID 72057594143375360, alloc unit ID 72057594232504320 (type In-row data) by page (0:0).

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1419152101, index ID 0, partition ID 72057594139705344, alloc unit ID 72057594229686272 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:4336) for object ID 1419152101, index ID 0, partition ID 72057594139705344, alloc unit ID 72057594229686272 (type In-row data) is linked in the IAM chain for object ID 1643152899, index ID 0, partition ID 72057594143375360, alloc unit ID 72057594232504320 (type In-row data) by page (0:0).

CHECKDB found 1 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_chmdefaults' (object ID 1419152101).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:530) is pointed to by the next pointer of IAM page (0:0) in object ID 1431676148, index ID 0, partition ID 72057594175094784, alloc unit ID 72057594256687104 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:4307) in object ID 1431676148, index ID 0, partition ID 72057594175094784, alloc unit ID 72057594256687104 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:530) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1431676148, index ID 0, partition ID 72057594175094784, alloc unit ID 72057594256687104 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_trunktypes' (object ID 1431676148).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:4439) in object ID 1435152158, index ID 0, partition ID 72057594139967488, alloc unit ID 72057594229882880 (type In-row data), but it was not detected in the scan.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1435152158, index ID 0, partition ID 72057594139967488, alloc unit ID 72057594229882880 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 1 allocation errors and 1 consistency errors in table 'ShoreTel_ETL.Config_b_chmdelegationpolicy' (object ID 1435152158).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:432) in object ID 1447676205, index ID 0, partition ID 72057594175356928, alloc unit ID 72057594256883712 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:650) is pointed to by the next pointer of IAM page (0:0) in object ID 1447676205, index ID 0, partition ID 72057594175356928, alloc unit ID 72057594256883712 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:650) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1447676205, index ID 0, partition ID 72057594175356928, alloc unit ID 72057594256883712 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_types4ess' (object ID 1447676205).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:166) in object ID 1451152215, index ID 0, partition ID 72057594140229632, alloc unit ID 72057594230079488 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:365) is pointed to by the next pointer of IAM page (0:0) in object ID 1451152215, index ID 0, partition ID 72057594140229632, alloc unit ID 72057594230079488 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:365) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1451152215, index ID 0, partition ID 72057594140229632, alloc unit ID 72057594230079488 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_chmtypes' (object ID 1451152215).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:215) in object ID 1467152272, index ID 0, partition ID 72057594140491776, alloc unit ID 72057594230276096 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:305) is pointed to by the next pointer of IAM page (0:0) in object ID 1467152272, index ID 0, partition ID 72057594140491776, alloc unit ID 72057594230276096 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:305) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1467152272, index ID 0, partition ID 72057594140491776, alloc unit ID 72057594230276096 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_clockingtypes' (object ID 1467152272).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:230) in object ID 1483152329, index ID 0, partition ID 72057594140753920, alloc unit ID 72057594230472704 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:446) is pointed to by the next pointer of IAM page (0:0) in object ID 1483152329, index ID 0, partition ID 72057594140753920, alloc unit ID 72057594230472704 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:446) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1483152329, index ID 0, partition ID 72057594140753920, alloc unit ID 72057594230472704 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_codeclistitems' (object ID 1483152329).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:4291) for object ID 1495676376, index ID 0, partition ID 72057594176143360, alloc unit ID 72057594257473536 (type In-row data) is linked in the IAM chain for object ID 1895677801, index ID 0, partition ID 72057594182696960, alloc unit ID 72057594262454272 (type In-row data) by page (0:0).

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1495676376, index ID 0, partition ID 72057594176143360, alloc unit ID 72057594257473536 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:4291) for object ID 1495676376, index ID 0, partition ID 72057594176143360, alloc unit ID 72057594257473536 (type In-row data) is linked in the IAM chain for object ID 1895677801, index ID 0, partition ID 72057594182696960, alloc unit ID 72057594262454272 (type In-row data) by page (0:0).

CHECKDB found 1 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_ugwallpapers' (object ID 1495676376).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:433) for object ID 1515152443, index ID 0, partition ID 72057594141278208, alloc unit ID 72057594230865920 (type In-row data) is linked in the IAM chain for object ID 103671417, index ID 0, partition ID 72057594153336832, alloc unit ID 72057594239975424 (type In-row data) by page (0:0).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:653) is pointed to by the next pointer of IAM page (0:0) in object ID 1515152443, index ID 0, partition ID 72057594141278208, alloc unit ID 72057594230865920 (type In-row data), but it was not detected in the scan.

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:433) for object ID 1515152443, index ID 0, partition ID 72057594141278208, alloc unit ID 72057594230865920 (type In-row data) is linked in the IAM chain for object ID 103671417, index ID 0, partition ID 72057594153336832, alloc unit ID 72057594239975424 (type In-row data) by page (0:0).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:653) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1515152443, index ID 0, partition ID 72057594141278208, alloc unit ID 72057594230865920 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 3 consistency errors in table 'ShoreTel_ETL.Config_b_codecs' (object ID 1515152443).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:214) in object ID 1527676490, index ID 0, partition ID 72057594176667648, alloc unit ID 72057594257866752 (type In-row data), but it was not detected in the scan.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1527676490, index ID 0, partition ID 72057594176667648, alloc unit ID 72057594257866752 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 1 allocation errors and 1 consistency errors in table 'ShoreTel_ETL.Config_b_usercurrentswitch' (object ID 1527676490).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:658) for object ID 1531152500, index ID 0, partition ID 72057594141540352, alloc unit ID 72057594231062528 (type In-row data) is linked in the IAM chain for object ID 183671702, index ID 0, partition ID 72057594154647552, alloc unit ID 72057594240958464 (type In-row data) by page (0:0).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:4438) is pointed to by the next pointer of IAM page (0:0) in object ID 1531152500, index ID 0, partition ID 72057594141540352, alloc unit ID 72057594231062528 (type In-row data), but it was not detected in the scan.

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:658) for object ID 1531152500, index ID 0, partition ID 72057594141540352, alloc unit ID 72057594231062528 (type In-row data) is linked in the IAM chain for object ID 183671702, index ID 0, partition ID 72057594154647552, alloc unit ID 72057594240958464 (type In-row data) by page (0:0).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:4438) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1531152500, index ID 0, partition ID 72057594141540352, alloc unit ID 72057594231062528 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 3 consistency errors in table 'ShoreTel_ETL.Config_b_contacts' (object ID 1531152500).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:429) in object ID 1543676547, index ID 0, partition ID 72057594176929792, alloc unit ID 72057594258063360 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:534) is pointed to by the next pointer of IAM page (0:0) in object ID 1543676547, index ID 0, partition ID 72057594176929792, alloc unit ID 72057594258063360 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:534) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1543676547, index ID 0, partition ID 72057594176929792, alloc unit ID 72057594258063360 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_usergroups' (object ID 1543676547).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:4333) in object ID 1547152557, index ID 0, partition ID 72057594141802496, alloc unit ID 72057594231259136 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:17768) is pointed to by the next pointer of IAM page (0:0) in object ID 1547152557, index ID 0, partition ID 72057594141802496, alloc unit ID 72057594231259136 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:17768) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1547152557, index ID 0, partition ID 72057594141802496, alloc unit ID 72057594231259136 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_coscp' (object ID 1547152557).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:522) in object ID 1559676604, index ID 0, partition ID 72057594177191936, alloc unit ID 72057594258259968 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:3723) is pointed to by the next pointer of IAM page (0:0) in object ID 1559676604, index ID 0, partition ID 72057594177191936, alloc unit ID 72057594258259968 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:3723) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1559676604, index ID 0, partition ID 72057594177191936, alloc unit ID 72057594258259968 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_usergrouptrunkmap' (object ID 1559676604).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:364) is pointed to by the next pointer of IAM page (0:0) in object ID 1563152614, index ID 0, partition ID 72057594142064640, alloc unit ID 72057594231455744 (type In-row data), but it was not detected in the scan.

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:4433) for object ID 1563152614, index ID 0, partition ID 72057594142064640, alloc unit ID 72057594231455744 (type In-row data) is linked in the IAM chain for object ID 1659152956, index ID 0, partition ID 72057594143637504, alloc unit ID 72057594232700928 (type In-row data) by page (0:0).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:364) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1563152614, index ID 0, partition ID 72057594142064640, alloc unit ID 72057594231455744 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:4433) for object ID 1563152614, index ID 0, partition ID 72057594142064640, alloc unit ID 72057594231455744 (type In-row data) is linked in the IAM chain for object ID 1659152956, index ID 0, partition ID 72057594143637504, alloc unit ID 72057594232700928 (type In-row data) by page (0:0).

CHECKDB found 2 allocation errors and 3 consistency errors in table 'ShoreTel_ETL.Config_b_cost' (object ID 1563152614).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:4238) is pointed to by the next pointer of IAM page (0:0) in object ID 1575676661, index ID 0, partition ID 72057594177454080, alloc unit ID 72057594258456576 (type In-row data), but it was not detected in the scan.

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:4257) for object ID 1575676661, index ID 0, partition ID 72057594177454080, alloc unit ID 72057594258456576 (type In-row data) is linked in the IAM chain for object ID 1847677630, index ID 0, partition ID 72057594181910528, alloc unit ID 72057594261864448 (type In-row data) by page (0:0).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:4238) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1575676661, index ID 0, partition ID 72057594177454080, alloc unit ID 72057594258456576 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:4257) for object ID 1575676661, index ID 0, partition ID 72057594177454080, alloc unit ID 72057594258456576 (type In-row data) is linked in the IAM chain for object ID 1847677630, index ID 0, partition ID 72057594181910528, alloc unit ID 72057594261864448 (type In-row data) by page (0:0).

CHECKDB found 2 allocation errors and 3 consistency errors in table 'ShoreTel_ETL.Config_b_userlicensetypes' (object ID 1575676661).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:447) is pointed to by the next pointer of IAM page (0:0) in object ID 1579152671, index ID 0, partition ID 72057594142326784, alloc unit ID 72057594231652352 (type In-row data), but it was not detected in the scan.

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:24228) for object ID 1579152671, index ID 0, partition ID 72057594142326784, alloc unit ID 72057594231652352 (type In-row data) is linked in the IAM chain for object ID 1803153469, index ID 0, partition ID 72057594145996800, alloc unit ID 72057594234470400 (type In-row data) by page (0:0).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:447) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1579152671, index ID 0, partition ID 72057594142326784, alloc unit ID 72057594231652352 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:24228) for object ID 1579152671, index ID 0, partition ID 72057594142326784, alloc unit ID 72057594231652352 (type In-row data) is linked in the IAM chain for object ID 1803153469, index ID 0, partition ID 72057594145996800, alloc unit ID 72057594234470400 (type In-row data) by page (0:0).

CHECKDB found 2 allocation errors and 3 consistency errors in table 'ShoreTel_ETL.Config_b_cosvm' (object ID 1579152671).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:156) in object ID 1595152728, index ID 0, partition ID 72057594142588928, alloc unit ID 72057594231848960 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:3878) is pointed to by the next pointer of IAM page (0:0) in object ID 1595152728, index ID 0, partition ID 72057594142588928, alloc unit ID 72057594231848960 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:3878) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1595152728, index ID 0, partition ID 72057594142588928, alloc unit ID 72057594231848960 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_cotypes' (object ID 1595152728).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:208) for object ID 1607676775, index ID 0, partition ID 72057594177978368, alloc unit ID 72057594258849792 (type In-row data) is linked in the IAM chain for object ID 1735677231, index ID 0, partition ID 72057594180075520, alloc unit ID 72057594260488192 (type In-row data) by page (0:0).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:4271) is pointed to by the next pointer of IAM page (0:0) in object ID 1607676775, index ID 0, partition ID 72057594177978368, alloc unit ID 72057594258849792 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:4271) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1607676775, index ID 0, partition ID 72057594177978368, alloc unit ID 72057594258849792 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:208) for object ID 1607676775, index ID 0, partition ID 72057594177978368, alloc unit ID 72057594258849792 (type In-row data) is linked in the IAM chain for object ID 1735677231, index ID 0, partition ID 72057594180075520, alloc unit ID 72057594260488192 (type In-row data) by page (0:0).

CHECKDB found 2 allocation errors and 3 consistency errors in table 'ShoreTel_ETL.Config_b_userpcmpreferences' (object ID 1607676775).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:191) for object ID 1611152785, index ID 0, partition ID 72057594142851072, alloc unit ID 72057594232045568 (type In-row data) is linked in the IAM chain for object ID 1419152101, index ID 0, partition ID 72057594139705344, alloc unit ID 72057594229686272 (type In-row data) by page (0:0).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:4247) is pointed to by the next pointer of IAM page (0:0) in object ID 1611152785, index ID 0, partition ID 72057594142851072, alloc unit ID 72057594232045568 (type In-row data), but it was not detected in the scan.

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:191) for object ID 1611152785, index ID 0, partition ID 72057594142851072, alloc unit ID 72057594232045568 (type In-row data) is linked in the IAM chain for object ID 1419152101, index ID 0, partition ID 72057594139705344, alloc unit ID 72057594229686272 (type In-row data) by page (0:0).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:4247) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1611152785, index ID 0, partition ID 72057594142851072, alloc unit ID 72057594232045568 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 3 consistency errors in table 'ShoreTel_ETL.Config_b_countries' (object ID 1611152785).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:375) for object ID 1623676832, index ID 0, partition ID 72057594178240512, alloc unit ID 72057594259111936 (type In-row data) is linked in the IAM chain for object ID 1655676946, index ID 0, partition ID 72057594178764800, alloc unit ID 72057594259505152 (type In-row data) by page (0:0).

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1623676832, index ID 0, partition ID 72057594178240512, alloc unit ID 72057594259111936 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:375) for object ID 1623676832, index ID 0, partition ID 72057594178240512, alloc unit ID 72057594259111936 (type In-row data) is linked in the IAM chain for object ID 1655676946, index ID 0, partition ID 72057594178764800, alloc unit ID 72057594259505152 (type In-row data) by page (0:0).

CHECKDB found 1 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_userpreferences' (object ID 1623676832).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:435) for object ID 1639676889, index ID 0, partition ID 72057594178502656, alloc unit ID 72057594259308544 (type In-row data) is linked in the IAM chain for object ID 1415676091, index ID 0, partition ID 72057594174832640, alloc unit ID 72057594256424960 (type In-row data) by page (0:0).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:435) for object ID 1639676889, index ID 0, partition ID 72057594178502656, alloc unit ID 72057594259308544 (type In-row data) is linked in the IAM chain for object ID 1415676091, index ID 0, partition ID 72057594174832640, alloc unit ID 72057594256424960 (type In-row data) by page (0:0).

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1639676889, index ID 0, partition ID 72057594178502656, alloc unit ID 72057594259308544 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 1 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_userprogbuttons' (object ID 1639676889).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:314) in object ID 1643152899, index ID 0, partition ID 72057594143375360, alloc unit ID 72057594232504320 (type In-row data), but it was not detected in the scan.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1643152899, index ID 0, partition ID 72057594143375360, alloc unit ID 72057594232504320 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 1 allocation errors and 1 consistency errors in table 'ShoreTel_ETL.Config_b_countrycotypesmap' (object ID 1643152899).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:673) for object ID 1655676946, index ID 0, partition ID 72057594178764800, alloc unit ID 72057594259505152 (type In-row data) is linked in the IAM chain for object ID 839674039, index ID 0, partition ID 72057594165395456, alloc unit ID 72057594249084928 (type In-row data) by page (0:0).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:673) for object ID 1655676946, index ID 0, partition ID 72057594178764800, alloc unit ID 72057594259505152 (type In-row data) is linked in the IAM chain for object ID 839674039, index ID 0, partition ID 72057594165395456, alloc unit ID 72057594249084928 (type In-row data) by page (0:0).

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1655676946, index ID 0, partition ID 72057594178764800, alloc unit ID 72057594259505152 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 1 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_users' (object ID 1655676946).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:452) in object ID 1659152956, index ID 0, partition ID 72057594143637504, alloc unit ID 72057594232700928 (type In-row data), but it was not detected in the scan.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1659152956, index ID 0, partition ID 72057594143637504, alloc unit ID 72057594232700928 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 1 allocation errors and 1 consistency errors in table 'ShoreTel_ETL.Config_b_countryswitchtypemap' (object ID 1659152956).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:4281) for object ID 1671677003, index ID 0, partition ID 72057594179026944, alloc unit ID 72057594259701760 (type In-row data) is linked in the IAM chain for object ID 855674096, index ID 0, partition ID 72057594165657600, alloc unit ID 72057594249281536 (type In-row data) by page (0:0).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:4281) for object ID 1671677003, index ID 0, partition ID 72057594179026944, alloc unit ID 72057594259701760 (type In-row data) is linked in the IAM chain for object ID 855674096, index ID 0, partition ID 72057594165657600, alloc unit ID 72057594249281536 (type In-row data) by page (0:0).

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1671677003, index ID 0, partition ID 72057594179026944, alloc unit ID 72057594259701760 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 1 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_userstatustypes' (object ID 1671677003).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:4242) in object ID 1675153013, index ID 0, partition ID 72057594143899648, alloc unit ID 72057594232897536 (type In-row data), but it was not detected in the scan.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1675153013, index ID 0, partition ID 72057594143899648, alloc unit ID 72057594232897536 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 1 allocation errors and 1 consistency errors in table 'ShoreTel_ETL.Config_b_countrytrunktypemap' (object ID 1675153013).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:4330) for object ID 1687677060, index ID 0, partition ID 72057594179289088, alloc unit ID 72057594259898368 (type In-row data) is linked in the IAM chain for object ID 1863677687, index ID 0, partition ID 72057594182172672, alloc unit ID 72057594262061056 (type In-row data) by page (0:0).

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1687677060, index ID 0, partition ID 72057594179289088, alloc unit ID 72057594259898368 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:4330) for object ID 1687677060, index ID 0, partition ID 72057594179289088, alloc unit ID 72057594259898368 (type In-row data) is linked in the IAM chain for object ID 1863677687, index ID 0, partition ID 72057594182172672, alloc unit ID 72057594262061056 (type In-row data) by page (0:0).

CHECKDB found 1 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_usertoolbars' (object ID 1687677060).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:197) is pointed to by the next pointer of IAM page (0:0) in object ID 1691153070, index ID 0, partition ID 72057594144161792, alloc unit ID 72057594233094144 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:4449) in object ID 1691153070, index ID 0, partition ID 72057594144161792, alloc unit ID 72057594233094144 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:197) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1691153070, index ID 0, partition ID 72057594144161792, alloc unit ID 72057594233094144 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_dateformattypes' (object ID 1691153070).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:24226) for object ID 1703677117, index ID 0, partition ID 72057594179551232, alloc unit ID 72057594260094976 (type In-row data) is linked in the IAM chain for object ID 1975678086, index ID 0, partition ID 72057594184007680, alloc unit ID 72057594263502848 (type In-row data) by page (0:0).

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1703677117, index ID 0, partition ID 72057594179551232, alloc unit ID 72057594260094976 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:24226) for object ID 1703677117, index ID 0, partition ID 72057594179551232, alloc unit ID 72057594260094976 (type In-row data) is linked in the IAM chain for object ID 1975678086, index ID 0, partition ID 72057594184007680, alloc unit ID 72057594263502848 (type In-row data) by page (0:0).

CHECKDB found 1 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_usertypes' (object ID 1703677117).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:396) is pointed to by the next pointer of IAM page (0:0) in object ID 1707153127, index ID 0, partition ID 72057594144423936, alloc unit ID 72057594233290752 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:4437) in object ID 1707153127, index ID 0, partition ID 72057594144423936, alloc unit ID 72057594233290752 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:396) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1707153127, index ID 0, partition ID 72057594144423936, alloc unit ID 72057594233290752 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_dateseparatortypes' (object ID 1707153127).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:189) in object ID 1719677174, index ID 0, partition ID 72057594179813376, alloc unit ID 72057594260291584 (type In-row data), but it was not detected in the scan.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1719677174, index ID 0, partition ID 72057594179813376, alloc unit ID 72057594260291584 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 1 allocation errors and 1 consistency errors in table 'ShoreTel_ETL.Config_b_version' (object ID 1719677174).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:670) is pointed to by the next pointer of IAM page (0:0) in object ID 1723153184, index ID 0, partition ID 72057594144686080, alloc unit ID 72057594233487360 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:4447) in object ID 1723153184, index ID 0, partition ID 72057594144686080, alloc unit ID 72057594233487360 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:670) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1723153184, index ID 0, partition ID 72057594144686080, alloc unit ID 72057594233487360 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_daytypes' (object ID 1723153184).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:4444) in object ID 1735677231, index ID 0, partition ID 72057594180075520, alloc unit ID 72057594260488192 (type In-row data), but it was not detected in the scan.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1735677231, index ID 0, partition ID 72057594180075520, alloc unit ID 72057594260488192 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 1 allocation errors and 1 consistency errors in table 'ShoreTel_ETL.Config_b_vmnctypes' (object ID 1735677231).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:158) for object ID 1739153241, index ID 0, partition ID 72057594144948224, alloc unit ID 72057594233683968 (type In-row data) is linked in the IAM chain for object ID 1675153013, index ID 0, partition ID 72057594143899648, alloc unit ID 72057594232897536 (type In-row data) by page (0:0).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:4239) is pointed to by the next pointer of IAM page (0:0) in object ID 1739153241, index ID 0, partition ID 72057594144948224, alloc unit ID 72057594233683968 (type In-row data), but it was not detected in the scan.

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:158) for object ID 1739153241, index ID 0, partition ID 72057594144948224, alloc unit ID 72057594233683968 (type In-row data) is linked in the IAM chain for object ID 1675153013, index ID 0, partition ID 72057594143899648, alloc unit ID 72057594232897536 (type In-row data) by page (0:0).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:4239) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1739153241, index ID 0, partition ID 72057594144948224, alloc unit ID 72057594233683968 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 3 consistency errors in table 'ShoreTel_ETL.Config_b_dialingrange' (object ID 1739153241).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:321) in object ID 1751677288, index ID 0, partition ID 72057594180337664, alloc unit ID 72057594260684800 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:348) is pointed to by the next pointer of IAM page (0:0) in object ID 1751677288, index ID 0, partition ID 72057594180337664, alloc unit ID 72057594260684800 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:348) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1751677288, index ID 0, partition ID 72057594180337664, alloc unit ID 72057594260684800 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_vmnmtypes' (object ID 1751677288).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:207) for object ID 1755153298, index ID 0, partition ID 72057594145210368, alloc unit ID 72057594233880576 (type In-row data) is linked in the IAM chain for object ID 1003150619, index ID 0, partition ID 72057594132889600, alloc unit ID 72057594224574464 (type In-row data) by page (0:0).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:4273) is pointed to by the next pointer of IAM page (0:0) in object ID 1755153298, index ID 0, partition ID 72057594145210368, alloc unit ID 72057594233880576 (type In-row data), but it was not detected in the scan.

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:207) for object ID 1755153298, index ID 0, partition ID 72057594145210368, alloc unit ID 72057594233880576 (type In-row data) is linked in the IAM chain for object ID 1003150619, index ID 0, partition ID 72057594132889600, alloc unit ID 72057594224574464 (type In-row data) by page (0:0).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:4273) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1755153298, index ID 0, partition ID 72057594145210368, alloc unit ID 72057594233880576 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 3 consistency errors in table 'ShoreTel_ETL.Config_b_dialingrangetypes' (object ID 1755153298).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:223) for object ID 1771153355, index ID 0, partition ID 72057594145472512, alloc unit ID 72057594234077184 (type In-row data) is linked in the IAM chain for object ID 1435152158, index ID 0, partition ID 72057594139967488, alloc unit ID 72057594229882880 (type In-row data) by page (0:0).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:4300) is pointed to by the next pointer of IAM page (0:0) in object ID 1771153355, index ID 0, partition ID 72057594145472512, alloc unit ID 72057594234077184 (type In-row data), but it was not detected in the scan.

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:223) for object ID 1771153355, index ID 0, partition ID 72057594145472512, alloc unit ID 72057594234077184 (type In-row data) is linked in the IAM chain for object ID 1435152158, index ID 0, partition ID 72057594139967488, alloc unit ID 72057594229882880 (type In-row data) by page (0:0).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:4300) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1771153355, index ID 0, partition ID 72057594145472512, alloc unit ID 72057594234077184 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 3 consistency errors in table 'ShoreTel_ETL.Config_b_diddigitmap' (object ID 1771153355).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:643) is pointed to by the next pointer of IAM page (0:0) in object ID 1783677402, index ID 0, partition ID 72057594180861952, alloc unit ID 72057594261078016 (type In-row data), but it was not detected in the scan.

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:647) for object ID 1783677402, index ID 0, partition ID 72057594180861952, alloc unit ID 72057594261078016 (type In-row data) is linked in the IAM chain for object ID 1815677516, index ID 0, partition ID 72057594181386240, alloc unit ID 72057594261471232 (type In-row data) by page (0:0).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:643) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1783677402, index ID 0, partition ID 72057594180861952, alloc unit ID 72057594261078016 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:647) for object ID 1783677402, index ID 0, partition ID 72057594180861952, alloc unit ID 72057594261078016 (type In-row data) is linked in the IAM chain for object ID 1815677516, index ID 0, partition ID 72057594181386240, alloc unit ID 72057594261471232 (type In-row data) by page (0:0).

CHECKDB found 2 allocation errors and 3 consistency errors in table 'ShoreTel_ETL.Config_b_vmserverextensions' (object ID 1783677402).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:307) in object ID 1787153412, index ID 0, partition ID 72057594145734656, alloc unit ID 72057594234273792 (type In-row data), but it was not detected in the scan.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1787153412, index ID 0, partition ID 72057594145734656, alloc unit ID 72057594234273792 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 1 allocation errors and 1 consistency errors in table 'ShoreTel_ETL.Config_b_didranges' (object ID 1787153412).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:525) is pointed to by the next pointer of IAM page (0:0) in object ID 1799677459, index ID 0, partition ID 72057594181124096, alloc unit ID 72057594261274624 (type In-row data), but it was not detected in the scan.

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:4276) for object ID 1799677459, index ID 0, partition ID 72057594181124096, alloc unit ID 72057594261274624 (type In-row data) is linked in the IAM chain for object ID 1703677117, index ID 0, partition ID 72057594179551232, alloc unit ID 72057594260094976 (type In-row data) by page (0:0).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:4276) for object ID 1799677459, index ID 0, partition ID 72057594181124096, alloc unit ID 72057594261274624 (type In-row data) is linked in the IAM chain for object ID 1703677117, index ID 0, partition ID 72057594179551232, alloc unit ID 72057594260094976 (type In-row data) by page (0:0).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:525) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1799677459, index ID 0, partition ID 72057594181124096, alloc unit ID 72057594261274624 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 3 consistency errors in table 'ShoreTel_ETL.Config_b_vmservers' (object ID 1799677459).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:387) in object ID 1803153469, index ID 0, partition ID 72057594145996800, alloc unit ID 72057594234470400 (type In-row data), but it was not detected in the scan.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1803153469, index ID 0, partition ID 72057594145996800, alloc unit ID 72057594234470400 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 1 allocation errors and 1 consistency errors in table 'ShoreTel_ETL.Config_b_didservices' (object ID 1803153469).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:4319) for object ID 1815677516, index ID 0, partition ID 72057594181386240, alloc unit ID 72057594261471232 (type In-row data) is linked in the IAM chain for object ID 1719677174, index ID 0, partition ID 72057594179813376, alloc unit ID 72057594260291584 (type In-row data) by page (0:0).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:4319) for object ID 1815677516, index ID 0, partition ID 72057594181386240, alloc unit ID 72057594261471232 (type In-row data) is linked in the IAM chain for object ID 1719677174, index ID 0, partition ID 72057594179813376, alloc unit ID 72057594260291584 (type In-row data) by page (0:0).

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1815677516, index ID 0, partition ID 72057594181386240, alloc unit ID 72057594261471232 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 1 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_vmservertypes' (object ID 1815677516).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:3875) is pointed to by the next pointer of IAM page (0:0) in object ID 1831677573, index ID 0, partition ID 72057594181648384, alloc unit ID 72057594261667840 (type In-row data), but it was not detected in the scan.

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:4450) for object ID 1831677573, index ID 0, partition ID 72057594181648384, alloc unit ID 72057594261667840 (type In-row data) is linked in the IAM chain for object ID 1943677972, index ID 0, partition ID 72057594183483392, alloc unit ID 72057594263109632 (type In-row data) by page (0:0).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:3875) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1831677573, index ID 0, partition ID 72057594181648384, alloc unit ID 72057594261667840 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:4450) for object ID 1831677573, index ID 0, partition ID 72057594181648384, alloc unit ID 72057594261667840 (type In-row data) is linked in the IAM chain for object ID 1943677972, index ID 0, partition ID 72057594183483392, alloc unit ID 72057594263109632 (type In-row data) by page (0:0).

CHECKDB found 2 allocation errors and 3 consistency errors in table 'ShoreTel_ETL.Config_b_voicemailtuitypes' (object ID 1831677573).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:153) for object ID 1847677630, index ID 0, partition ID 72057594181910528, alloc unit ID 72057594261864448 (type In-row data) is linked in the IAM chain for object ID 1991678143, index ID 0, partition ID 72057594184269824, alloc unit ID 72057594263699456 (type In-row data) by page (0:0).

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1847677630, index ID 0, partition ID 72057594181910528, alloc unit ID 72057594261864448 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:153) for object ID 1847677630, index ID 0, partition ID 72057594181910528, alloc unit ID 72057594261864448 (type In-row data) is linked in the IAM chain for object ID 1991678143, index ID 0, partition ID 72057594184269824, alloc unit ID 72057594263699456 (type In-row data) by page (0:0).

CHECKDB found 1 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_wallpapers' (object ID 1847677630).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:374) in object ID 1851153640, index ID 0, partition ID 72057594146783232, alloc unit ID 72057594235060224 (type In-row data), but it was not detected in the scan.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1851153640, index ID 0, partition ID 72057594146783232, alloc unit ID 72057594235060224 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 1 allocation errors and 1 consistency errors in table 'ShoreTel_ETL.Config_b_directoryservicetypes' (object ID 1851153640).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:202) in object ID 1863677687, index ID 0, partition ID 72057594182172672, alloc unit ID 72057594262061056 (type In-row data), but it was not detected in the scan.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1863677687, index ID 0, partition ID 72057594182172672, alloc unit ID 72057594262061056 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 1 allocation errors and 1 consistency errors in table 'ShoreTel_ETL.Config_b_workgroupagents' (object ID 1863677687).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:159) in object ID 1879677744, index ID 0, partition ID 72057594182434816, alloc unit ID 72057594262257664 (type In-row data), but it was not detected in the scan.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1879677744, index ID 0, partition ID 72057594182434816, alloc unit ID 72057594262257664 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 1 allocation errors and 1 consistency errors in table 'ShoreTel_ETL.Config_b_workgroupagentstates' (object ID 1879677744).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:535) is pointed to by the next pointer of IAM page (0:0) in object ID 1883153754, index ID 0, partition ID 72057594147307520, alloc unit ID 72057594235453440 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:656) in object ID 1883153754, index ID 0, partition ID 72057594147307520, alloc unit ID 72057594235453440 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:535) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1883153754, index ID 0, partition ID 72057594147307520, alloc unit ID 72057594235453440 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_distributionlistitems' (object ID 1883153754).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:386) in object ID 1895677801, index ID 0, partition ID 72057594182696960, alloc unit ID 72057594262454272 (type In-row data), but it was not detected in the scan.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1895677801, index ID 0, partition ID 72057594182696960, alloc unit ID 72057594262454272 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 1 allocation errors and 1 consistency errors in table 'ShoreTel_ETL.Config_b_workgroupchm' (object ID 1895677801).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:4286) in object ID 1899153811, index ID 0, partition ID 72057594147569664, alloc unit ID 72057594235650048 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:4451) is pointed to by the next pointer of IAM page (0:0) in object ID 1899153811, index ID 0, partition ID 72057594147569664, alloc unit ID 72057594235650048 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:4451) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1899153811, index ID 0, partition ID 72057594147569664, alloc unit ID 72057594235650048 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_distributionlists' (object ID 1899153811).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:516) in object ID 1911677858, index ID 0, partition ID 72057594182959104, alloc unit ID 72057594262716416 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:4350) is pointed to by the next pointer of IAM page (0:0) in object ID 1911677858, index ID 0, partition ID 72057594182959104, alloc unit ID 72057594262716416 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:4350) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1911677858, index ID 0, partition ID 72057594182959104, alloc unit ID 72057594262716416 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_workgroupkeypadtypes' (object ID 1911677858).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:226) is pointed to by the next pointer of IAM page (0:0) in object ID 1915153868, index ID 0, partition ID 72057594147831808, alloc unit ID 72057594235846656 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:17774) in object ID 1915153868, index ID 0, partition ID 72057594147831808, alloc unit ID 72057594235846656 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:226) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1915153868, index ID 0, partition ID 72057594147831808, alloc unit ID 72057594235846656 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_dn' (object ID 1915153868).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:4244) in object ID 1927677915, index ID 0, partition ID 72057594183221248, alloc unit ID 72057594262913024 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:4442) is pointed to by the next pointer of IAM page (0:0) in object ID 1927677915, index ID 0, partition ID 72057594183221248, alloc unit ID 72057594262913024 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:4442) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1927677915, index ID 0, partition ID 72057594183221248, alloc unit ID 72057594262913024 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_workgroupmailboxes' (object ID 1927677915).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:358) for object ID 1931153925, index ID 0, partition ID 72057594148093952, alloc unit ID 72057594236043264 (type In-row data) is linked in the IAM chain for object ID 535672956, index ID 0, partition ID 72057594160414720, alloc unit ID 72057594245349376 (type In-row data) by page (0:0).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:358) for object ID 1931153925, index ID 0, partition ID 72057594148093952, alloc unit ID 72057594236043264 (type In-row data) is linked in the IAM chain for object ID 535672956, index ID 0, partition ID 72057594160414720, alloc unit ID 72057594245349376 (type In-row data) by page (0:0).

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1931153925, index ID 0, partition ID 72057594148093952, alloc unit ID 72057594236043264 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 1 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_dn_ref' (object ID 1931153925).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:4314) in object ID 1943677972, index ID 0, partition ID 72057594183483392, alloc unit ID 72057594263109632 (type In-row data), but it was not detected in the scan.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1943677972, index ID 0, partition ID 72057594183483392, alloc unit ID 72057594263109632 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 1 allocation errors and 1 consistency errors in table 'ShoreTel_ETL.Config_b_workgroupmembers' (object ID 1943677972).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:167) is pointed to by the next pointer of IAM page (0:0) in object ID 1963154039, index ID 0, partition ID 72057594148618240, alloc unit ID 72057594236436480 (type In-row data), but it was not detected in the scan.

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:195) for object ID 1963154039, index ID 0, partition ID 72057594148618240, alloc unit ID 72057594236436480 (type In-row data) is linked in the IAM chain for object ID 2123154609, index ID 0, partition ID 72057594151239680, alloc unit ID 72057594238402560 (type In-row data) by page (0:0).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:167) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1963154039, index ID 0, partition ID 72057594148618240, alloc unit ID 72057594236436480 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:195) for object ID 1963154039, index ID 0, partition ID 72057594148618240, alloc unit ID 72057594236436480 (type In-row data) is linked in the IAM chain for object ID 2123154609, index ID 0, partition ID 72057594151239680, alloc unit ID 72057594238402560 (type In-row data) by page (0:0).

CHECKDB found 2 allocation errors and 3 consistency errors in table 'ShoreTel_ETL.Config_b_dntypes' (object ID 1963154039).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:155) for object ID 1975678086, index ID 0, partition ID 72057594184007680, alloc unit ID 72057594263502848 (type In-row data) is linked in the IAM chain for object ID 2007678200, index ID 0, partition ID 72057594184531968, alloc unit ID 72057594263896064 (type In-row data) by page (0:0).

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1975678086, index ID 0, partition ID 72057594184007680, alloc unit ID 72057594263502848 (type In-row data) due to invalid allocation (IAM) page(s).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:155) for object ID 1975678086, index ID 0, partition ID 72057594184007680, alloc unit ID 72057594263502848 (type In-row data) is linked in the IAM chain for object ID 2007678200, index ID 0, partition ID 72057594184531968, alloc unit ID 72057594263896064 (type In-row data) by page (0:0).

CHECKDB found 1 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_workgroups' (object ID 1975678086).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:224) in object ID 1991678143, index ID 0, partition ID 72057594184269824, alloc unit ID 72057594263699456 (type In-row data), but it was not detected in the scan.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1991678143, index ID 0, partition ID 72057594184269824, alloc unit ID 72057594263699456 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 1 allocation errors and 1 consistency errors in table 'ShoreTel_ETL.Config_b_workgroupstepitems' (object ID 1991678143).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:298) is pointed to by the next pointer of IAM page (0:0) in object ID 1995154153, index ID 0, partition ID 72057594149142528, alloc unit ID 72057594236829696 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:644) in object ID 1995154153, index ID 0, partition ID 72057594149142528, alloc unit ID 72057594236829696 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:298) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 1995154153, index ID 0, partition ID 72057594149142528, alloc unit ID 72057594236829696 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_ecractiontypes' (object ID 1995154153).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:300) in object ID 2007678200, index ID 0, partition ID 72057594184531968, alloc unit ID 72057594263896064 (type In-row data), but it was not detected in the scan.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 2007678200, index ID 0, partition ID 72057594184531968, alloc unit ID 72057594263896064 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 1 allocation errors and 1 consistency errors in table 'ShoreTel_ETL.Config_b_workgroupsteps' (object ID 2007678200).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:384) is pointed to by the next pointer of IAM page (0:0) in object ID 2011154210, index ID 0, partition ID 72057594149404672, alloc unit ID 72057594237026304 (type In-row data), but it was not detected in the scan.

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:4236) in object ID 2011154210, index ID 0, partition ID 72057594149404672, alloc unit ID 72057594237026304 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:384) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 2011154210, index ID 0, partition ID 72057594149404672, alloc unit ID 72057594237026304 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_ecrcriteria' (object ID 2011154210).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:4313) in object ID 2043154324, index ID 0, partition ID 72057594149928960, alloc unit ID 72057594237419520 (type In-row data), but it was not detected in the scan.

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:49165) is pointed to by the next pointer of IAM page (0:0) in object ID 2043154324, index ID 0, partition ID 72057594149928960, alloc unit ID 72057594237419520 (type In-row data), but it was not detected in the scan.

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:49165) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 2043154324, index ID 0, partition ID 72057594149928960, alloc unit ID 72057594237419520 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_ecrnumbertypes' (object ID 2043154324).

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (5:412) in object ID 2091154495, index ID 0, partition ID 72057594150715392, alloc unit ID 72057594238009344 (type In-row data), but it was not detected in the scan.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 2091154495, index ID 0, partition ID 72057594150715392, alloc unit ID 72057594238009344 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 1 allocation errors and 1 consistency errors in table 'ShoreTel_ETL.Config_b_emergencynumbers' (object ID 2091154495).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:4227) for object ID 2107154552, index ID 0, partition ID 72057594150977536, alloc unit ID 72057594238205952 (type In-row data) is linked in the IAM chain for object ID 903674267, index ID 0, partition ID 72057594166444032, alloc unit ID 72057594249871360 (type In-row data) by page (0:0).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:4349) is pointed to by the next pointer of IAM page (0:0) in object ID 2107154552, index ID 0, partition ID 72057594150977536, alloc unit ID 72057594238205952 (type In-row data), but it was not detected in the scan.

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:4227) for object ID 2107154552, index ID 0, partition ID 72057594150977536, alloc unit ID 72057594238205952 (type In-row data) is linked in the IAM chain for object ID 903674267, index ID 0, partition ID 72057594166444032, alloc unit ID 72057594249871360 (type In-row data) by page (0:0).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:4349) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 2107154552, index ID 0, partition ID 72057594150977536, alloc unit ID 72057594238205952 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 3 consistency errors in table 'ShoreTel_ETL.Config_b_encryptiontypes' (object ID 2107154552).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:17775) for object ID 2123154609, index ID 0, partition ID 72057594151239680, alloc unit ID 72057594238402560 (type In-row data) is linked in the IAM chain for object ID 1319675749, index ID 0, partition ID 72057594173259776, alloc unit ID 72057594255245312 (type In-row data) by page (0:0).

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:17775) for object ID 2123154609, index ID 0, partition ID 72057594151239680, alloc unit ID 72057594238402560 (type In-row data) is linked in the IAM chain for object ID 1319675749, index ID 0, partition ID 72057594173259776, alloc unit ID 72057594255245312 (type In-row data) by page (0:0).

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 2123154609, index ID 0, partition ID 72057594151239680, alloc unit ID 72057594238402560 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 1 allocation errors and 2 consistency errors in table 'ShoreTel_ETL.Config_b_escalationpaging' (object ID 2123154609).

Msg 8959, Level 16, State 3, Line 1

Table error: IAM page (5:409) for object ID 2139154666, index ID 0, partition ID 72057594151501824, alloc unit ID 72057594238599168 (type In-row data) is linked in the IAM chain for object ID 167671645, index ID 0, partition ID 72057594154385408, alloc unit ID 72057594240761856 (type In-row data) by page (0:0).

Msg 2575, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (5:645) is pointed to by the next pointer of IAM page (0:0) in object ID 2139154666, index ID 0, partition ID 72057594151501824, alloc unit ID 72057594238599168 (type In-row data), but it was not detected in the scan.

Msg 8959, Level 16, State 1, Line 1

Table error: IAM page (5:409) for object ID 2139154666, index ID 0, partition ID 72057594151501824, alloc unit ID 72057594238599168 (type In-row data) is linked in the IAM chain for object ID 167671645, index ID 0, partition ID 72057594154385408, alloc unit ID 72057594240761856 (type In-row data) by page (0:0).

Msg 8946, Level 16, State 3, Line 1

Table error: Allocation page (5:645) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.

Msg 7965, Level 16, State 2, Line 1

Table error: Could not check object ID 2139154666, index ID 0, partition ID 72057594151501824, alloc unit ID 72057594238599168 (type In-row data) due to invalid allocation (IAM) page(s).

CHECKDB found 2 allocation errors and 3 consistency errors in table 'ShoreTel_ETL.Config_b_escalationpagingsteps' (object ID 2139154666).

CHECKDB found 244 allocation errors and 312 consistency errors in database 'EDW_ShoreTel'.

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

A big thank you to all of you for your input and help on this!

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

Firstly, repair_rebuild is not going to do a damn thing.

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

and that's the same for both DBs

Try repair_allow_data_loss (warning, you could lose a lot of data here). If it gives you the same error, try restarting the instance and trying again.

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

SQL_ME_RICH SSChampion Points: 11200 More actions · Answer 5

Hi Gail - thank you very much for this feedback.

What I wound up doing was taking a backup of each of the databases, and restored them into a new database instance. I was able to run my DBCC command there without issue.

I am doing the data comparison now, and will let you know just how bad the data loss is.

Thanks again to you all for your help. Just for clarity - I did not try bouncing the SQL services in the original instance to see if that would address the 5244 error (just was going to be too time consuming to do it in there).