February 6, 2010 at 1:23 am
Hi All,
Last week we had a issue where an update statistics job that got started appeared to hang the SQL 2000 Server. Users complained that they could not access the DB from their app. One of the staff looked at Enterprise Manager and it would not connect to the default instance at all and the service appeared to be hung. After about 15 minutes the staff member tried to stop the service and was unsuccessful so he ended up killing the process from Task Manager. After starting the service back up all the databases seemed ok so he allowed the staff to load up their app again and continue to work. All was fine until this week when an update statistics job was run again and it appeared to fail. We ran a CheckDB and there appears to be many errors now in the DB. Can anyone assist in helping us to fix these? Since the original problem happened a week ago we really cannot go back to a backup that long ago. DBCC log is shown below. Please help!
Server: Msg 8948, Level 16, State 3, Line 1
Database error: Page (1:239048) is marked with the wrong type in PFS page (1:234552). PFS status 0x70 expected 0x60.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 0, index ID 0: Page (1:239050) could not be processed. See other errors for details.
Server: Msg 8948, Level 16, State 1, Line 1
Database error: Page (1:270112) is marked with the wrong type in PFS page (1:266904). PFS status 0x70 expected 0x60.
Server: Msg 8948, Level 16, State 1, Line 1
Database error: Page (1:270114) is marked with the wrong type in PFS page (1:266904). PFS status 0x70 expected 0x60.
Server: Msg 8948, Level 16, State 1, Line 1
Database error: Page (1:270116) is marked with the wrong type in PFS page (1:266904). PFS status 0x70 expected 0x60.
Server: Msg 8948, Level 16, State 1, Line 1
Database error: Page (1:270119) is marked with the wrong type in PFS page (1:266904). PFS status 0x70 expected 0x60.
Server: Msg 8948, Level 16, State 1, Line 1
Database error: Page (1:270138) is marked with the wrong type in PFS page (1:266904). PFS status 0x70 expected 0x60.
Server: Msg 8948, Level 16, State 1, Line 1
Database error: Page (1:270140) is marked with the wrong type in PFS page (1:266904). PFS status 0x70 expected 0x60.
Server: Msg 8948, Level 16, State 1, Line 1
Database error: Page (1:270142) is marked with the wrong type in PFS page (1:266904). PFS status 0x70 expected 0x60.
Server: Msg 8948, Level 16, State 1, Line 1
Database error: Page (1:270928) is marked with the wrong type in PFS page (1:266904). PFS status 0x70 expected 0x60.
Server: Msg 8948, Level 16, State 1, Line 1
Database error: Page (1:270930) is marked with the wrong type in PFS page (1:266904). PFS status 0x70 expected 0x60.
Server: Msg 8948, Level 16, State 1, Line 1
Database error: Page (1:270934) is marked with the wrong type in PFS page (1:266904). PFS status 0x70 expected 0x60.
Server: Msg 8948, Level 16, State 1, Line 1
Database error: Page (1:270936) is marked with the wrong type in PFS page (1:266904). PFS status 0x70 expected 0x60.
Server: Msg 8948, Level 16, State 1, Line 1
Database error: Page (1:270989) is marked with the wrong type in PFS page (1:266904). PFS status 0x70 expected 0x60.
Server: Msg 8948, Level 16, State 1, Line 1
Database error: Page (1:270991) is marked with the wrong type in PFS page (1:266904). PFS status 0x70 expected 0x60.
DBCC results for 'ppmdatatest'.
Server: Msg 8948, Level 16, State 3, Line 1
Database error: Page (1:271025) is marked with the wrong type in PFS page (1:266904). PFS status 0x70 expected 0x60.
Server: Msg 8948, Level 16, State 1, Line 1
Database error: Page (1:271644) is marked with the wrong type in PFS page (1:266904). PFS status 0x70 expected 0x60.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 0, index ID 0: Page (1:271646) could not be processed. See other errors for details.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:320848) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:320872) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:320920) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:320936) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:320944) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:320952) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:320968) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:320976) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:320984) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:320992) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321000) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321008) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321016) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321024) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321032) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321056) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321072) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321096) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321144) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321152) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321160) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321168) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321192) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321200) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321216) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321248) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321256) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321264) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321272) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321280) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321288) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321296) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321304) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321320) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321328) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321344) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321368) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321376) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321384) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321392) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321416) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321432) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321440) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321456) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321480) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321488) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321496) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321512) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321520) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321536) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321560) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321600) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321608) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321616) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321632) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321672) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321696) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321712) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321744) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321752) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321760) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321784) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321792) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321800) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321808) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321856) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321904) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321936) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:321960) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:322008) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:322016) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:322032) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:322048) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:322056) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:322064) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:322072) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:322104) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:322136) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:322144) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:322168) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:322176) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:322184) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:322192) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:322200) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:322208) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:322216) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:322224) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:322232) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:322240) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:322256) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:322288) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:322296) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:322304) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:322312) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:322320) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:322328) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:322336) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:322344) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:322352) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:322360) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:322368) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:322376) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:322384) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:322392) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:322400) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:322416) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:322424) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:322440) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:322456) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:322464) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:322488) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 43971313664 owned by data record identified by RID = (1:97:4) id = 991263978 and indid = 4.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 43971379200 owned by data record identified by RID = (1:97:5) id = 991263978 and indid = 5.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 43971444736 owned by data record identified by RID = (1:97:6) id = 991263978 and indid = 6.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 43976032256 owned by data record identified by RID = (1:283664:6) id = 2054935784 and indid = 3.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 43976294400 owned by data record identified by RID = (1:283664:10) id = 2054935784 and indid = 7.
CHECKDB found 129 allocation errors and 0 consistency errors not associated with any single object.
DBCC results for 'sysobjects'.
There are 1237 rows in 22 pages for object 'sysobjects'.
DBCC results for 'sysindexes'.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 43997659136 owned by data record identified by RID = (1:283669:8) id = 331173717 and indid = 10.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 43970068480 owned by data record identified by RID = (1:335089:2) id = 642738734 and indid = 3.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:279810), slot 1, text ID 43971444736 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:296704), slot 2, text ID 43402723328 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:296704), slot 4, text ID 43406262272 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:296704), slot 6, text ID 43406327808 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:296704), slot 15, text ID 43406393344 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:296704), slot 16, text ID 43406458880 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:296704), slot 17, text ID 43406524416 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:296704), slot 18, text ID 43406589952 is not referenced.
Server: Msg 8961, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:312481), slot 4, text ID 43970068480 does not match its reference from page (1:296704), slot 16.
Server: Msg 8974, Level 16, State 1, Line 1
Text node referenced by more than one node. Object ID 2, text, ntext, or image node page (1:312481), slot 4, text ID 43970068480 is pointed to by page (1:335089), slot 2 and by page (1:296704), slot 16.
Server: Msg 8961, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:322092), slot 1, text ID 43997659136 does not match its reference from page (1:296704), slot 17.
Server: Msg 8974, Level 16, State 1, Line 1
Text node referenced by more than one node. Object ID 2, text, ntext, or image node page (1:322092), slot 1, text ID 43997659136 is pointed to by page (1:296704), slot 17 and by page (1:283669), slot 8.
Server: Msg 8961, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:338986), slot 1, text ID 43976032256 does not match its reference from page (1:296704), slot 18.
Server: Msg 8974, Level 16, State 1, Line 1
Text node referenced by more than one node. Object ID 2, text, ntext, or image node page (1:338986), slot 1, text ID 43976032256 is pointed to by page (1:338986), slot 2 and by page (1:296704), slot 18.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:345480), slot 3, text ID 43971313664 is not referenced.
Server: Msg 8961, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:345486), slot 2, text ID 43403444224 does not match its reference from page (1:97), slot 4.
Server: Msg 8974, Level 16, State 1, Line 1
Text node referenced by more than one node. Object ID 2, text, ntext, or image node page (1:345486), slot 2, text ID 43403444224 is pointed to by page (1:97), slot 4 and by page (1:345486), slot 3.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:345486), slot 3, text ID 43403444224 is not referenced.
Server: Msg 8961, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:345486), slot 4, text ID 43403509760 does not match its reference from page (1:97), slot 5.
Server: Msg 8974, Level 16, State 1, Line 1
Text node referenced by more than one node. Object ID 2, text, ntext, or image node page (1:345486), slot 4, text ID 43403509760 is pointed to by page (1:97), slot 5 and by page (1:345486), slot 5.
Server: Msg 8961, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:345486), slot 5, text ID 43403509760 does not match its reference from page (1:97), slot 6.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:345486), slot 12, text ID 43403575296 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:345486), slot 13, text ID 43403640832 is not referenced.
Server: Msg 8961, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:363638), slot 0, text ID 43976294400 does not match its reference from page (1:345486), slot 13.
Server: Msg 8974, Level 16, State 1, Line 1
Text node referenced by more than one node. Object ID 2, text, ntext, or image node page (1:363638), slot 0, text ID 43976294400 is pointed to by page (1:363639), slot 9 and by page (1:345486), slot 13.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:458906), slot 4, text ID 43403575296 is referenced by page (1:345486), slot 12, but was not seen in the scan.
There are 4480 rows in 278 pages for object 'sysindexes'.
CHECKDB found 0 allocation errors and 33 consistency errors in table 'sysindexes' (object ID 2).
DBCC results for 'syscolumns'.
There are 12854 rows in 254 pages for object 'syscolumns'.
DBCC results for 'systypes'.
There are 26 rows in 1 pages for object 'systypes'.
DBCC results for 'syscomments'.
There are 697 rows in 30 pages for object 'syscomments'.
DBCC results for 'sysfiles1'.
There are 2 rows in 1 pages for object 'sysfiles1'.
DBCC results for 'syspermissions'.
There are 52 rows in 1 pages for object 'syspermissions'.
DBCC results for 'sysusers'.
There are 15 rows in 1 pages for object 'sysusers'.
DBCC results for 'sysproperties'.
There are 0 rows in 0 pages for object 'sysproperties'.
DBCC results for 'sysdepends'.
There are 1588 rows in 8 pages for object 'sysdepends'.
DBCC results for 'sysreferences'.
There are 0 rows in 0 pages for object 'sysreferences'.
DBCC results for 'sysfulltextcatalogs'.
There are 0 rows in 0 pages for object 'sysfulltextcatalogs'.
DBCC results for 'sysfulltextnotify'.
There are 0 rows in 0 pages for object 'sysfulltextnotify'.
DBCC results for 'sysfilegroups'.
There are 1 rows in 1 pages for object 'sysfilegroups'.
DBCC results for 'ZZZ30Y'.
There are 27 rows in 1 pages for object 'ZZZ30Y'.
DBCC results for 'ZZZUC9'.
There are 61 rows in 2 pages for object 'ZZZUC9'.
DBCC results for 'SOURCEOFPAYMANT'.
There are 36 rows in 1 pages for object 'SOURCEOFPAYMANT'.
DBCC results for 'InsuranceA'.
There are 2041 rows in 62 pages for object 'InsuranceA'.
DBCC results for 'ZZZCAX'.
There are 1440 rows in 12 pages for object 'ZZZCAX'.
DBCC results for 'EOMFinClass'.
There are 1862 rows in 28 pages for object 'EOMFinClass'.
DBCC results for 'ZZZYBK'.
There are 57 rows in 1 pages for object 'ZZZYBK'.
DBCC results for 'ZZZUWQ'.
There are 62 rows in 2 pages for object 'ZZZUWQ'.
DBCC results for 'Appointment'.
There are 412194 rows in 7805 pages for object 'Appointment'.
DBCC results for 'SPECIALTY'.
There are 149 rows in 1 pages for object 'SPECIALTY'.
DBCC results for 'InsuranceB'.
There are 5 rows in 1 pages for object 'InsuranceB'.
DBCC results for 'ZZZTBV'.
There are 52 rows in 1 pages for object 'ZZZTBV'.
DBCC results for 'ApptApptTypes'.
There are 412523 rows in 2056 pages for object 'ApptApptTypes'.
DBCC results for 'EOMPractice'.
There are 36 rows in 1 pages for object 'EOMPractice'.
DBCC results for 'ZZZTPY'.
There are 64 rows in 2 pages for object 'ZZZTPY'.
DBCC results for 'ZZZY5J'.
There are 51 rows in 1 pages for object 'ZZZY5J'.
DBCC results for 'ZZZJJE'.
There are 59 rows in 1 pages for object 'ZZZJJE'.
DBCC results for 'ZZZBE8'.
There are 102 rows in 2 pages for object 'ZZZBE8'.
DBCC results for 'ZZZ4F4'.
There are 68 rows in 2 pages for object 'ZZZ4F4'.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:270936) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:266904), but was not allocated in any IAM. PFS flags 'IAM_PG MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:270138) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:266904), but was not allocated in any IAM. PFS flags 'IAM_PG MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:270140) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:266904), but was not allocated in any IAM. PFS flags 'IAM_PG MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:270142) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:266904), but was not allocated in any IAM. PFS flags 'IAM_PG MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:270989) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:266904), but was not allocated in any IAM. PFS flags 'IAM_PG MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:270991) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:266904), but was not allocated in any IAM. PFS flags 'IAM_PG MIXED_EXT ALLOCATED 0_PCT_FULL'.
DBCC results for 'StmtBilling'.
There are 473430 rows in 2886 pages for object 'StmtBilling'.
CHECKDB found 6 allocation errors and 0 consistency errors in table 'StmtBilling' (object ID 78623323).
DBCC results for 'InsuranceC'.
There are 1 rows in 1 pages for object 'InsuranceC'.
DBCC results for 'ZZZ2SU'.
There are 62 rows in 2 pages for object 'ZZZ2SU'.
DBCC results for 'ZZZVXB'.
There are 1 rows in 1 pages for object 'ZZZVXB'.
DBCC results for 'ZZZWFK'.
There are 63 rows in 2 pages for object 'ZZZWFK'.
DBCC results for 'ApptInstruct'.
There are 2 rows in 1 pages for object 'ApptInstruct'.
DBCC results for 'ZZZHPD'.
There are 73 rows in 2 pages for object 'ZZZHPD'.
DBCC results for 'EOMProvider'.
Server: Msg 7965, Level 16, State 2, Line 1
Table error: Could not check object ID 102212806, index ID 3 due to invalid allocation (IAM) page(s).
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 102212806, index ID 5 due to invalid allocation (IAM) page(s).
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 102212806, index ID 6 due to invalid allocation (IAM) page(s).
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 102212806, index ID 7 due to invalid allocation (IAM) page(s).
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 102212806, index ID 8 due to invalid allocation (IAM) page(s).
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 102212806, index ID 9 due to invalid allocation (IAM) page(s).
There are 1343 rows in 22 pages for object 'EOMProvider'.
DBCC results for 'ZZZZVY'.
There are 61 rows in 1 pages for object 'ZZZZVY'.
DBCC results for 'ZZZYBM'.
There are 53 rows in 1 pages for object 'ZZZYBM'.
DBCC results for 'ZZZW7I'.
There are 61 rows in 2 pages for object 'ZZZW7I'.
DBCC results for 'ZZZWXL'.
There are 61 rows in 1 pages for object 'ZZZWXL'.
CHECKDB found 0 allocation errors and 6 consistency errors in table 'ZZZWXL' (object ID 102212806).
DBCC results for 'ZZZXVK'.
There are 92 rows in 2 pages for object 'ZZZXVK'.
DBCC results for 'Strings'.
There are 0 rows in 0 pages for object 'Strings'.
DBCC results for 'ZZZTBX'.
There are 30 rows in 1 pages for object 'ZZZTBX'.
DBCC results for 'ApptType'.
There are 294 rows in 4 pages for object 'ApptType'.
DBCC results for 'Instruction'.
There are 1 rows in 1 pages for object 'Instruction'.
DBCC results for 'SMR_TRIGGER'.
There are 0 rows in 0 pages for object 'SMR_TRIGGER'.
DBCC results for 'ZZZEMI'.
There are 1440 rows in 8 pages for object 'ZZZEMI'.
DBCC results for 'ZZZQH2'.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:270112) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:266904), but was not allocated in any IAM. PFS flags 'IAM_PG MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:270928) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:266904), but was not allocated in any IAM. PFS flags 'IAM_PG MIXED_EXT ALLOCATED 0_PCT_FULL'.
There are 80 rows in 2 pages for object 'ZZZQH2'.
DBCC results for 'ZZZK40'.
There are 73 rows in 2 pages for object 'ZZZK40'.
DBCC results for 'ZZZ3YZ'.
There are 765 rows in 13 pages for object 'ZZZ3YZ'.
DBCC results for 'ZZZJJG'.
There are 59 rows in 1 pages for object 'ZZZJJG'.
DBCC results for 'InsuranceCoverage'.
There are 71954 rows in 2066 pages for object 'InsuranceCoverage'.
DBCC results for 'ZZZEMJ'.
There are 1440 rows in 8 pages for object 'ZZZEMJ'.
DBCC results for 'ApptTypeGroup'.
There are 2 rows in 1 pages for object 'ApptTypeGroup'.
DBCC results for 'PatientNotes'.
There are 24808 rows in 636 pages for object 'PatientNotes'.
CHECKDB found 2 allocation errors and 0 consistency errors in table 'PatientNotes' (object ID 151671588).
DBCC results for 'SMR_HL7QUE'.
There are 0 rows in 0 pages for object 'SMR_HL7QUE'.
DBCC results for 'ZZZYBO'.
There are 59 rows in 1 pages for object 'ZZZYBO'.
DBCC results for 'ZZZTNZ'.
There are 55 rows in 1 pages for object 'ZZZTNZ'.
DBCC results for 'ZZZZRU'.
There are 60 rows in 1 pages for object 'ZZZZRU'.
DBCC results for 'ZZZYQ0'.
There are 61 rows in 1 pages for object 'ZZZYQ0'.
DBCC results for 'ZZZ3Z0'.
There are 883 rows in 15 pages for object 'ZZZ3Z0'.
DBCC results for 'ZZZ4PB'.
There are 86 rows in 2 pages for object 'ZZZ4PB'.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:271646) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:266904), but was not allocated in any IAM. PFS flags 'IAM_PG MIXED_EXT ALLOCATED 0_PCT_FULL'.
DBCC results for 'TABLECHANGE'.
There are 5 rows in 1 pages for object 'TABLECHANGE'.
DBCC results for 'IntXref'.
There are 0 rows in 0 pages for object 'IntXref'.
DBCC results for 'ApptTypGrpItem'.
There are 1 rows in 1 pages for object 'ApptTypGrpItem'.
DBCC results for 'CarrierPlanNotes'.
There are 0 rows in 0 pages for object 'CarrierPlanNotes'.
DBCC results for 'ZZZPMD'.
There are 55 rows in 1 pages for object 'ZZZPMD'.
DBCC results for 'SMR_ERRORS'.
There are 0 rows in 0 pages for object 'SMR_ERRORS'.
DBCC results for 'ZZZNYX'.
There are 76 rows in 2 pages for object 'ZZZNYX'.
DBCC results for 'ZZZJJI'.
There are 59 rows in 1 pages for object 'ZZZJJI'.
DBCC results for 'TableVersions'.
There are 43625 rows in 365 pages for object 'TableVersions'.
CHECKDB found 1 allocation errors and 0 consistency errors in table 'TableVersions' (object ID 206623779).
DBCC results for 'LastRunTotals'.
There are 8 rows in 1 pages for object 'LastRunTotals'.
DBCC results for 'ARDetail'.
There are 0 rows in 0 pages for object 'ARDetail'.
DBCC results for 'ZZZD12'.
There are 109 rows in 2 pages for object 'ZZZD12'.
DBCC results for 'Occurance'.
There are 41678 rows in 606 pages for object 'Occurance'.
DBCC results for 'ZZZZG3'.
There are 43 rows in 1 pages for object 'ZZZZG3'.
DBCC results for 'SMR_TCPLOG'.
There are 0 rows in 0 pages for object 'SMR_TCPLOG'.
DBCC results for 'WOReportLBI'.
There are 0 rows in 0 pages for object 'WOReportLBI'.
Server: Msg 7965, Level 16, State 2, Line 1
Table error: Could not check object ID 283785460, index ID 3 due to invalid allocation (IAM) page(s).
DBCC results for 'ZZZZRW'.
There are 59 rows in 1 pages for object 'ZZZZRW'.
DBCC results for 'ZZZ4PD'.
There are 86 rows in 2 pages for object 'ZZZ4PD'.
DBCC results for 'TAXONOMY'.
There are 28 rows in 1 pages for object 'TAXONOMY'.
DBCC results for 'ZZZUOR'.
There are 66 rows in 2 pages for object 'ZZZUOR'.
DBCC results for 'Letters'.
There are 939 rows in 8 pages for object 'Letters'.
DBCC results for 'ZZZ3TF'.
There are 89 rows in 2 pages for object 'ZZZ3TF'.
DBCC results for 'ARDetailErrs'.
There are 0 rows in 0 pages for object 'ARDetailErrs'.
DBCC results for 'WaitList'.
There are 0 rows in 0 pages for object 'WaitList'.
DBCC results for 'dtproperties'.
There are 0 rows in 0 pages for object 'dtproperties'.
DBCC results for 'WOReportLBJ'.
There are 0 rows in 0 pages for object 'WOReportLBJ'.
DBCC results for 'ZZZOWE'.
There are 49 rows in 1 pages for object 'ZZZOWE'.
DBCC results for 'ZZZJJK'.
There are 59 rows in 1 pages for object 'ZZZJJK'.
DBCC results for 'ZZZVB2'.
There are 58 rows in 1 pages for object 'ZZZVB2'.
DBCC results for 'TCPIPLOG'.
There are 0 rows in 0 pages for object 'TCPIPLOG'.
DBCC results for 'lettersbmp'.
There are 1 rows in 1 pages for object 'lettersbmp'.
DBCC results for 'AssigntCode'.
There are 0 rows in 0 pages for object 'AssigntCode'.
DBCC results for 'ZZZYY9'.
There are 59 rows in 1 pages for object 'ZZZYY9'.
DBCC results for 'ZZZZG5'.
There are 61 rows in 2 pages for object 'ZZZZG5'.
DBCC results for 'ZZZX3S'.
There are 160634 rows in 4386 pages for object 'ZZZX3S'.
CHECKDB found 0 allocation errors and 1 consistency errors in table 'ZZZX3S' (object ID 283785460).
DBCC results for 'ZZZDTO'.
There are 61 rows in 2 pages for object 'ZZZDTO'.
DBCC results for 'ZZZUSS'.
There are 58 rows in 1 pages for object 'ZZZUSS'.
DBCC results for 'TemplateAssignmt'.
There are 1360 rows in 12 pages for object 'TemplateAssignmt'.
DBCC results for 'ZZZPAK'.
There are 69 rows in 2 pages for object 'ZZZPAK'.
DBCC results for 'Location'.
There are 0 rows in 0 pages for object 'Location'.
DBCC results for 'ZZZJXX'.
There are 1440 rows in 11 pages for object 'ZZZJXX'.
DBCC results for 'FL_PENSF'.
There are 1589 rows in 15 pages for object 'FL_PENSF'.
DBCC results for 'AUTOWO'.
There are 0 rows in 0 pages for object 'AUTOWO'.
DBCC results for 'ZZZUGO'.
There are 63 rows in 2 pages for object 'ZZZUGO'.
DBCC results for 'ZZZJXY'.
There are 1440 rows in 11 pages for object 'ZZZJXY'.
DBCC results for 'FL_PENSFA'.
There are 1589 rows in 15 pages for object 'FL_PENSFA'.
DBCC results for 'apptConf'.
There are 0 rows in 0 pages for object 'apptConf'.
DBCC results for 'ZZZCH8'.
There are 73 rows in 2 pages for object 'ZZZCH8'.
DBCC results for 'ZZZZ67'.
There are 56 rows in 1 pages for object 'ZZZZ67'.
DBCC results for 'TemplateItems'.
There are 9599 rows in 104 pages for object 'TemplateItems'.
DBCC results for 'ZZZ12J'.
There are 95 rows in 2 pages for object 'ZZZ12J'.
DBCC results for 'MessagePool'.
There are 4 rows in 1 pages for object 'MessagePool'.
DBCC results for 'FL_PENSFP'.
Server: Msg 8959, Level 16, State 3, Line 1
Table error: IAM page (1:173500) for object ID 356117701, index ID 3 is linked in the IAM chain for object ID 512642261, index ID 3 by page (0:0).
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:270113) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:266904), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 2575, Level 16, State 1, Line 1
IAM page (1:270114) is pointed to by the next pointer of IAM page (0:0) object ID 356117701 index ID 3 but was not detected in the scan.
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 356117701, index ID 3 due to invalid allocation (IAM) page(s).
Server: Msg 8946, Level 16, State 1, Line 1
Table error: Allocation page (1:270114) has invalid IAM_PAGE page header values. Type is 2. Check type, object ID and page ID on the page.
Server: Msg 8959, Level 16, State 1, Line 1
Table error: IAM page (1:173502) for object ID 356117701, index ID 4 is linked in the IAM chain for object ID 512642261, index ID 4 by page (0:0).
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:270115) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:266904), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 2575, Level 16, State 1, Line 1
IAM page (1:270116) is pointed to by the next pointer of IAM page (0:0) object ID 356117701 index ID 4 but was not detected in the scan.
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 356117701, index ID 4 due to invalid allocation (IAM) page(s).
Server: Msg 8946, Level 16, State 1, Line 1
Table error: Allocation page (1:270116) has invalid IAM_PAGE page header values. Type is 2. Check type, object ID and page ID on the page.
There are 1587 rows in 15 pages for object 'FL_PENSFP'.
DBCC results for 'Batch'.
There are 9658 rows in 188 pages for object 'Batch'.
DBCC results for 'ResSched_DEV'.
There are 0 rows in 0 pages for object 'ResSched_DEV'.
DBCC results for 'ZZZ476'.
There are 93 rows in 2 pages for object 'ZZZ476'.
DBCC results for 'ZZZWPT'.
Server: Msg 8959, Level 16, State 1, Line 1
Table error: IAM page (1:173512) for object ID 356117701, index ID 5 is linked in the IAM chain for object ID 512642261, index ID 5 by page (0:0).
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:270117) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:266904), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 2575, Level 16, State 1, Line 1
IAM page (1:270119) is pointed to by the next pointer of IAM page (0:0) object ID 356117701 index ID 5 but was not detected in the scan.
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 356117701, index ID 5 due to invalid allocation (IAM) page(s).
Server: Msg 8946, Level 16, State 1, Line 1
Table error: Allocation page (1:270119) has invalid IAM_PAGE page header values. Type is 2. Check type, object ID and page ID on the page.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:270137) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:266904), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 2575, Level 16, State 1, Line 1
IAM page (1:270138) is pointed to by the next pointer of IAM page (0:0) object ID 356117701 index ID 6 but was not detected in the scan.
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 356117701, index ID 6 due to invalid allocation (IAM) page(s).
Server: Msg 8946, Level 16, State 1, Line 1
Table error: Allocation page (1:270138) has invalid IAM_PAGE page header values. Type is 2. Check type, object ID and page ID on the page.
Server: Msg 8959, Level 16, State 1, Line 1
Table error: IAM page (1:276979) for object ID 356117701, index ID 6 is linked in the IAM chain for object ID 991263978, index ID 4 by page (0:0).
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:270139) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:266904), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 2575, Level 16, State 1, Line 1
IAM page (1:270140) is pointed to by the next pointer of IAM page (0:0) object ID 356117701 index ID 7 but was not detected in the scan.
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 356117701, index ID 7 due to invalid allocation (IAM) page(s).
Server: Msg 8946, Level 16, State 1, Line 1
Table error: Allocation page (1:270140) has invalid IAM_PAGE page header values. Type is 2. Check type, object ID and page ID on the page.
Server: Msg 8959, Level 16, State 3, Line 1
Table error: IAM page (1:276981) for object ID 356117701, index ID 7 is linked in the IAM chain for object ID 991263978, index ID 5 by page (0:0).
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:270141) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:266904), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 2575, Level 16, State 1, Line 1
IAM page (1:270142) is pointed to by the next pointer of IAM page (0:0) object ID 356117701 index ID 8 but was not detected in the scan.
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 356117701, index ID 8 due to invalid allocation (IAM) page(s).
Server: Msg 8946, Level 16, State 1, Line 1
Table error: Allocation page (1:270142) has invalid IAM_PAGE page header values. Type is 2. Check type, object ID and page ID on the page.
Server: Msg 8959, Level 16, State 1, Line 1
Table error: IAM page (1:276983) for object ID 356117701, index ID 8 is linked in the IAM chain for object ID 991263978, index ID 6 by page (0:0).
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:270191) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:266904), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 2575, Level 16, State 1, Line 1
IAM page (1:270928) is pointed to by the next pointer of IAM page (0:0) object ID 356117701 index ID 9 but was not detected in the scan.
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 356117701, index ID 9 due to invalid allocation (IAM) page(s).
Server: Msg 8946, Level 16, State 1, Line 1
Table error: Allocation page (1:270928) has invalid IAM_PAGE page header values. Type is 2. Check type, object ID and page ID on the page.
Server: Msg 8959, Level 16, State 1, Line 1
Table error: IAM page (1:280916) for object ID 356117701, index ID 9 is linked in the IAM chain for object ID 991263978, index ID 7 by page (0:0).
There are 52 rows in 1 pages for object 'ZZZWPT'.
CHECKDB found 19 allocation errors and 16 consistency errors in table 'ZZZWPT' (object ID 356117701).
DBCC results for 'FL_PENSFPA'.
There are 1588 rows in 16 pages for object 'FL_PENSFPA'.
DBCC results for 'FL_old_ENSFPA'.
There are 1090 rows in 11 pages for object 'FL_old_ENSFPA'.
DBCC results for 'ZZZYOB'.
There are 63 rows in 2 pages for object 'ZZZYOB'.
DBCC results for 'Templates'.
There are 80 rows in 1 pages for object 'Templates'.
DBCC results for 'MultipleFee'.
There are 0 rows in 0 pages for object 'MultipleFee'.
DBCC results for 'FL_PCYNSF5'.
There are 613 rows in 6 pages for object 'FL_PCYNSF5'.
DBCC results for 'batchbmp'.
There are 1 rows in 1 pages for object 'batchbmp'.
DBCC results for 'FL_old_ENSF'.
There are 1092 rows in 10 pages for object 'FL_old_ENSF'.
DBCC results for 'FL_PCYNSF'.
There are 620 rows in 6 pages for object 'FL_PCYNSF'.
DBCC results for 'FL_old_ENSFA'.
There are 1093 rows in 11 pages for object 'FL_old_ENSFA'.
DBCC results for 'ZZZGMI'.
There are 73 rows in 2 pages for object 'ZZZGMI'.
DBCC results for 'TempTableBmp'.
There are 1 rows in 1 pages for object 'TempTableBmp'.
DBCC results for 'NotesBump'.
There are 1 rows in 1 pages for object 'NotesBump'.
DBCC results for 'ZZZU4F'.
There are 43 rows in 1 pages for object 'ZZZU4F'.
DBCC results for 'FL_P1500_90'.
There are 180 rows in 2 pages for object 'FL_P1500_90'.
DBCC results for 'BenefitRanges'.
There are 62 rows in 1 pages for object 'BenefitRanges'.
DBCC results for 'FL_old_ENSFP'.
There are 1091 rows in 11 pages for object 'FL_old_ENSFP'.
DBCC results for 'ZZZ478'.
There are 93 rows in 2 pages for object 'ZZZ478'.
DBCC results for 'ZZZMN5'.
There are 58 rows in 1 pages for object 'ZZZMN5'.
DBCC results for 'ZZZY9T'.
There are 49 rows in 1 pages for object 'ZZZY9T'.
DBCC results for 'FL_P1500LAS'.
There are 175 rows in 2 pages for object 'FL_P1500LAS'.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:270119) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:266904), but was not allocated in any IAM. PFS flags 'IAM_PG MIXED_EXT ALLOCATED 0_PCT_FULL'.
DBCC results for 'ZZZCZD'.
There are 60 rows in 1 pages for object 'ZZZCZD'.
DBCC results for 'ZZZOUO'.
There are 81 rows in 2 pages for object 'ZZZOUO'.
DBCC results for 'ZZZXVU'.
There are 97 rows in 2 pages for object 'ZZZXVU'.
DBCC results for 'TESTTABLE'.
There are 0 rows in 0 pages for object 'TESTTABLE'.
DBCC results for 'FL_PCSLIP'.
There are 9 rows in 1 pages for object 'FL_PCSLIP'.
DBCC results for 'Budget'.
There are 0 rows in 0 pages for object 'Budget'.
DBCC results for 'FL_ENSF_prod'.
There are 1092 rows in 10 pages for object 'FL_ENSF_prod'.
DBCC results for 'FL_PFACE'.
There are 3 rows in 1 pages for object 'FL_PFACE'.
DBCC results for 'FL_ENSFPA_prod'.
There are 1090 rows in 11 pages for object 'FL_ENSFPA_prod'.
DBCC results for 'Tickler'.
There are 2605 rows in 38 pages for object 'Tickler'.
CHECKDB found 1 allocation errors and 0 consistency errors in table 'Tickler' (object ID 462624691).
DBCC results for 'OccurAsgnCode'.
There are 0 rows in 0 pages for object 'OccurAsgnCode'.
DBCC results for 'FL_PLOGIN'.
There are 42 rows in 1 pages for object 'FL_PLOGIN'.
DBCC results for 'budgetbmp'.
There are 0 rows in 0 pages for object 'budgetbmp'.
DBCC results for 'FL_ENSFP_prod'.
There are 1091 rows in 11 pages for object 'FL_ENSFP_prod'.
DBCC results for 'FL_PDMDINSR'.
There are 135 rows in 2 pages for object 'FL_PDMDINSR'.
DBCC results for 'FL_ENSFA_prod'.
There are 1093 rows in 11 pages for object 'FL_ENSFA_prod'.
Server: Msg 7965, Level 16, State 2, Line 1
Table error: Could not check object ID 512642261, index ID 3 due to invalid allocation (IAM) page(s).
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 512642261, index ID 4 due to invalid allocation (IAM) page(s).
Server: Msg 8959, Level 16, State 1, Line 1
Table error: IAM page (1:280944) for object ID 512642261, index ID 4 is linked in the IAM chain for object ID 991263978, index ID 9 by page (0:0).
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 512642261, index ID 5 due to invalid allocation (IAM) page(s).
Server: Msg 8959, Level 16, State 1, Line 1
Table error: IAM page (1:280947) for object ID 512642261, index ID 5 is linked in the IAM chain for object ID 283785460, index ID 3 by page (0:0).
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:270929) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:266904), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
DBCC results for 'ZZZOUQ'.
There are 48 rows in 1 pages for object 'ZZZOUQ'.
DBCC results for 'ticklerbmp'.
There are 1 rows in 1 pages for object 'ticklerbmp'.
DBCC results for 'ZZZHLK'.
There are 49 rows in 1 pages for object 'ZZZHLK'.
DBCC results for 'OccurenceCodes'.
There are 17 rows in 1 pages for object 'OccurenceCodes'.
DBCC results for 'FL_PDMDSTMT'.
There are 110 rows in 2 pages for object 'FL_PDMDSTMT'.
DBCC results for 'CARRIER_TYPE'.
There are 10 rows in 1 pages for object 'CARRIER_TYPE'.
DBCC results for 'FL_1500_90_prod'.
There are 180 rows in 2 pages for object 'FL_1500_90_prod'.
DBCC results for 'ZZZX5T'.
There are 62 rows in 2 pages for object 'ZZZX5T'.
DBCC results for 'ZZZ37K'.
There are 85 rows in 2 pages for object 'ZZZ37K'.
DBCC results for 'ZZZZE9'.
There are 59 rows in 1 pages for object 'ZZZZE9'.
DBCC results for 'ZZZWS0'.
Server: Msg 2575, Level 16, State 1, Line 1
IAM page (1:270930) is pointed to by the next pointer of IAM page (0:0) object ID 512642261 index ID 6 but was not detected in the scan.
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 512642261, index ID 6 due to invalid allocation (IAM) page(s).
Server: Msg 8946, Level 16, State 1, Line 1
Table error: Allocation page (1:270930) has invalid IAM_PAGE page header values. Type is 2. Check type, object ID and page ID on the page.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:270931) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:266904), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 2575, Level 16, State 1, Line 1
IAM page (1:270934) is pointed to by the next pointer of IAM page (0:0) object ID 512642261 index ID 7 but was not detected in the scan.
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 512642261, index ID 7 due to invalid allocation (IAM) page(s).
Server: Msg 8946, Level 16, State 1, Line 1
Table error: Allocation page (1:270934) has invalid IAM_PAGE page header values. Type is 2. Check type, object ID and page ID on the page.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:270935) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:266904), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 2575, Level 16, State 1, Line 1
IAM page (1:270936) is pointed to by the next pointer of IAM page (0:0) object ID 512642261 index ID 8 but was not detected in the scan.
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 512642261, index ID 8 due to invalid allocation (IAM) page(s).
Server: Msg 8946, Level 16, State 1, Line 1
Table error: Allocation page (1:270936) has invalid IAM_PAGE page header values. Type is 2. Check type, object ID and page ID on the page.
There are 62 rows in 2 pages for object 'ZZZWS0'.
CHECKDB found 7 allocation errors and 10 consistency errors in table 'ZZZWS0' (object ID 512642261).
DBCC results for 'ZZZLK5'.
There are 66 rows in 2 pages for object 'ZZZLK5'.
DBCC results for 'FL_PSTMT'.
There are 374 rows in 4 pages for object 'FL_PSTMT'.
DBCC results for 'FL_CSLIP_prod'.
There are 9 rows in 1 pages for object 'FL_CSLIP_prod'.
DBCC results for 'ZZZMXR'.
There are 51 rows in 1 pages for object 'ZZZMXR'.
DBCC results for 'TrackerTemplate'.
There are 18 rows in 1 pages for object 'TrackerTemplate'.
DBCC results for 'ZZZ3DO'.
There are 52 rows in 1 pages for object 'ZZZ3DO'.
DBCC results for 'Organization'.
There are 1 rows in 1 pages for object 'Organization'.
DBCC results for 'FL_PCY_BFWD'.
There are 158 rows in 2 pages for object 'FL_PCY_BFWD'.
DBCC results for 'FL_1500LASE_prod'.
There are 175 rows in 2 pages for object 'FL_1500LASE_prod'.
DBCC results for 'ZZZX3Z'.
There are 87 rows in 2 pages for object 'ZZZX3Z'.
DBCC results for 'ZZZUET'.
There are 63 rows in 2 pages for object 'ZZZUET'.
DBCC results for 'FL_PCY_OITE'.
There are 164 rows in 2 pages for object 'FL_PCY_OITE'.
DBCC results for 'FL_CY_BFWD_prod'.
There are 158 rows in 2 pages for object 'FL_CY_BFWD_prod'.
DBCC results for 'Patient'.
There are 44125 rows in 1513 pages for object 'Patient'.
DBCC results for 'FL_PPI_OITE'.
There are 188 rows in 2 pages for object 'FL_PPI_OITE'.
DBCC results for 'FL_CY_OITEM_prod'.
There are 164 rows in 2 pages for object 'FL_CY_OITEM_prod'.
DBCC results for 'ZZZES'.
There are 47 rows in 1 pages for object 'ZZZES'.
DBCC results for 'ZZZ69K'.
There are 1 rows in 1 pages for object 'ZZZ69K'.
DBCC results for 'ZZZOK9'.
There are 76 rows in 2 pages for object 'ZZZOK9'.
DBCC results for 'ZZZR5R'.
There are 50 rows in 1 pages for object 'ZZZR5R'.
DBCC results for 'FL_PSUPER'.
There are 189 rows in 2 pages for object 'FL_PSUPER'.
DBCC results for 'FL_CYNSF_prod'.
There are 620 rows in 6 pages for object 'FL_CYNSF_prod'.
DBCC results for 'transferauditbmp'.
There are 1 rows in 1 pages for object 'transferauditbmp'.
DBCC results for 'ZZZ2VI'.
There are 79 rows in 2 pages for object 'ZZZ2VI'.
DBCC results for 'patientbmp'.
There are 1 rows in 1 pages for object 'patientbmp'.
DBCC results for 'CarrierECS'.
There are 2220 rows in 31 pages for object 'CarrierECS'.
DBCC results for 'CarrierPlans'.
There are 6 rows in 1 pages for object 'CarrierPlans'.
DBCC results for 'FL_CYNSF5_prod'.
There are 613 rows in 6 pages for object 'FL_CYNSF5_prod'.
DBCC results for 'ZZZ49G'.
There are 52 rows in 1 pages for object 'ZZZ49G'.
DBCC results for 'ZZZE0A'.
There are 73 rows in 2 pages for object 'ZZZE0A'.
DBCC results for 'ZZZ8PW'.
There are 58 rows in 1 pages for object 'ZZZ8PW'.
DBCC results for 'FL_DMDINSR_prod'.
There are 123 rows in 2 pages for object 'FL_DMDINSR_prod'.
DBCC results for 'ZZZHFE'.
There are 1440 rows in 11 pages for object 'ZZZHFE'.
DBCC results for 'ZZZYMO'.
There are 67029 rows in 1855 pages for object 'ZZZYMO'.
DBCC results for 'TransForm'.
There are 0 rows in 0 pages for object 'TransForm'.
DBCC results for 'ZZZXS4'.
There are 62 rows in 2 pages for object 'ZZZXS4'.
DBCC results for 'PatientECS'.
There are 39914 rows in 327 pages for object 'PatientECS'.
DBCC results for 'ZZZS2C'.
There are 76 rows in 2 pages for object 'ZZZS2C'.
DBCC results for 'CarrNote'.
There are 0 rows in 0 pages for object 'CarrNote'.
DBCC results for 'FL_DMDSTMT_prod'.
There are 110 rows in 2 pages for object 'FL_DMDSTMT_prod'.
DBCC results for 'ZZZHFF'.
Server: Msg 7965, Level 16, State 2, Line 1
Table error: Could not check object ID 642738734, index ID 3 due to invalid allocation (IAM) page(s).
Server: Msg 8959, Level 16, State 1, Line 1
Table error: IAM page (1:276844) for object ID 642738734, index ID 3 is linked in the IAM chain for object ID 1218740786, index ID 8 by page (0:0).
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 642738734, index ID 4 due to invalid allocation (IAM) page(s).
Server: Msg 8959, Level 16, State 1, Line 1
Table error: IAM page (1:276846) for object ID 642738734, index ID 4 is linked in the IAM chain for object ID 1218740786, index ID 9 by page (0:0).
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 642738734, index ID 5 due to invalid allocation (IAM) page(s).
Server: Msg 8959, Level 16, State 1, Line 1
Table error: IAM page (1:276976) for object ID 642738734, index ID 5 is linked in the IAM chain for object ID 991263978, index ID 3 by page (0:0).
There are 1440 rows in 11 pages for object 'ZZZHFF'.
DBCC results for 'ZZZX04'.
There are 59 rows in 1 pages for object 'ZZZX04'.
CHECKDB found 3 allocation errors and 3 consistency errors in table 'ZZZX04' (object ID 642738734).
DBCC results for 'ZZZVFK'.
There are 61 rows in 2 pages for object 'ZZZVFK'.
DBCC results for 'ZZZY85'.
There are 48 rows in 1 pages for object 'ZZZY85'.
DBCC results for 'ZZZ419'.
There are 86 rows in 2 pages for object 'ZZZ419'.
DBCC results for 'ZZZXY4'.
There are 61 rows in 1 pages for object 'ZZZXY4'.
DBCC results for 'FL_FACE_prod'.
There are 3 rows in 1 pages for object 'FL_FACE_prod'.
DBCC results for 'ZZZHFG'.
There are 1440 rows in 11 pages for object 'ZZZHFG'.
DBCC results for 'ZZZYMP'.
There are 62438 rows in 1731 pages for object 'ZZZYMP'.
DBCC results for 'TransTracking'.
There are 1656 rows in 14 pages for object 'TransTracking'.
DBCC results for 'PatientMemos'.
There are 16383 rows in 207 pages for object 'PatientMemos'.
Server: Msg 8947, Level 16, State 1, Line 1
Table error: Multiple IAM pages for object ID 661498777, index ID 7 contain allocations for the same interval. IAM pages (1:248562) and (1:232994).
Server: Msg 8959, Level 16, State 1, Line 1
Table error: IAM page (1:248562) for object ID 661498777, index ID 7 is linked in the IAM chain for object ID 1707074509, index ID 8 by page (0:0).
Server: Msg 8947, Level 16, State 1, Line 1
Table error: Multiple IAM pages for object ID 661498777, index ID 9 contain allocations for the same interval. IAM pages (1:248566) and (1:232998).
Server: Msg 8959, Level 16, State 1, Line 1
Table error: IAM page (1:248566) for object ID 661498777, index ID 9 is linked in the IAM chain for object ID 1963075421, index ID 3 by page (0:0).
DBCC results for 'ZZZV5E'.
There are 64 rows in 2 pages for object 'ZZZV5E'.
DBCC results for 'ZZZWG2'.
There are 60 rows in 1 pages for object 'ZZZWG2'.
CHECKDB found 4 allocation errors and 0 consistency errors in table 'ZZZWG2' (object ID 661498777).
DBCC results for 'Charge2'.
There are 584173 rows in 12393 pages for object 'Charge2'.
DBCC results for 'FL_LOGIN_prod'.
There are 42 rows in 1 pages for object 'FL_LOGIN_prod'.
DBCC results for 'ZZZQPO'.
There are 1440 rows in 12 pages for object 'ZZZQPO'.
DBCC results for 'ZZZ104I'.
There are 62 rows in 2 pages for object 'ZZZ104I'.
DBCC results for 'FL_PI_OITEM_prod'.
There are 188 rows in 2 pages for object 'FL_PI_OITEM_prod'.
DBCC results for 'ZZZQPP'.
There are 1440 rows in 12 pages for object 'ZZZQPP'.
DBCC results for 'ZZZOUW'.
There are 48 rows in 1 pages for object 'ZZZOUW'.
DBCC results for 'TRIGCODE'.
There are 8 rows in 1 pages for object 'TRIGCODE'.
DBCC results for 'ChargeBilling'.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:270934) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:266904), but was not allocated in any IAM. PFS flags 'IAM_PG MIXED_EXT ALLOCATED 0_PCT_FULL'.
There are 657634 rows in 6116 pages for object 'ChargeBilling'.
CHECKDB found 1 allocation errors and 0 consistency errors in table 'ChargeBilling' (object ID 693577509).
DBCC results for 'FL_STMT_prod'.
There are 374 rows in 4 pages for object 'FL_STMT_prod'.
DBCC results for 'ZZZ1X3'.
There are 64 rows in 2 pages for object 'ZZZ1X3'.
DBCC results for 'ZZZXJY'.
There are 42 rows in 1 pages for object 'ZZZXJY'.
DBCC results for 'ZZZFHN'.
There are 73 rows in 2 pages for object 'ZZZFHN'.
DBCC results for 'ZZZ8U'.
There are 89 rows in 2 pages for object 'ZZZ8U'.
DBCC results for 'ZZZY87'.
There are 54 rows in 1 pages for object 'ZZZY87'.
DBCC results for 'FL_SUPER_prod'.
There are 289 rows in 3 pages for object 'FL_SUPER_prod'.
DBCC results for 'TRIGGERERRS'.
There are 0 rows in 0 pages for object 'TRIGGERERRS'.
DBCC results for 'ZZZK0K'.
There are 41 rows in 1 pages for object 'ZZZK0K'.
DBCC results for 'ZZZA2D'.
There are 62 rows in 2 pages for object 'ZZZA2D'.
DBCC results for 'patientnotesbmp'.
There are 1 rows in 1 pages for object 'patientnotesbmp'.
DBCC results for 'FL_P1500_05'.
There are 231 rows in 3 pages for object 'FL_P1500_05'.
DBCC results for 'ChargeCredits'.
There are 551021 rows in 4496 pages for object 'ChargeCredits'.
DBCC results for 'FL_UB92_prod'.
There are 216 rows in 2 pages for object 'FL_UB92_prod'.
DBCC results for 'FL_PDINS_05'.
There are 231 rows in 3 pages for object 'FL_PDINS_05'.
DBCC results for 'ZZZHS2'.
There are 1440 rows in 8 pages for object 'ZZZHS2'.
DBCC results for 'ZZZTKC'.
There are 40 rows in 1 pages for object 'ZZZTKC'.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:271025) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:266904), but was not allocated in any IAM. PFS flags 'IAM_PG MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:270114) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:266904), but was not allocated in any IAM. PFS flags 'IAM_PG MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:270116) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:266904), but was not allocated in any IAM. PFS flags 'IAM_PG MIXED_EXT ALLOCATED 0_PCT_FULL'.
DBCC results for 'TransferAudit'.
There are 10301 rows in 270 pages for object 'TransferAudit'.
DBCC results for 'WOReport4ZR'.
There are 0 rows in 0 pages for object 'WOReport4ZR'.
DBCC results for 'PatientNotesType'.
There are 4 rows in 1 pages for object 'PatientNotesType'.
DBCC results for 'ZZZPR0'.
There are 64 rows in 2 pages for object 'ZZZPR0'.
DBCC results for 'ZZZ20W'.
There are 54 rows in 1 pages for object 'ZZZ20W'.
DBCC results for 'ChargePayments'.
There are 814801 rows in 6526 pages for object 'ChargePayments'.
DBCC results for 'ZZZVNS'.
There are 62 rows in 2 pages for object 'ZZZVNS'.
DBCC results for 'ZZZHS3'.
There are 1440 rows in 8 pages for object 'ZZZHS3'.
DBCC results for 'ZZZXK0'.
There are 63 rows in 2 pages for object 'ZZZXK0'.
DBCC results for 'ZZZ41E'.
There are 86 rows in 2 pages for object 'ZZZ41E'.
DBCC results for 'ZZZDRZ'.
There are 51 rows in 1 pages for object 'ZZZDRZ'.
DBCC results for 'TYPEOFINSURANCE'.
There are 10 rows in 1 pages for object 'TYPEOFINSURANCE'.
DBCC results for 'Payments'.
There are 572977 rows in 12911 pages for object 'Payments'.
CHECKDB found 3 allocation errors and 0 consistency errors in table 'Payments' (object ID 786101841).
DBCC results for 'Provider'.
There are 41 rows in 3 pages for object 'Provider'.
DBCC results for 'ZZZ3TX'.
There are 73 rows in 2 pages for object 'ZZZ3TX'.
DBCC results for 'ChargePaymentsNote'.
There are 0 rows in 0 pages for object 'ChargePaymentsNote'.
DBCC results for 'FL_1500_05'.
There are 232 rows in 3 pages for object 'FL_1500_05'.
DBCC results for 'ZZZZ8P'.
There are 57 rows in 1 pages for object 'ZZZZ8P'.
DBCC results for 'UserColumns'.
There are 6459 rows in 48 pages for object 'UserColumns'.
DBCC results for 'ZZZ1B6'.
There are 49 rows in 1 pages for object 'ZZZ1B6'.
DBCC results for 'ZZZ3VS'.
There are 49 rows in 1 pages for object 'ZZZ3VS'.
DBCC results for 'PeriodTracking'.
There are 111 rows in 1 pages for object 'PeriodTracking'.
DBCC results for 'ReferingProvider'.
There are 3894 rows in 196 pages for object 'ReferingProvider'.
DBCC results for 'Charges'.
There are 584172 rows in 35017 pages for object 'Charges'.
DBCC results for 'ZZZROC'.
There are 49 rows in 1 pages for object 'ZZZROC'.
DBCC results for 'FL_MEDI_05'.
There are 211 rows in 3 pages for object 'FL_MEDI_05'.
DBCC results for 'ZZZZUI'.
There are 68 rows in 2 pages for object 'ZZZZUI'.
DBCC results for 'ZZZ1T2'.
There are 773 rows in 13 pages for object 'ZZZ1T2'.
DBCC results for 'ZZZZ6V'.
There are 86 rows in 2 pages for object 'ZZZZ6V'.
DBCC results for 'ZZZREA'.
There are 84 rows in 2 pages for object 'ZZZREA'.
DBCC results for 'UserLogging'.
There are 2 rows in 2 pages for object 'UserLogging'.
DBCC results for 'PermDiag'.
There are 2 rows in 1 pages for object 'PermDiag'.
DBCC results for 'Practice'.
There are 1 rows in 1 pages for object 'Practice'.
DBCC results for 'CLAIM_TEMP'.
There are 0 rows in 0 pages for object 'CLAIM_TEMP'.
DBCC results for 'ZZZVHU'.
There are 61 rows in 1 pages for object 'ZZZVHU'.
DBCC results for 'ZZZ3LY'.
There are 93 rows in 2 pages for object 'ZZZ3LY'.
DBCC results for 'ZZZNXN'.
There are 87 rows in 2 pages for object 'ZZZNXN'.
DBCC results for 'ZZZZSO'.
There are 59 rows in 1 pages for object 'ZZZZSO'.
DBCC results for 'ZZZ2ZU'.
There are 24 rows in 1 pages for object 'ZZZ2ZU'.
DBCC results for 'ZZZ4HV'.
There are 0 rows in 0 pages for object 'ZZZ4HV'.
DBCC results for 'ZZZHNZ'.
There are 1440 rows in 8 pages for object 'ZZZHNZ'.
DBCC results for 'UserName'.
There are 57 rows in 2 pages for object 'UserName'.
DBCC results for 'ZZZ3VU'.
There are 49 rows in 1 pages for object 'ZZZ3VU'.
DBCC results for 'ZZZG0G'.
There are 11608 rows in 318 pages for object 'ZZZG0G'.
DBCC results for 'PlanCoverage'.
There are 229 rows in 3 pages for object 'PlanCoverage'.
DBCC results for 'Facility'.
There are 12 rows in 1 pages for object 'Facility'.
DBCC results for 'ZZZIVG'.
There are 73 rows in 2 pages for object 'ZZZIVG'.
DBCC results for 'ClientNote'.
There are 237 rows in 5 pages for object 'ClientNote'.
DBCC results for 'ZZZ1T4'.
There are 773 rows in 13 pages for object 'ZZZ1T4'.
DBCC results for 'ZZZFDP'.
There are 0 rows in 0 pages for object 'ZZZFDP'.
DBCC results for 'UserVars'.
There are 1 rows in 1 pages for object 'UserVars'.
DBCC results for 'PowerFile'.
There are 1088 rows in 14 pages for object 'PowerFile'.
DBCC results for 'EpsdtCodes'.
There are 6 rows in 1 pages for object 'EpsdtCodes'.
DBCC results for 'ClosedDay'.
There are 2209 rows in 13 pages for object 'ClosedDay'.
DBCC results for 'ZZZJUA'.
There are 95 rows in 2 pages for object 'ZZZJUA'.
DBCC results for 'FL_DINS_05'.
There are 232 rows in 3 pages for object 'FL_DINS_05'.
DBCC results for 'ZZZI4J'.
There are 4320 rows in 23 pages for object 'ZZZI4J'.
DBCC results for 'ZZZNXP'.
There are 87 rows in 2 pages for object 'ZZZNXP'.
DBCC results for 'ZZZDU8'.
There are 45 rows in 1 pages for object 'ZZZDU8'.
DBCC results for 'ZZZW4A'.
There are 100 rows in 2 pages for object 'ZZZW4A'.
DBCC results for 'ValueCodes'.
There are 19 rows in 1 pages for object 'ValueCodes'.
DBCC results for 'ZZZ3VW'.
There are 49 rows in 1 pages for object 'ZZZ3VW'.
DBCC results for 'ZZZI4K'.
There are 4464 rows in 24 pages for object 'ZZZI4K'.
DBCC results for 'PowerfileTemplate'.
There are 1 rows in 1 pages for object 'PowerfileTemplate'.
DBCC results for 'ZZZIVI'.
There are 73 rows in 2 pages for object 'ZZZIVI'.
DBCC results for 'ZZZH5'.
There are 82 rows in 2 pages for object 'ZZZH5'.
DBCC results for 'CollectionLetters'.
There are 4125 rows in 45 pages for object 'CollectionLetters'.
DBCC results for 'ZZZZ0P'.
There are 62 rows in 2 pages for object 'ZZZZ0P'.
DBCC results for 'ZZZH7D'.
There are 73 rows in 2 pages for object 'ZZZH7D'.
DBCC results for 'ZZZ9MG'.
There are 9 rows in 1 pages for object 'ZZZ9MG'.
Server: Msg 7965, Level 16, State 2, Line 1
Table error: Could not check object ID 991263978, index ID 3 due to invalid allocation (IAM) page(s).
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 991263978, index ID 4 due to invalid allocation (IAM) page(s).
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 991263978, index ID 5 due to invalid allocation (IAM) page(s).
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 991263978, index ID 6 due to invalid allocation (IAM) page(s).
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 991263978, index ID 7 due to invalid allocation (IAM) page(s).
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 991263978, index ID 9 due to invalid allocation (IAM) page(s).
DBCC results for 'ZZZHFP'.
There are 53 rows in 1 pages for object 'ZZZHFP'.
DBCC results for 'FL_DMED_05'.
There are 211 rows in 2 pages for object 'FL_DMED_05'.
DBCC results for 'ZZZVFV'.
There are 62 rows in 2 pages for object 'ZZZVFV'.
DBCC results for 'ZZZ41N'.
There are 86 rows in 2 pages for object 'ZZZ41N'.
DBCC results for 'FL_CYNSF'.
There are 620 rows in 6 pages for object 'FL_CYNSF'.
DBCC results for 'ZZZ3G3'.
There are 87 rows in 2 pages for object 'ZZZ3G3'.
DBCC results for 'ZZZNP7'.
There are 100 rows in 2 pages for object 'ZZZNP7'.
DBCC results for 'PowerTracker'.
There are 133481 rows in 1725 pages for object 'PowerTracker'.
DBCC results for 'collectionlettersbmp'.
There are 1 rows in 1 pages for object 'collectionlettersbmp'.
DBCC results for 'ZZZX2I'.
There are 76 rows in 2 pages for object 'ZZZX2I'.
CHECKDB found 0 allocation errors and 6 consistency errors in table 'ZZZX2I' (object ID 991263978).
DBCC results for 'FL_ENSFP'.
There are 1547 rows in 17 pages for object 'FL_ENSFP'.
DBCC results for 'ZZZNXR'.
There are 87 rows in 2 pages for object 'ZZZNXR'.
DBCC results for 'ZZZW4C'.
There are 100 rows in 2 pages for object 'ZZZW4C'.
DBCC results for 'FL_CYNSF5'.
There are 613 rows in 6 pages for object 'FL_CYNSF5'.
DBCC results for 'WOReport'.
There are 0 rows in 0 pages for object 'WOReport'.
DBCC results for 'ZZZ3VY'.
There are 58 rows in 1 pages for object 'ZZZ3VY'.
DBCC results for 'CONCURRENCY'.
There are 0 rows in 0 pages for object 'CONCURRENCY'.
DBCC results for 'Results'.
There are 42 rows in 3 pages for object 'Results'.
DBCC results for 'ZZZ5S1'.
There are 51 rows in 1 pages for object 'ZZZ5S1'.
DBCC results for 'FL_ENSF'.
There are 1549 rows in 18 pages for object 'FL_ENSF'.
DBCC results for 'InsuranceCarrier'.
There are 2220 rows in 173 pages for object 'InsuranceCarrier'.
DBCC results for 'ZZZZAR'.
There are 60 rows in 1 pages for object 'ZZZZAR'.
DBCC results for 'Zipcode'.
There are 5884 rows in 52 pages for object 'Zipcode'.
DBCC results for 'ZZZ2VW'.
There are 18 rows in 1 pages for object 'ZZZ2VW'.
DBCC results for 'PracticeXREF'.
There are 675 rows in 5 pages for object 'PracticeXREF'.
DBCC results for 'ZZZVQ7'.
There are 76 rows in 2 pages for object 'ZZZVQ7'.
DBCC results for 'CONCURRENCY_ITEM'.
There are 0 rows in 0 pages for object 'CONCURRENCY_ITEM'.
DBCC results for 'ZZZF5P'.
There are 30 rows in 1 pages for object 'ZZZF5P'.
DBCC results for 'FL_ENSFA'.
There are 1589 rows in 15 pages for object 'FL_ENSFA'.
DBCC results for 'ZZZNXT'.
There are 87 rows in 2 pages for object 'ZZZNXT'.
DBCC results for 'ZZZSAT'.
There are 49 rows in 1 pages for object 'ZZZSAT'.
DBCC results for 'ZZZ3W0'.
There are 49 rows in 1 pages for object 'ZZZ3W0'.
DBCC results for 'ProcedureCategory'.
There are 18 rows in 1 pages for object 'ProcedureCategory'.
DBCC results for 'ZZZ1JL'.
There are 53 rows in 1 pages for object 'ZZZ1JL'.
DBCC results for 'ConditionCode'.
There are 28 rows in 1 pages for object 'ConditionCode'.
DBCC results for 'ZZZ382'.
There are 90 rows in 2 pages for object 'ZZZ382'.
DBCC results for 'ZZZ1VB'.
There are 44 rows in 1 pages for object 'ZZZ1VB'.
DBCC results for 'FL_ENSFPA'.
There are 1588 rows in 15 pages for object 'FL_ENSFPA'.
DBCC results for 'FL_PUB92'.
There are 216 rows in 2 pages for object 'FL_PUB92'.
DBCC results for 'ProcedureModify'.
There are 1 rows in 1 pages for object 'ProcedureModify'.
DBCC results for 'Credits'.
There are 337734 rows in 6937 pages for object 'Credits'.
DBCC results for 'ZZZ158'.
There are 54 rows in 1 pages for object 'ZZZ158'.
DBCC results for 'FL_ENSFPMD'.
There are 1556 rows in 15 pages for object 'FL_ENSFPMD'.
DBCC results for 'ZZZ7Q8'.
There are 51 rows in 1 pages for object 'ZZZ7Q8'.
DBCC results for 'ZZZNXV'.
There are 87 rows in 2 pages for object 'ZZZNXV'.
DBCC results for 'ZZZ3W2'.
There are 49 rows in 1 pages for object 'ZZZ3W2'.
DBCC results for 'ProcedureNotes'.
There are 4 rows in 1 pages for object 'ProcedureNotes'.
DBCC results for 'CUSTOM_REPORTS'.
There are 5 rows in 1 pages for object 'CUSTOM_REPORTS'.
DBCC results for 'FL_ENSFPMSP'.
There are 1556 rows in 17 pages for object 'FL_ENSFPMSP'.
DBCC results for 'ZZZ561'.
Server: Msg 7965, Level 16, State 2, Line 1
Table error: Could not check object ID 1218740786, index ID 6 due to invalid allocation (IAM) page(s).
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 1218740786, index ID 8 due to invalid allocation (IAM) page(s).
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 1218740786, index ID 9 due to invalid allocation (IAM) page(s).
There are 6207 rows in 621 pages for object 'ZZZ561'.
DBCC results for 'ProcedureTable'.
There are 567 rows in 20 pages for object 'ProcedureTable'.
DBCC results for 'CYNSFProv'.
There are 0 rows in 0 pages for object 'CYNSFProv'.
DBCC results for 'ZZZ15A'.
There are 54 rows in 1 pages for object 'ZZZ15A'.
DBCC results for 'ZZZ9A'.
There are 93 rows in 2 pages for object 'ZZZ9A'.
DBCC results for 'ZZZDUG'.
There are 27 rows in 1 pages for object 'ZZZDUG'.
DBCC results for 'ZZZZ91'.
There are 55 rows in 1 pages for object 'ZZZZ91'.
DBCC results for 'ZZZK4Y'.
There are 90 rows in 2 pages for object 'ZZZK4Y'.
DBCC results for 'ZZZ5K3'.
There are 86 rows in 2 pages for object 'ZZZ5K3'.
DBCC results for 'ZZZ3IC'.
There are 32 rows in 1 pages for object 'ZZZ3IC'.
DBCC results for 'ZZZU79'.
There are 63 rows in 2 pages for object 'ZZZU79'.
DBCC results for 'ZZZ3W4'.
There are 49 rows in 1 pages for object 'ZZZ3W4'.
DBCC results for 'ProcRVUClass'.
There are 0 rows in 0 pages for object 'ProcRVUClass'.
DBCC results for 'DAYSHEET'.
There are 0 rows in 0 pages for object 'DAYSHEET'.
DBCC results for 'ZZZZZ0'.
There are 57 rows in 1 pages for object 'ZZZZZ0'.
DBCC results for 'ZZZX0M'.
There are 57 rows in 1 pages for object 'ZZZX0M'.
CHECKDB found 0 allocation errors and 3 consistency errors in table 'ZZZX0M' (object ID 1218740786).
DBCC results for 'ZZZYT0'.
There are 60 rows in 1 pages for object 'ZZZYT0'.
DBCC results for 'ProvDepart'.
There are 0 rows in 0 pages for object 'ProvDepart'.
DBCC results for 'ZZZRUQ'.
There are 50 rows in 1 pages for object 'ZZZRUQ'.
DBCC results for 'DebitCredits'.
There are 162 rows in 2 pages for object 'DebitCredits'.
DBCC results for 'ZZZXYN'.
There are 47 rows in 1 pages for object 'ZZZXYN'.
DBCC results for 'ZZZ3W6'.
There are 58 rows in 1 pages for object 'ZZZ3W6'.
DBCC results for 'ZZZJF'.
There are 53 rows in 1 pages for object 'ZZZJF'.
DBCC results for 'DebitPayments'.
There are 2880 rows in 26 pages for object 'DebitPayments'.
DBCC results for 'ZZZQM9'.
There are 76 rows in 2 pages for object 'ZZZQM9'.
DBCC results for 'ZZZR2M'.
There are 64 rows in 2 pages for object 'ZZZR2M'.
DBCC results for 'ProviderECS'.
There are 33 rows in 1 pages for object 'ProviderECS'.
DBCC results for 'FL_MEDICARE'.
There are 182 rows in 2 pages for object 'FL_MEDICARE'.
DBCC results for 'ZZZV5Y'.
There are 57 rows in 1 pages for object 'ZZZV5Y'.
DBCC results for 'DebitPaymentsNote'.
There are 0 rows in 0 pages for object 'DebitPaymentsNote'.
DBCC results for 'ZZZPM'.
There are 53 rows in 1 pages for object 'ZZZPM'.
DBCC results for 'ZZZBF'.
There are 51 rows in 1 pages for object 'ZZZBF'.
DBCC results for 'ZZZXEM'.
There are 60 rows in 1 pages for object 'ZZZXEM'.
DBCC results for 'ZZZ3W8'.
There are 58 rows in 1 pages for object 'ZZZ3W8'.
DBCC results for 'ZZZJH'.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:239048) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:234552), but was not allocated in any IAM. PFS flags 'IAM_PG MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:239050) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:234552), but was not allocated in any IAM. PFS flags 'IAM_PG MIXED_EXT ALLOCATED 0_PCT_FULL'.
There are 53 rows in 1 pages for object 'ZZZJH'.
DBCC results for 'ProviderXREF'.
There are 10921 rows in 80 pages for object 'ProviderXREF'.
DBCC results for 'FL_DMDINSLA'.
There are 181 rows in 2 pages for object 'FL_DMDINSLA'.
DBCC results for 'Debits'.
There are 3266 rows in 83 pages for object 'Debits'.
CHECKDB found 2 allocation errors and 0 consistency errors in table 'Debits' (object ID 1333579789).
DBCC results for 'ZZZZJ3'.
There are 60 rows in 1 pages for object 'ZZZZJ3'.
DBCC results for 'ChargeReceiveAudit'.
There are 0 rows in 0 pages for object 'ChargeReceiveAudit'.
DBCC results for 'ZZZR2O'.
There are 40 rows in 1 pages for object 'ZZZR2O'.
DBCC results for 'ChargeRecvErrorDtl'.
There are 0 rows in 0 pages for object 'ChargeRecvErrorDtl'.
DBCC results for 'ZZZ23P'.
There are 86 rows in 2 pages for object 'ZZZ23P'.
DBCC results for 'ProvLocation'.
There are 0 rows in 0 pages for object 'ProvLocation'.
DBCC results for 'Department'.
There are 0 rows in 0 pages for object 'Department'.
DBCC results for 'ChargeRecvErrorHdr'.
There are 0 rows in 0 pages for object 'ChargeRecvErrorHdr'.
DBCC results for 'ZZZUJO'.
There are 65 rows in 2 pages for object 'ZZZUJO'.
DBCC results for 'ZZZPLJ'.
There are 76 rows in 2 pages for object 'ZZZPLJ'.
DBCC results for 'DemoReceiveAudit'.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:271644) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:266904), but was not allocated in any IAM. PFS flags 'IAM_PG MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:270930) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:266904), but was not allocated in any IAM. PFS flags 'IAM_PG MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:270988) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:266904), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
There are 0 rows in 0 pages for object 'DemoReceiveAudit'.
DBCC results for 'ZZZ2Y9'.
There are 97 rows in 2 pages for object 'ZZZ2Y9'.
DBCC results for 'ZZZ3WA'.
There are 47 rows in 1 pages for object 'ZZZ3WA'.
DBCC results for 'PurgeBatch'.
There are 0 rows in 0 pages for object 'PurgeBatch'.
DBCC results for 'FL_CHRTBOY'.
There are 9 rows in 1 pages for object 'FL_CHRTBOY'.
DBCC results for 'Diagnosis'.
There are 2987 rows in 45 pages for object 'Diagnosis'.
CHECKDB found 2 allocation errors and 0 consistency errors in table 'Diagnosis' (object ID 1397580017).
DBCC results for 'DemoRecvErrorDtl'.
There are 0 rows in 0 pages for object 'DemoRecvErrorDtl'.
DBCC results for 'ZZZR2Q'.
There are 40 rows in 1 pages for object 'ZZZR2Q'.
DBCC results for 'ZZZIDE'.
There are 54 rows in 1 pages for object 'ZZZIDE'.
DBCC results for 'PurgeItem'.
There are 0 rows in 0 pages for object 'PurgeItem'.
DBCC results for 'FL_CHRTGIRL'.
There are 8 rows in 1 pages for object 'FL_CHRTGIRL'.
DBCC results for 'DlgSettings'.
There are 1860 rows in 101 pages for object 'DlgSettings'.
DBCC results for 'HL7QUE_IN'.
There are 0 rows in 0 pages for object 'HL7QUE_IN'.
DBCC results for 'ZZZWUO'.
Server: Msg 2575, Level 16, State 1, Line 1
IAM page (1:270989) is pointed to by the next pointer of IAM page (0:0) object ID 1437169557 index ID 3 but was not detected in the scan.
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 1437169557, index ID 3 due to invalid allocation (IAM) page(s).
Server: Msg 8946, Level 16, State 1, Line 1
Table error: Allocation page (1:270989) has invalid IAM_PAGE page header values. Type is 2. Check type, object ID and page ID on the page.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:270990) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:266904), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 2575, Level 16, State 1, Line 1
IAM page (1:270991) is pointed to by the next pointer of IAM page (0:0) object ID 1437169557 index ID 4 but was not detected in the scan.
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 1437169557, index ID 4 due to invalid allocation (IAM) page(s).
Server: Msg 8946, Level 16, State 1, Line 1
Table error: Allocation page (1:270991) has invalid IAM_PAGE page header values. Type is 2. Check type, object ID and page ID on the page.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:271024) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:266904), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 2575, Level 16, State 1, Line 1
IAM page (1:271025) is pointed to by the next pointer of IAM page (0:0) object ID 1437169557 index ID 5 but was not detected in the scan.
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 1437169557, index ID 5 due to invalid allocation (IAM) page(s).
Server: Msg 8946, Level 16, State 1, Line 1
Table error: Allocation page (1:271025) has invalid IAM_PAGE page header values. Type is 2. Check type, object ID and page ID on the page.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:271643) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:266904), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 2575, Level 16, State 1, Line 1
IAM page (1:271644) is pointed to by the next pointer of IAM page (0:0) object ID 1437169557 index ID 6 but was not detected in the scan.
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 1437169557, index ID 6 due to invalid allocation (IAM) page(s).
Server: Msg 8946, Level 16, State 1, Line 1
Table error: Allocation page (1:271644) has invalid IAM_PAGE page header values. Type is 2. Check type, object ID and page ID on the page.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:271645) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:266904), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 2575, Level 16, State 1, Line 1
IAM page (1:271646) is pointed to by the next pointer of IAM page (0:0) object ID 1437169557 index ID 7 but was not detected in the scan.
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 1437169557, index ID 7 due to invalid allocation (IAM) page(s).
Server: Msg 8946, Level 16, State 1, Line 1
Table error: Allocation page (1:271646) has invalid IAM_PAGE page header values. Type is 2. Check type, object ID and page ID on the page.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:271647) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:266904), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 1437169557, index ID 8 due to invalid allocation (IAM) page(s).
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 1437169557, index ID 9 due to invalid allocation (IAM) page(s).
There are 63 rows in 2 pages for object 'ZZZWUO'.
CHECKDB found 11 allocation errors and 12 consistency errors in table 'ZZZWUO' (object ID 1437169557).
DBCC results for 'ZZZIFI'.
There are 47 rows in 1 pages for object 'ZZZIFI'.
DBCC results for 'ZZZ9T1'.
There are 96 rows in 2 pages for object 'ZZZ9T1'.
DBCC results for 'AutoWO1037'.
There are 4 rows in 1 pages for object 'AutoWO1037'.
DBCC results for 'SyncData'.
There are 1 rows in 1 pages for object 'SyncData'.
DBCC results for 'ZZZ3K'.
There are 87 rows in 2 pages for object 'ZZZ3K'.
DBCC results for 'ZZZ1E'.
There are 87 rows in 2 pages for object 'ZZZ1E'.
DBCC results for 'ZZZ3WC'.
There are 61 rows in 2 pages for object 'ZZZ3WC'.
DBCC results for 'ZZZYL1'.
There are 60 rows in 1 pages for object 'ZZZYL1'.
DBCC results for 'Reasons'.
There are 212 rows in 2 pages for object 'Reasons'.
DBCC results for 'FL_CSLIPLZJ'.
There are 124 rows in 2 pages for object 'FL_CSLIPLZJ'.
DBCC results for 'Documents'.
There are 61639 rows in 875 pages for object 'Documents'.
DBCC results for 'ZZZDYZ'.
There are 97 rows in 2 pages for object 'ZZZDYZ'.
DBCC results for 'ZZZ1038'.
There are 1272 rows in 12 pages for object 'ZZZ1038'.
DBCC results for 'ZZZFUI'.
There are 32 rows in 1 pages for object 'ZZZFUI'.
DBCC results for 'ZZZM5T'.
There are 73 rows in 2 pages for object 'ZZZM5T'.
DBCC results for 'Recall'.
There are 9 rows in 1 pages for object 'Recall'.
DBCC results for 'FL_LABLBL'.
There are 34 rows in 1 pages for object 'FL_LABLBL'.
DBCC results for 'documentsbmp'.
There are 1 rows in 1 pages for object 'documentsbmp'.
DBCC results for 'ZZZX6X'.
There are 150542 rows in 4113 pages for object 'ZZZX6X'.
DBCC results for 'ZZZD0B'.
There are 66 rows in 2 pages for object 'ZZZD0B'.
DBCC results for 'ZZZ3WE'.
There are 73 rows in 2 pages for object 'ZZZ3WE'.
DBCC results for 'ZZZXSW'.
There are 95 rows in 2 pages for object 'ZZZXSW'.
DBCC results for 'recallbmp'.
There are 1 rows in 1 pages for object 'recallbmp'.
DBCC results for 'FL_LABLBLS'.
There are 44 rows in 1 pages for object 'FL_LABLBLS'.
DBCC results for 'EIImport'.
There are 0 rows in 0 pages for object 'EIImport'.
DBCC results for 'ZZZLO'.
There are 83 rows in 2 pages for object 'ZZZLO'.
DBCC results for 'ZZZVIJ'.
There are 23 rows in 1 pages for object 'ZZZVIJ'.
DBCC results for 'ZZZR2U'.
There are 53 rows in 1 pages for object 'ZZZR2U'.
DBCC results for 'ZZZ25X'.
There are 56 rows in 1 pages for object 'ZZZ25X'.
DBCC results for 'ZZZM5V'.
There are 73 rows in 2 pages for object 'ZZZM5V'.
DBCC results for 'RecallInstructions'.
There are 11 rows in 1 pages for object 'RecallInstructions'.
DBCC results for 'FL_PATUPDTE'.
There are 34 rows in 1 pages for object 'FL_PATUPDTE'.
DBCC results for 'Employer'.
There are 1 rows in 1 pages for object 'Employer'.
DBCC results for 'ZZZNQ'.
There are 53 rows in 1 pages for object 'ZZZNQ'.
DBCC results for 'ZZZNFC'.
There are 96 rows in 2 pages for object 'ZZZNFC'.
DBCC results for 'REFERIDQUAL'.
There are 18 rows in 1 pages for object 'REFERIDQUAL'.
DBCC results for 'FL_REFERRAL'.
There are 27 rows in 1 pages for object 'FL_REFERRAL'.
DBCC results for 'EODSum'.
There are 1 rows in 1 pages for object 'EODSum'.
DBCC results for 'ZZZ2C5'.
There are 73 rows in 2 pages for object 'ZZZ2C5'.
DBCC results for 'ZZZTJ8'.
There are 76 rows in 2 pages for object 'ZZZTJ8'.
DBCC results for 'ZZZZP5'.
There are 59 rows in 1 pages for object 'ZZZZP5'.
DBCC results for 'FL_REGISTRA'.
There are 43 rows in 1 pages for object 'FL_REGISTRA'.
DBCC results for 'ZZZX8X'.
There are 65 rows in 2 pages for object 'ZZZX8X'.
DBCC results for 'EODTotals'.
There are 535 rows in 6 pages for object 'EODTotals'.
DBCC results for 'ZZZ101F'.
There are 59 rows in 1 pages for object 'ZZZ101F'.
DBCC results for 'DemoRecvErrorHdr'.
There are 0 rows in 0 pages for object 'DemoRecvErrorHdr'.
DBCC results for 'ZZZ34K'.
There are 53 rows in 1 pages for object 'ZZZ34K'.
DBCC results for 'ZZZL2J'.
There are 61 rows in 2 pages for object 'ZZZL2J'.
DBCC results for 'ReferralPlan'.
There are 58823 rows in 1667 pages for object 'ReferralPlan'.
DBCC results for 'EOMTable'.
There are 0 rows in 0 pages for object 'EOMTable'.
DBCC results for 'ZZZVOT'.
There are 57 rows in 1 pages for object 'ZZZVOT'.
DBCC results for 'ZZZ3AL'.
There are 86 rows in 2 pages for object 'ZZZ3AL'.
DBCC results for 'ZZZZZE'.
There are 59 rows in 1 pages for object 'ZZZZZE'.
DBCC results for 'FL_1500_90'.
There are 182 rows in 2 pages for object 'FL_1500_90'.
DBCC results for 'ZZZWAX'.
There are 63 rows in 2 pages for object 'ZZZWAX'.
DBCC results for 'ZZZ283'.
There are 53 rows in 1 pages for object 'ZZZ283'.
DBCC results for 'RefrProviderXREF'.
There are 3 rows in 1 pages for object 'RefrProviderXREF'.
DBCC results for 'ZZZZ3F'.
There are 61 rows in 2 pages for object 'ZZZZ3F'.
DBCC results for 'Episode'.
There are 314992 rows in 3270 pages for object 'Episode'.
DBCC results for 'FL_1500LASE'.
There are 175 rows in 2 pages for object 'FL_1500LASE'.
DBCC results for 'ZZZYVJ'.
There are 62 rows in 2 pages for object 'ZZZYVJ'.
DBCC results for 'ZZZJET'.
There are 73 rows in 2 pages for object 'ZZZJET'.
DBCC results for 'ZZZ30K'.
There are 24 rows in 1 pages for object 'ZZZ30K'.
DBCC results for 'ZZZ5T'.
There are 48 rows in 1 pages for object 'ZZZ5T'.
DBCC results for 'ZZZWN1'.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:239039) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:234552), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 2575, Level 16, State 1, Line 1
IAM page (1:239048) is pointed to by the next pointer of IAM page (0:0) object ID 1707074509 index ID 3 but was not detected in the scan.
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 1707074509, index ID 3 due to invalid allocation (IAM) page(s).
Server: Msg 8946, Level 16, State 1, Line 1
Table error: Allocation page (1:239048) has invalid IAM_PAGE page header values. Type is 2. Check type, object ID and page ID on the page.
Server: Msg 8959, Level 16, State 1, Line 1
Table error: IAM page (1:273296) for object ID 1707074509, index ID 3 is linked in the IAM chain for object ID 1437169557, index ID 8 by page (0:0).
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:239049) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:234552), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 2575, Level 16, State 1, Line 1
IAM page (1:239050) is pointed to by the next pointer of IAM page (0:0) object ID 1707074509 index ID 4 but was not detected in the scan.
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 1707074509, index ID 4 due to invalid allocation (IAM) page(s).
Server: Msg 8946, Level 16, State 1, Line 1
Table error: Allocation page (1:239050) has invalid IAM_PAGE page header values. Type is 2. Check type, object ID and page ID on the page.
Server: Msg 8959, Level 16, State 1, Line 1
Table error: IAM page (1:273299) for object ID 1707074509, index ID 4 is linked in the IAM chain for object ID 1437169557, index ID 9 by page (0:0).
Server: Msg 8947, Level 16, State 1, Line 1
Table error: Multiple IAM pages for object ID 1707074509, index ID 5 contain allocations for the same interval. IAM pages (1:273301) and (1:239057).
Server: Msg 8959, Level 16, State 1, Line 1
Table error: IAM page (1:273301) for object ID 1707074509, index ID 5 is linked in the IAM chain for object ID 102212806, index ID 3 by page (0:0).
Server: Msg 8947, Level 16, State 1, Line 1
Table error: Multiple IAM pages for object ID 1707074509, index ID 7 contain allocations for the same interval. IAM pages (1:273315) and (1:239063).
Server: Msg 8959, Level 16, State 3, Line 1
Table error: IAM page (1:273315) for object ID 1707074509, index ID 7 is linked in the IAM chain for object ID 102212806, index ID 5 by page (0:0).
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:248560) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:242640), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 1707074509, index ID 8 due to invalid allocation (IAM) page(s).
Server: Msg 8959, Level 16, State 1, Line 1
Table error: IAM page (1:273317) for object ID 1707074509, index ID 8 is linked in the IAM chain for object ID 102212806, index ID 6 by page (0:0).
Server: Msg 8947, Level 16, State 1, Line 1
Table error: Multiple IAM pages for object ID 1707074509, index ID 9 contain allocations for the same interval. IAM pages (1:273360) and (1:248564).
Server: Msg 8959, Level 16, State 1, Line 1
Table error: IAM page (1:273360) for object ID 1707074509, index ID 9 is linked in the IAM chain for object ID 102212806, index ID 7 by page (0:0).
There are 64 rows in 2 pages for object 'ZZZWN1'.
CHECKDB found 12 allocation errors and 7 consistency errors in table 'ZZZWN1' (object ID 1707074509).
DBCC results for 'ZZZTV'.
There are 53 rows in 1 pages for object 'ZZZTV'.
DBCC results for 'ZZZU7P'.
There are 56 rows in 1 pages for object 'ZZZU7P'.
DBCC results for 'RELATEDCAUSES'.
There are 5 rows in 1 pages for object 'RELATEDCAUSES'.
DBCC results for 'FL_COL_120'.
There are 11 rows in 1 pages for object 'FL_COL_120'.
DBCC results for 'episodebmp'.
There are 1 rows in 1 pages for object 'episodebmp'.
DBCC results for 'ZZZXU'.
There are 54 rows in 1 pages for object 'ZZZXU'.
DBCC results for 'FL_CY_BFWD'.
There are 158 rows in 2 pages for object 'FL_CY_BFWD'.
DBCC results for 'ZZZU1M'.
There are 1440 rows in 8 pages for object 'ZZZU1M'.
DBCC results for 'ZZZU9U'.
There are 63 rows in 2 pages for object 'ZZZU9U'.
DBCC results for 'ZZZ3YH'.
There are 91 rows in 2 pages for object 'ZZZ3YH'.
Server: Msg 8947, Level 16, State 1, Line 1
Table error: Multiple IAM pages for object ID 1778026757, index ID 8 contain allocations for the same interval. IAM pages (1:267264) and (1:233892).
Server: Msg 8959, Level 16, State 1, Line 1
Table error: IAM page (1:267264) for object ID 1778026757, index ID 8 is linked in the IAM chain for object ID 1963075421, index ID 7 by page (0:0).
DBCC results for 'AutoWOQCG'.
There are 9 rows in 1 pages for object 'AutoWOQCG'.
DBCC results for 'ZZZY31'.
There are 61 rows in 1 pages for object 'ZZZY31'.
DBCC results for 'Reminder'.
There are 1 rows in 1 pages for object 'Reminder'.
DBCC results for 'ZZZS1'.
There are 94 rows in 2 pages for object 'ZZZS1'.
DBCC results for 'FL_COL_60'.
There are 11 rows in 1 pages for object 'FL_COL_60'.
DBCC results for 'AutoWOZZJ'.
There are 12 rows in 1 pages for object 'AutoWOZZJ'.
DBCC results for 'FL_PI_OITEM'.
There are 188 rows in 2 pages for object 'FL_PI_OITEM'.
DBCC results for 'FL_CY_OITEM'.
There are 164 rows in 2 pages for object 'FL_CY_OITEM'.
DBCC results for 'ZZZJEV'.
There are 66 rows in 2 pages for object 'ZZZJEV'.
DBCC results for 'ZZZ32N'.
There are 92 rows in 2 pages for object 'ZZZ32N'.
DBCC results for 'ZZZNBL'.
There are 73 rows in 2 pages for object 'ZZZNBL'.
DBCC results for 'ZZZ5V'.
There are 48 rows in 1 pages for object 'ZZZ5V'.
DBCC results for 'ZZZXF2'.
There are 55 rows in 1 pages for object 'ZZZXF2'.
DBCC results for 'ZZZPDQ'.
There are 82 rows in 2 pages for object 'ZZZPDQ'.
DBCC results for 'ZZZME6'.
There are 91 rows in 2 pages for object 'ZZZME6'.
DBCC results for 'ZZZQCH'.
There are 421 rows in 4 pages for object 'ZZZQCH'.
DBCC results for 'ZZZWJ4'.
Server: Msg 8947, Level 16, State 1, Line 1
Table error: Multiple IAM pages for object ID 1778026757, index ID 9 contain allocations for the same interval. IAM pages (1:267266) and (1:233920).
Server: Msg 8959, Level 16, State 1, Line 1
Table error: IAM page (1:267266) for object ID 1778026757, index ID 9 is linked in the IAM chain for object ID 1963075421, index ID 8 by page (0:0).
There are 64 rows in 2 pages for object 'ZZZWJ4'.
CHECKDB found 4 allocation errors and 0 consistency errors in table 'ZZZWJ4' (object ID 1778026757).
DBCC results for 'Remit'.
There are 0 rows in 0 pages for object 'Remit'.
DBCC results for 'FL_COL_90'.
There are 11 rows in 1 pages for object 'FL_COL_90'.
DBCC results for 'FacilityXREF'.
There are 0 rows in 0 pages for object 'FacilityXREF'.
DBCC results for 'ZZZZZK'.
There are 419 rows in 4 pages for object 'ZZZZZK'.
DBCC results for 'FL_UB92'.
There are 216 rows in 2 pages for object 'FL_UB92'.
DBCC results for 'FL_STMT'.
There are 374 rows in 4 pages for object 'FL_STMT'.
DBCC results for 'TRIGTBLLIST'.
There are 1 rows in 1 pages for object 'TRIGTBLLIST'.
DBCC results for 'ZZZY51'.
There are 47 rows in 1 pages for object 'ZZZY51'.
DBCC results for 'RemitLine'.
There are 0 rows in 0 pages for object 'RemitLine'.
DBCC results for 'FinanceClass'.
There are 53 rows in 2 pages for object 'FinanceClass'.
DBCC results for 'ZZZXX'.
There are 54 rows in 1 pages for object 'ZZZXX'.
DBCC results for 'FL_SUPER'.
There are 289 rows in 3 pages for object 'FL_SUPER'.
DBCC results for 'ZZZNBN'.
There are 49 rows in 1 pages for object 'ZZZNBN'.
DBCC results for 'ZZZ5X'.
There are 48 rows in 1 pages for object 'ZZZ5X'.
DBCC results for 'DaySheet_DEV'.
There are 0 rows in 0 pages for object 'DaySheet_DEV'.
DBCC results for 'Reports'.
There are 27 rows in 1 pages for object 'Reports'.
DBCC results for 'ZZZ1'.
There are 1188110 rows in 32672 pages for object 'ZZZ1'.
DBCC results for 'Formgen'.
There are 32 rows in 2 pages for object 'Formgen'.
DBCC results for 'ARErrs_DEV'.
There are 0 rows in 0 pages for object 'ARErrs_DEV'.
DBCC results for 'ZZZVKS'.
There are 63 rows in 2 pages for object 'ZZZVKS'.
DBCC results for 'FL_DMDSTMT'.
There are 110 rows in 2 pages for object 'FL_DMDSTMT'.
DBCC results for 'ZZZ56M'.
There are 87 rows in 2 pages for object 'ZZZ56M'.
DBCC results for 'ANALSERV_DEV'.
There are 0 rows in 0 pages for object 'ANALSERV_DEV'.
DBCC results for 'ZZZXV8'.
There are 61 rows in 1 pages for object 'ZZZXV8'.
DBCC results for 'Resources'.
There are 70 rows in 3 pages for object 'Resources'.
DBCC results for 'ZZZ2'.
There are 7 rows in 1 pages for object 'ZZZ2'.
DBCC results for 'FormLine'.
There are 0 rows in 0 pages for object 'FormLine'.
DBCC results for 'ZZZ2QO'.
There are 90 rows in 2 pages for object 'ZZZ2QO'.
DBCC results for 'ARDetail_DEV'.
There are 0 rows in 0 pages for object 'ARDetail_DEV'.
DBCC results for 'ZZZ1E7'.
There are 52 rows in 1 pages for object 'ZZZ1E7'.
DBCC results for 'FL_DMDINSR'.
There are 181 rows in 2 pages for object 'FL_DMDINSR'.
DBCC results for 'ZZZSBJ'.
There are 50 rows in 1 pages for object 'ZZZSBJ'.
DBCC results for 'ZZZGPX'.
There are 73 rows in 2 pages for object 'ZZZGPX'.
DBCC results for 'ZZZW54'.
There are 63 rows in 2 pages for object 'ZZZW54'.
Server: Msg 8947, Level 16, State 1, Line 1
Table error: Multiple IAM pages for object ID 1906027213, index ID 3 contain allocations for the same interval. IAM pages (1:267268) and (1:233922).
Server: Msg 8959, Level 16, State 1, Line 1
Table error: IAM page (1:267268) for object ID 1906027213, index ID 3 is linked in the IAM chain for object ID 1963075421, index ID 9 by page (0:0).
Server: Msg 8947, Level 16, State 1, Line 1
Table error: Multiple IAM pages for object ID 1906027213, index ID 4 contain allocations for the same interval. IAM pages (1:267608) and (1:233924).
Server: Msg 8959, Level 16, State 1, Line 1
Table error: IAM page (1:267608) for object ID 1906027213, index ID 4 is linked in the IAM chain for object ID 2119599981, index ID 3 by page (0:0).
Server: Msg 8947, Level 16, State 1, Line 1
Table error: Multiple IAM pages for object ID 1906027213, index ID 5 contain allocations for the same interval. IAM pages (1:267610) and (1:233927).
Server: Msg 8959, Level 16, State 1, Line 1
Table error: IAM page (1:267610) for object ID 1906027213, index ID 5 is linked in the IAM chain for object ID 2119599981, index ID 4 by page (0:0).
Server: Msg 8947, Level 16, State 1, Line 1
Table error: Multiple IAM pages for object ID 1906027213, index ID 6 contain allocations for the same interval. IAM pages (1:267615) and (1:235505).
Server: Msg 8959, Level 16, State 1, Line 1
Table error: IAM page (1:267615) for object ID 1906027213, index ID 6 is linked in the IAM chain for object ID 2119599981, index ID 5 by page (0:0).
Server: Msg 8947, Level 16, State 1, Line 1
Table error: Multiple IAM pages for object ID 1906027213, index ID 7 contain allocations for the same interval. IAM pages (1:267817) and (1:235509).
Server: Msg 8959, Level 16, State 1, Line 1
Table error: IAM page (1:267817) for object ID 1906027213, index ID 7 is linked in the IAM chain for object ID 2119599981, index ID 6 by page (0:0).
DBCC results for 'DiagCmp_DEV'.
There are 0 rows in 0 pages for object 'DiagCmp_DEV'.
DBCC results for 'ZZZVAM'.
There are 62 rows in 2 pages for object 'ZZZVAM'.
DBCC results for 'ZZZ1MC'.
There are 77 rows in 2 pages for object 'ZZZ1MC'.
DBCC results for 'ZZZWJ8'.
Server: Msg 8947, Level 16, State 1, Line 1
Table error: Multiple IAM pages for object ID 1906027213, index ID 8 contain allocations for the same interval. IAM pages (1:267819) and (1:235864).
Server: Msg 8959, Level 16, State 1, Line 1
Table error: IAM page (1:267819) for object ID 1906027213, index ID 8 is linked in the IAM chain for object ID 2119599981, index ID 7 by page (0:0).
Server: Msg 8947, Level 16, State 1, Line 1
Table error: Multiple IAM pages for object ID 1906027213, index ID 9 contain allocations for the same interval. IAM pages (1:267822) and (1:235892).
Server: Msg 8959, Level 16, State 1, Line 1
Table error: IAM page (1:267822) for object ID 1906027213, index ID 9 is linked in the IAM chain for object ID 2119599981, index ID 8 by page (0:0).
There are 96 rows in 2 pages for object 'ZZZWJ8'.
CHECKDB found 14 allocation errors and 0 consistency errors in table 'ZZZWJ8' (object ID 1906027213).
DBCC results for 'ResourceType'.
There are 5 rows in 1 pages for object 'ResourceType'.
DBCC results for 'ZZZ3'.
There are 8825 rows in 246 pages for object 'ZZZ3'.
DBCC results for 'FTP_Config'.
There are 0 rows in 0 pages for object 'FTP_Config'.
DBCC results for 'OOPD_DEV'.
There are 0 rows in 0 pages for object 'OOPD_DEV'.
DBCC results for 'FL_CSLIP'.
There are 126 rows in 2 pages for object 'FL_CSLIP'.
DBCC results for 'OpenItems_DEV'.
There are 0 rows in 0 pages for object 'OpenItems_DEV'.
DBCC results for 'ZZZYNS'.
There are 96 rows in 2 pages for object 'ZZZYNS'.
DBCC results for 'ZZZS5K'.
There are 64 rows in 2 pages for object 'ZZZS5K'.
DBCC results for 'ResponsibleParty'.
There are 52670 rows in 4176 pages for object 'ResponsibleParty'.
DBCC results for 'FTP_Errors'.
There are 0 rows in 0 pages for object 'FTP_Errors'.
DBCC results for 'PrntScrn'.
There are 0 rows in 0 pages for object 'PrntScrn'.
DBCC results for 'FL_FACE'.
There are 3 rows in 1 pages for object 'FL_FACE'.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:248565) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:242640), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 1963075421, index ID 3 due to invalid allocation (IAM) page(s).
Server: Msg 8959, Level 16, State 1, Line 1
Table error: IAM page (1:273362) for object ID 1963075421, index ID 3 is linked in the IAM chain for object ID 102212806, index ID 8 by page (0:0).
Server: Msg 8947, Level 16, State 1, Line 1
Table error: Multiple IAM pages for object ID 1963075421, index ID 4 contain allocations for the same interval. IAM pages (1:273366) and (1:264712).
Server: Msg 8959, Level 16, State 1, Line 1
Table error: IAM page (1:273366) for object ID 1963075421, index ID 4 is linked in the IAM chain for object ID 102212806, index ID 9 by page (0:0).
Server: Msg 8947, Level 16, State 1, Line 1
Table error: Multiple IAM pages for object ID 1963075421, index ID 5 contain allocations for the same interval. IAM pages (1:273376) and (1:264714).
Server: Msg 8959, Level 16, State 1, Line 1
Table error: IAM page (1:273376) for object ID 1963075421, index ID 5 is linked in the IAM chain for object ID 642738734, index ID 3 by page (0:0).
Server: Msg 8947, Level 16, State 1, Line 1
Table error: Multiple IAM pages for object ID 1963075421, index ID 6 contain allocations for the same interval. IAM pages (1:273378) and (1:264716).
Server: Msg 8959, Level 16, State 1, Line 1
Table error: IAM page (1:273378) for object ID 1963075421, index ID 6 is linked in the IAM chain for object ID 642738734, index ID 4 by page (0:0).
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:264717) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:258816), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 1963075421, index ID 7 due to invalid allocation (IAM) page(s).
Server: Msg 8959, Level 16, State 1, Line 1
Table error: IAM page (1:273381) for object ID 1963075421, index ID 7 is linked in the IAM chain for object ID 642738734, index ID 5 by page (0:0).
DBCC results for 'ZZZWN9'.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:267265) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:266904), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 1963075421, index ID 8 due to invalid allocation (IAM) page(s).
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:267267) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:266904), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 1963075421, index ID 9 due to invalid allocation (IAM) page(s).
There are 76 rows in 2 pages for object 'ZZZWN9'.
CHECKDB found 12 allocation errors and 4 consistency errors in table 'ZZZWN9' (object ID 1963075421).
DBCC results for 'ProcCmp'.
There are 0 rows in 0 pages for object 'ProcCmp'.
DBCC results for 'ZZZ3YP'.
There are 765 rows in 13 pages for object 'ZZZ3YP'.
DBCC results for 'ZZZZ5R'.
There are 61 rows in 2 pages for object 'ZZZZ5R'.
DBCC results for 'responsiblepartybmp'.
There are 1 rows in 1 pages for object 'responsiblepartybmp'.
DBCC results for 'FTP_Purged'.
There are 0 rows in 0 pages for object 'FTP_Purged'.
DBCC results for 'AccLevels'.
There are 29688 rows in 784 pages for object 'AccLevels'.
DBCC results for 'ZZZU1T'.
There are 57 rows in 1 pages for object 'ZZZU1T'.
DBCC results for 'ZZZYFA'.
There are 68 rows in 2 pages for object 'ZZZYFA'.
DBCC results for 'FL_LOGIN'.
There are 42 rows in 1 pages for object 'FL_LOGIN'.
DBCC results for 'ZZZ3YQ'.
There are 765 rows in 13 pages for object 'ZZZ3YQ'.
DBCC results for 'RevenueCodes'.
There are 8 rows in 1 pages for object 'RevenueCodes'.
DBCC results for 'FTP_TransLog'.
There are 0 rows in 0 pages for object 'FTP_TransLog'.
DBCC results for 'AutoWO3AZ'.
There are 0 rows in 0 pages for object 'AutoWO3AZ'.
DBCC results for 'AccountType'.
There are 1 rows in 1 pages for object 'AccountType'.
DBCC results for 'WOReport_DEV'.
There are 0 rows in 0 pages for object 'WOReport_DEV'.
DBCC results for 'ZZZX59'.
There are 76 rows in 2 pages for object 'ZZZX59'.
DBCC results for 'ZZZDCQ'.
There are 60 rows in 2 pages for object 'ZZZDCQ'.
DBCC results for 'AUTOWO_DEV'.
There are 0 rows in 0 pages for object 'AUTOWO_DEV'.
DBCC results for 'ZZZY5C'.
There are 62 rows in 2 pages for object 'ZZZY5C'.
DBCC results for 'ZZZ3YR'.
There are 765 rows in 13 pages for object 'ZZZ3YR'.
DBCC results for 'RVUDescription'.
There are 0 rows in 0 pages for object 'RVUDescription'.
DBCC results for 'ZZZ4CY'.
There are 93 rows in 2 pages for object 'ZZZ4CY'.
DBCC results for 'HL7MSGQUE'.
There are 0 rows in 0 pages for object 'HL7MSGQUE'.
DBCC results for 'ZZZ3B0'.
There are 563 rows in 5 pages for object 'ZZZ3B0'.
DBCC results for 'ZZZUME'.
There are 1440 rows in 7 pages for object 'ZZZUME'.
DBCC results for 'AdStmt'.
There are 0 rows in 0 pages for object 'AdStmt'.
DBCC results for 'ZZZZZX'.
There are 58 rows in 1 pages for object 'ZZZZZX'.
DBCC results for 'PTAR1_DEV'.
There are 0 rows in 0 pages for object 'PTAR1_DEV'.
DBCC results for 'ZZZYFC'.
There are 68 rows in 2 pages for object 'ZZZYFC'.
DBCC results for 'ZZZWB9'.
There are 59 rows in 1 pages for object 'ZZZWB9'.
DBCC results for 'ZZZ3WW'.
There are 1440 rows in 10 pages for object 'ZZZ3WW'.
DBCC results for 'ZZZXH6'.
There are 64 rows in 2 pages for object 'ZZZXH6'.
DBCC results for 'ZZZUMF'.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:267271) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:266904), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 2119599981, index ID 3 due to invalid allocation (IAM) page(s).
There are 1440 rows in 7 pages for object 'ZZZUMF'.
DBCC results for 'PTAR_DEV'.
There are 0 rows in 0 pages for object 'PTAR_DEV'.
DBCC results for 'ZZZ3YS'.
There are 765 rows in 13 pages for object 'ZZZ3YS'.
DBCC results for 'FL_ENSF6908'.
There are 1589 rows in 16 pages for object 'FL_ENSF6908'.
DBCC results for 'RVUProcedures'.
There are 0 rows in 0 pages for object 'RVUProcedures'.
DBCC results for 'ZZZZ3R'.
There are 61 rows in 2 pages for object 'ZZZZ3R'.
DBCC results for 'ANESTHESIA_CHG'.
There are 0 rows in 0 pages for object 'ANESTHESIA_CHG'.
DBCC results for 'ZZZ3J4'.
There are 52 rows in 1 pages for object 'ZZZ3J4'.
DBCC results for 'ZZZ65'.
There are 48 rows in 1 pages for object 'ZZZ65'.
DBCC results for 'FL_ENSFP69'.
There are 1587 rows in 16 pages for object 'FL_ENSFP69'.
DBCC results for 'RVUXREF'.
There are 0 rows in 0 pages for object 'RVUXREF'.
DBCC results for 'ZZZS3U'.
There are 64 rows in 2 pages for object 'ZZZS3U'.
DBCC results for 'InpatientDays'.
There are 0 rows in 0 pages for object 'InpatientDays'.
DBCC results for 'ANESTHESIA_PRICE'.
There are 0 rows in 0 pages for object 'ANESTHESIA_PRICE'.
DBCC results for 'SmrTrigger'.
There are 0 rows in 0 pages for object 'SmrTrigger'.
DBCC results for 'ZZZ7T3'.
There are 5676 rows in 568 pages for object 'ZZZ7T3'.
DBCC results for 'ZZZWPH'.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:267609) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:266904), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 2119599981, index ID 4 due to invalid allocation (IAM) page(s).
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:267612) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:266904), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 2119599981, index ID 5 due to invalid allocation (IAM) page(s).
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:267816) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:266904), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 2119599981, index ID 6 due to invalid allocation (IAM) page(s).
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:267818) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:266904), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 2119599981, index ID 7 due to invalid allocation (IAM) page(s).
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:267820) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:266904), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 2119599981, index ID 8 due to invalid allocation (IAM) page(s).
Server: Msg 8959, Level 16, State 1, Line 1
Table error: IAM page (1:274537) for object ID 2119599981, index ID 8 is linked in the IAM chain for object ID 1218740786, index ID 6 by page (0:0).
Server: Msg 2575, Level 16, State 1, Line 1
IAM page (1:270112) is pointed to by the next pointer of IAM page (0:0) object ID 2119599981 index ID 9 but was not detected in the scan.
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 2119599981, index ID 9 due to invalid allocation (IAM) page(s).
Server: Msg 8946, Level 16, State 1, Line 1
Table error: Allocation page (1:270112) has invalid IAM_PAGE page header values. Type is 2. Check type, object ID and page ID on the page.
There are 63 rows in 2 pages for object 'ZZZWPH'.
CHECKDB found 7 allocation errors and 9 consistency errors in table 'ZZZWPH' (object ID 2119599981).
DBCC results for 'AppointHistory'.
There are 674375 rows in 8781 pages for object 'AppointHistory'.
CHECKDB found 240 allocation errors and 110 consistency errors in database 'PPMDATATest'.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
February 6, 2010 at 2:03 am
You have irreparable corruption here, there's damage to the system tables and to some allocation pages. There's no way to fix this.
Your options are:
1) restore from your last good backup, use any transaction log backups to roll forward to the point of failure
2) Script all objects (some may fail), export all data (some may fail) and recreate the database.
You should also do some analysis as to the root cause. Typically corruption is an IO subsystem problem, check for errors in the system log, RAID logs, SAN logs, etc.
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
February 6, 2010 at 11:23 am
Thanks for the reply. This DB is using the Simple Recovery method and has been performing full backups each evening even after the corruption. We have all the backups but trying to convince the powers that be to restore from a backup that pre-dates the problem (about 10 days ago) is going to be impossible. They probably add about 5000 records of data to the database each day and do not have a complete paper trail to re-enter.
Currently everything appears to be working correctly which is why we kinda missed our window for restoring since there have been no complaints using the database. Can you point me the right direction on the option #2 you gave?
Thanks!
February 6, 2010 at 11:54 am
What's worse is that you've got tables whose allocations are intermixed so you're running the risk of corrupting your actual data by continuiing to run on this database - you need to create a new one and migrate the data out ASAP.
Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
February 6, 2010 at 12:09 pm
The majority of the tables that show problems in the CheckDB log are temporary tables that have not yet been dropped by the app so they are not important. I am pretty sure I can migrate the data to a clean database this weekend while they are not using it. Can anyone give me a basic overview on the proper way to do this? I have a pretty good idea but am not an expert.
Thanks
February 6, 2010 at 12:38 pm
I'm sure there's an article somewhere (but I don't have any links). Try your favourite search engine.
From enterprise manager, generate the scripts. I don't use EntMan any longer, and I can't recall exactly where the option is.
As for the data, bcp out to a flat file's the easiest however bear in mind that you have allocation page damage in this database. There's a fair chance that some data will export incorrectly (where those intermixed extents are) and some will not export at all. This may not be a quick or trivial process
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
February 6, 2010 at 1:42 pm
Thanks for the additional info. Maybe I am using the wrong search keywords but have not had any luck finding an article on performing this task. Still looking....
February 6, 2010 at 9:44 pm
Still havent found any specific instructions on this. Can anyone give me some guidance and point me in the right direction?
February 7, 2010 at 12:10 am
Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
February 7, 2010 at 4:10 pm
So just wanted to ask real quick; Is this an acceptable way to accomplish the suggestions above?
1. Attached a clean empty copy of the database that already has all the tables(no records), views and stored procedures.
2. Used DTS and set source to corrupt database and destination to new empty database that was attached above.
3. Used first option "Copy tables and views from source database" and copied all user tables.
All user tables copied with no issues (Yay!). I ran a checkdb after this was completed and there are no errors on the new database.
I will soon try this out soon with the app. Hopefully will hear something back from someone here just to confirm what I have done so far.
Thanks again!
February 7, 2010 at 11:50 pm
There's no one single way to coy the DB. I'd say anything that gets the data into a new DB is perfectly acceptable.
Have you had a chance to look at the IO subsystem? Something caused this and a hard service restart alone should not be able to do this kind of damage.
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
February 7, 2010 at 11:55 pm
Thanks for the input. From what I can tell so far, the server appears to be functioning correctly.
I believe what might have happened was an overlap in processes that probably shouldnt be running at the same time. The SQL DB has grown large enough that some of the jobs scheduled to run against it are taking longer than they had before and they just started to overlap with some other backup and disk imaging processes that didn't used to overlap. I have seen this kind of thing happen before. I just need to fix the schedules and I think I am good to go.
February 8, 2010 at 12:07 am
What kind of backup and disk imaging?
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
February 8, 2010 at 12:35 am
Going back through logs I can see that there was a re-index job that ran at the same time as a Livestate Recovery Image of the server drive partition where the SQL DBs are located. Both started at almost the same time. It appears that this first overlap coincides with the first sign of the DB getting corrupted. I have also seen this happen twice in the past with other servers.
February 8, 2010 at 12:56 am
I don't know what LiveState Recovery is, but if it's a file mirroring app, those generally don't play nice with SQL Server and often the mirrored copies aren't usable.
If that were my server, I'd be thinking seriously about removing that from the SQL data/log files and mirroring backups only.
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
Viewing 15 posts - 1 through 14 (of 14 total)
You must be logged in to reply to this topic. Login to reply