I am running SQL Server 2000 with Service Pack 4. We recently had a rather nasty corruption problem over several of our databases on our server. It primarily affected indexes and page allocation tables. As of yet, we have yet to identify the cause of this problem. We ran hardware diagnostics and no problems were returned, and nothing aside from the errors that alerted us to the issue in the first place were found in the event logs or SQL error logs.
DBCC CHECKDB was ran several times (we ran it on all DBs on the server just to be safe, several came up corrupted) and used that to repair the data, but very quickly new corruptions popped up.
However, this is not the extent of my bewilderment. Due to the need to get our server back online, a couple co-workers decided to detatch the databases and reinstall the SQL server, then reattatch the databases and try and repair them. I am not sure why this would have mattered but it seems to have prevented any new corruptions.
Anyway, while I was repairing the problem databases to bring them back online, one of them has been giving me a particular problem. Several indexes were pretty thoroughly trashed, giving over 1000 consistency errors. There were also around 25 or so allocation errors. I rebuilt all of the indexes to remove the consistency errors, however the allocation errors still remain and CHECKDB will not remove them. Here are the results of my most recent checkdb repair attempt:
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:886000) in database ID 37 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:886112) in database ID 37 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:886224) in database ID 37 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:886424) in database ID 37 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:886520) in database ID 37 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:886656) in database ID 37 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:886736) in database ID 37 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:886936) in database ID 37 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:887024) in database ID 37 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:887176) in database ID 37 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:887344) in database ID 37 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:887464) in database ID 37 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:887624) in database ID 37 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:887816) in database ID 37 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:887920) in database ID 37 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:888096) in database ID 37 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:888248) in database ID 37 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:888352) in database ID 37 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:888584) in database ID 37 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Could not repair this error.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:888704) in database ID 37 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:888840) in database ID 37 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:889024) in database ID 37 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:889168) in database ID 37 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:889328) in database ID 37 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
CHECKDB found 24 allocation errors and 0 consistency errors not associated with any single object.
CHECKDB found 24 allocation errors and 0 consistency errors in database 'PRODUCTION_CATEGORIZER'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (PRODUCTION_CATEGORIZER repair_allow_data_loss).
As you can see, it is telling me that the errors cannot be repaired until other errors are corrected first, but there are no other errors! I cannot figure it out. The rest of our databases on the server are now clean, this is the only one that is not working. Does anyone have any suggestions before we restore to the last backup?
I am getting the following after kicking off DBCC CHECKDB 'DATABASE', REPAIR_ALLOW_DATA_LOSS) :
Executed as user: USER. Database 'TEST' consistency errors in sysobjects, sysindexes, syscolumns, or systypes prevent further CHECKDB processing. [SQLSTATE 42000] (Error 7995) Clustered index successfully restored for object 'syscolumns' in database 'TEST'. [SQLSTATE 01000] (Error 2592) DBCC execution completed. If DBCC printed error messages, contact your system administrator. [SQLSTATE 01000] (Error 2528). The step failed.
When I try to delete a job from Enterprise Manager Console I get the following error: Erro 644: Could not find the index entry for RID '163bd10000010000' in index page (1:553), index ID 0 database 'msdb'
Oh and this is on MSDE.
Here is my complete output of DBCC CHECKDB DBCC results for 'msdb'. DBCC results for 'sysobjects'. There are 280 rows in 6 pages for object 'sysobjects'. DBCC results for 'sysindexes'. There are 143 rows in 6 pages for object 'sysindexes'. DBCC results for 'syscolumns'. There are 1567 rows in 26 pages for object 'syscolumns'. DBCC results for 'systypes'. There are 26 rows in 1 pages for object 'systypes'. DBCC results for 'syscomments'. There are 357 rows in 108 pages for object 'syscomments'. DBCC results for 'sysfiles1'. There are 2 rows in 1 pages for object 'sysfiles1'. DBCC results for 'syspermissions'. There are 116 rows in 1 pages for object 'syspermissions'. DBCC results for 'sysusers'. There are 13 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 1635 rows in 8 pages for object 'sysdepends'. DBCC results for 'sysreferences'. There are 12 rows in 1 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 'backupset'. There are 1045 rows in 44 pages for object 'backupset'. DBCC results for 'sysjobschedules'. There are 7 rows in 1 pages for object 'sysjobschedules'. DBCC results for 'syscategories'. There are 19 rows in 1 pages for object 'syscategories'. DBCC results for 'systargetservers'. There are 0 rows in 0 pages for object 'systargetservers'. DBCC results for 'backupfile'. There are 1451 rows in 24 pages for object 'backupfile'. DBCC results for 'systargetservergroups'. There are 0 rows in 0 pages for object 'systargetservergroups'. DBCC results for 'systargetservergroupmembers'. There are 0 rows in 0 pages for object 'systargetservergroupmembers'. DBCC results for 'restorehistory'. There are 1 rows in 1 pages for object 'restorehistory'. DBCC results for 'sysalerts'. There are 9 rows in 1 pages for object 'sysalerts'. DBCC results for 'sysoperators'. There are 0 rows in 0 pages for object 'sysoperators'. DBCC results for 'sysnotifications'. There are 0 rows in 0 pages for object 'sysnotifications'. DBCC results for 'restorefile'. There are 2 rows in 1 pages for object 'restorefile'. DBCC results for 'systaskids'. There are 0 rows in 0 pages for object 'systaskids'. DBCC results for 'syscachedcredentials'. There are 0 rows in 0 pages for object 'syscachedcredentials'. DBCC results for 'restorefilegroup'. There are 1 rows in 1 pages for object 'restorefilegroup'. DBCC results for 'logmarkhistory'. There are 0 rows in 0 pages for object 'logmarkhistory'. DBCC results for 'sysdtscategories'. There are 3 rows in 1 pages for object 'sysdtscategories'. DBCC results for 'sysdtspackages'. There are 0 rows in 0 pages for object 'sysdtspackages'. DBCC results for 'sysdtspackagelog'. There are 0 rows in 0 pages for object 'sysdtspackagelog'. DBCC results for 'sysdtssteplog'. Server: Msg 8935, Level 16, State 1, Line 1 Table error: Object ID 2073058421, index ID 1. The previous link (1:343) on page (1:371) does not match the previous page (1:382) that the parent (1:300), slot 32 expects for this page. Server: Msg 8978, Level 16, State 1, Line 1 Table error: Object ID 2073058421, index ID 1. Page (1:371) is missing a reference from previous page (1:343). Possible chain linkage problem. There are 0 rows in 0 pages for object 'sysdtssteplog'. DBCC results for 'sysdtstasklog'. There are 0 rows in 0 pages for object 'sysdtstasklog'. DBCC results for 'sysdbmaintplans'. There are 4 rows in 1 pages for object 'sysdbmaintplans'. DBCC results for 'sysdbmaintplan_jobs'. There are 4 rows in 1 pages for object 'sysdbmaintplan_jobs'. DBCC results for 'sysdbmaintplan_databases'. There are 12 rows in 1 pages for object 'sysdbmaintplan_databases'. DBCC results for 'sysdbmaintplan_history'. There are 724 rows in 23 pages for object 'sysdbmaintplan_history'. DBCC results for 'log_shipping_primaries'. There are 0 rows in 0 pages for object 'log_shipping_primaries'. DBCC results for 'log_shipping_secondaries'. There are 0 rows in 0 pages for object 'log_shipping_secondaries'. DBCC results for 'mswebtasks'. There are 0 rows in 0 pages for object 'mswebtasks'. DBCC results for 'sqlagent_info'. There are 0 rows in 0 pages for object 'sqlagent_info'. DBCC results for 'sysdownloadlist'. There are 0 rows in 0 pages for object 'sysdownloadlist'. DBCC results for 'backupmediaset'. There are 1045 rows in 11 pages for object 'backupmediaset'. DBCC results for 'sysjobhistory'. Server: Msg 8935, Level 16, State 1, Line 1 Table error: Object ID 2073058421, index ID 1. The previous link (1:382) on page (1:564) does not match the previous page (1:371) that the parent (1:300), slot 33 expects for this page. There are 626 rows in 208 pages for object 'sysjobhistory'. CHECKDB found 0 allocation errors and 3 consistency errors in table 'sysjobhistory' (object ID 2073058421). DBCC results for 'sysjobs'. There are 7 rows in 1 pages for object 'sysjobs'. DBCC results for 'backupmediafamily'. There are 1045 rows in 20 pages for object 'backupmediafamily'. DBCC results for 'sysjobservers'. There are 7 rows in 1 pages for object 'sysjobservers'. DBCC results for 'sysjobsteps'. There are 9 rows in 1 pages for object 'sysjobsteps'. CHECKDB found 0 allocation errors and 3 consistency errors in database 'msdb'. repair_rebuild is the minimum repair level for the errors found by DBCC CHECKDB (msdb ). DBCC execution completed. If DBCC printed error messages, contact your system administrator.
Ran DBCC CHECKDB on my database and it's returning the following:
There are 460 rows in 13 pages for object 'KPW'. Server: Msg 8928, Level 16, State 1, Line 1 Object ID 1977058079, index ID 0: Page (1:1868079) could not be processed. See other errors for details. Server: Msg 8944, Level 16, State 1, Line 1 Table error: Object ID 1977058079, index ID 0, page (1:1868079), row 76. Test (!(hdr->r_tagA & (VERSION_MASK | RECTAG_RESV_A | RECTAG_RESV_B))) failed. Values are 173 and 193. Server: Msg 8944, Level 16, State 1, Line 1 Table error: Object ID 1977058079, index ID 0, page (1:1868079), row 76. Test (ColumnOffsets <= (nextRec - pRec)) failed. Values are 16374 and 33. Server: Msg 8964, Level 16, State 1, Line 1 Table error: Object ID 1977058079. The text, ntext, or image node at page (1:1867931), slot 8, text ID 205274873856 is not referenced. Server: Msg 8964, Level 16, State 1, Line 1 Table error: Object ID 1977058079. The text, ntext, or image node at page (1:1867932), slot 0, text ID 205275004928 is not referenced. Server: Msg 8964, Level 16, State 1, Line 1 Table error: Object ID 1977058079. The text, ntext, or image node at page (1:1867932), slot 2, text ID 205275136000 is not referenced. Server: Msg 8964, Level 16, State 1, Line 1
I have a database that was handed to me which is getting the following errors:
DBCC CHECKDB ('DBName') returns: Server: Msg 8939, Level 16, State 106, Line 1 Table error: Object ID 1, index ID 0, page (1:37). Test (m_freeCnt == freeCnt) failed. Values are 680 and 788. Server: Msg 8966, Level 16, State 1, Line 1 Could not read and latch page (1:37) with latch type SH. sysobjects failed.
DBCC PAGE (DBName, 1, 37, 1) returns: Server: Msg 8939, Level 16, State 20, Line 1 Table error: Object ID 99, index ID 0, page (1:2). Test (m_slots[0].GetOffset () == PAGEHEADSIZE) failed. Values are 662 and 96. Server: Msg 8939, Level 16, State 1, Line 1 Table error: Object ID 99, index ID 0, page (1:2). Test (Align(m_slots[-1].GetOffset ()) == Align(m_slots[0].GetOffset () + sizeof(GAMHEADER) + sizeof(DataRecHdr))) failed. Values are 190 and 756. DBCC execution completed. If DBCC printed error messages, contact your system administrator.
DBCC PAGE (DBName, 1, 2, 1) returns: Server: Msg 8939, Level 16, State 20, Line 1 Table error: Object ID 99, index ID 0, page (1:2). Test (m_slots[0].GetOffset () == PAGEHEADSIZE) failed. Values are 662 and 96. Server: Msg 8939, Level 16, State 1, Line 1 Table error: Object ID 99, index ID 0, page (1:2). Test (Align(m_slots[-1].GetOffset ()) == Align(m_slots[0].GetOffset () + sizeof(GAMHEADER) + sizeof(DataRecHdr))) failed. Values are 190 and 756. Server: Msg 3624, Level 20, State 1, Line 1
And finally, DBCC CHECKTABLE (sysobjects) WITH NO_INFOMSGS, ALL_ERRORMSGS gives me: Server: Msg 8939, Level 16, State 106, Line 1 Table error: Object ID 1, index ID 0, page (1:37). Test (m_freeCnt == freeCnt) failed. Values are 680 and 788. Server: Msg 8966, Level 16, State 1, Line 1 Could not read and latch page (1:37) with latch type SH. sysobjects failed.
I've looked at the MDF with a hex editor and there's definitely data in there. I have the DB attached and in single user/emergency mode, but DBCC isn't having much luck. Help?
I actually ran this on a reporting copy of my DB (restored once a week). I would guess the errors are present in the main copy as well. I fear running the check during production hours as it takes 2.5 hours and the system (4 processor) is under a lot of load for almost the entire day and much of the night.
It looks like the repair with data loss is my only choice but I would definitely prefer to know which rows are messed up. I'm also wary of running the repair as it's probably going to take well over an hour on the huge sessions table. I don't know how it got in this corrupted state. I inherited a DB of this size (50GB) that's been known to be very sensitive to any admin or index fiddling due to the high load. After I get this repaired I feel I should run the CHECKDB in a maintenance plan but I'm not sure if this will cause slowdowns in itself if it runs for 2.5 hours. The DB backup takes over 2 hours leaving almost no spare time in the off peak time.
Any advice/suggestions? Thanks.
DBCC results for 'dbloc'.
DBCC results for 'sessions'. Server: Msg 8928, Level 16, State 1, Line 1 Object ID 462624691, index ID 0: Page (1:9517861) could not be processed. See other errors for details. Server: Msg 8928, Level 16, State 1, Line 1 Object ID 462624691, index ID 0: Page (1:9659261) could not be processed. See other errors for details. Server: Msg 8928, Level 16, State 1, Line 1 Object ID 462624691, index ID 7: Page (1:5825743) could not be processed. See other errors for details. Server: Msg 8928, Level 16, State 1, Line 1 Object ID 462624691, index ID 7: Page (1:5890660) could not be processed. See other errors for details. Server: Msg 8928, Level 16, State 1, Line 1 Object ID 462624691, index ID 7: Page (1:5931145) could not be processed. See other errors for details. Server: Msg 8928, Level 16, State 1, Line 1 Object ID 462624691, index ID 7: Page (1:5950021) could not be processed. See other errors for details. Server: Msg 8928, Level 16, State 1, Line 1 Object ID 462624691, index ID 7: Page (1:5978420) could not be processed. See other errors for details. Server: Msg 8928, Level 16, State 1, Line 1 Object ID 462624691, index ID 7: Page (1:5988261) could not be processed. See other errors for details. Server: Msg 8928, Level 16, State 1, Line 1 Object ID 462624691, index ID 7: Page (1:6046306) could not be processed. See other errors for details. Server: Msg 2511, Level 16, State 1, Line 1 Table error: Object ID 510624862, Index ID 0. Keys out of order on page (1:11853027), slots 109 and 110. Server: Msg 2511, Level 16, State 1, Line 1 Table error: Object ID 510624862, Index ID 0. Keys out of order on page (1:11853027), slots 112 and 113. Server: Msg 2511, Level 16, State 1, Line 1 Table error: Object ID 510624862, Index ID 0. Keys out of order on page (1:11853027), slots 113 and 114. Server: Msg 2511, Level 16, State 1, Line 1 Table error: Object ID 510624862, Index ID 0. Keys out of order on page (1:11853027), slots 114 and 115. Server: Msg 2511, Level 16, State 1, Line 1 Table error: Object ID 510624862, Index ID 0. Keys out of order on page (1:11853027), slots 117 and 118. Server: Msg 2511, Level 16, State 1, Line 1 Table error: Object ID 510624862, Index ID 0. Keys out of order on page (1:11853027), slots 118 and 119. Server: Msg 2511, Level 16, State 1, Line 1 Table error: Object ID 510624862, Index ID 0. Keys out of order on page (1:11853027), slots 121 and 122. Server: Msg 2511, Level 16, State 1, Line 1 Table error: Object ID 510624862, Index ID 0. Keys out of order on page (1:11853027), slots 122 and 123. Server: Msg 2511, Level 16, State 1, Line 1 Table error: Object ID 510624862, Index ID 0. Keys out of order on page (1:11853027), slots 124 and 125. Server: Msg 8928, Level 16, State 1, Line 1 Object ID 510624862, index ID 0: Page (1:11858027) could not be processed. See other errors for details. Server: Msg 8939, Level 16, State 1, Line 1 Table error: Object ID 510624862, index ID 0, page (1:11858027). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1. Server: Msg 8928, Level 16, State 1, Line 1 Object ID 510624862, index ID 0: Page (1:11865547) could not be processed. See other errors for details. Server: Msg 8939, Level 16, State 1, Line 1 Table error: Object ID 510624862, index ID 0, page (1:11865547). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1. Server: Msg 8928, Level 16, State 1, Line 1 Object ID 510624862, index ID 2: Page (1:11889147) could not be processed. See other errors for details. DBCC results for 'sessions'. There are 153364096 rows in 3102681 pages for object 'sessions'. CHECKDB found 0 allocation errors and 9 consistency errors in table 'sessions' (object ID 462624691). DBCC results for 'map'. Server: Msg 8939, Level 16, State 98, Line 1 Table error: Object ID 510624862, index ID 2, page (1:11889147). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1. Server: Msg 2511, Level 16, State 1, Line 1 Table error: Object ID 510624862, Index ID 3. Keys out of order on page (1:11931268), slots 206 and 207. Server: Msg 2511, Level 16, State 1, Line 1 Table error: Object ID 510624862, Index ID 3. Keys out of order on page (1:11931268), slots 209 and 210. Server: Msg 2511, Level 16, State 1, Line 1 Table error: Object ID 510624862, Index ID 3. Keys out of order on page (1:11931268), slots 210 and 211. Server: Msg 2511, Level 16, State 1, Line 1 Table error: Object ID 510624862, Index ID 3. Keys out of order on page (1:11931268), slots 230 and 231. Server: Msg 8928, Level 16, State 1, Line 1 Object ID 510624862, index ID 11: Page (1:11988308) could not be processed. See other errors for details. Server: Msg 8944, Level 16, State 1, Line 1 Table error: Object ID 510624862, index ID 11, page (1:11988308), row 194. Test (ColumnOffsets <= (nextRec - pRec)) failed. Values are 7251 and 18. Server: Msg 8928, Level 16, State 1, Line 1 Object ID 510624862, index ID 11: Page (1:12003992) could not be processed. See other errors for details. Server: Msg 8939, Level 16, State 1, Line 1 Table error: Object ID 510624862, index ID 11, page (1:12003992). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1. There are 15576829 rows in 65455 pages for object 'map'. CHECKDB found 0 allocation errors and 23 consistency errors in table 'map' (object ID 510624862). Server: Msg 8928, Level 16, State 1, Line 1 Object ID 1790629422, index ID 16: Page (1:11471717) could not be processed. See other errors for details. Server: Msg 8944, Level 16, State 1, Line 1 Table error: Object ID 1790629422, index ID 16, page (1:11471717), row 88. Test (ColumnOffsets <= (nextRec - pRec)) failed. Values are 3500 and 28. Server: Msg 8928, Level 16, State 1, Line 1 Object ID 1790629422, index ID 16: Page (1:11474112) could not be processed. See other errors for details. Server: Msg 8944, Level 16, State 1, Line 1 Table error: Object ID 1790629422, index ID 16, page (1:11474112), row 108. Test (ColumnOffsets <= (nextRec - pRec)) failed. Values are 745 and 20. DBCC results for 'links'. There are 9919777 rows in 124284 pages for object 'links'. CHECKDB found 0 allocation errors and 4 consistency errors in table 'links' (object ID 1790629422). CHECKDB found 0 allocation errors and 36 consistency errors in database 'dbloc'. repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (dbloc ). DBCC execution completed. If DBCC printed error messages, contact your system administrator.
I've seen a lot of approaches to this, but I wanted to check here first before trying anything. Unfortunately, I just arrived and looking over the database, realized their backups have been failing for quite sometime. The application using the database is running fine so far, but backing it up freezes. I run DBCC CHECKDB (MyDB) WITH NO_INFOMSGS, ALL_ERRORMSGS and get:
Msg 8909, Level 16, State 1, Line 1 Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 844424953200640 (type Unknown), page ID (1:26483) contains an incorrect page ID in its page header. The PageId in the page header = (0:0). Msg 8909, Level 16, State 1, Line 1 Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 2533274801405952 (type Unknown), page ID (1:24589) contains an incorrect page ID in its page header. The PageId in the page header = (0:-1694496760). Msg 8909, Level 16, State 1, Line 1 Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 2533274811367424 (type Unknown), page ID (1:24301) contains an incorrect page ID in its page header. The PageId in the page header = (0:-1694496747). Msg 8909, Level 16, State 1, Line 1 Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 2533279088508928 (type Unknown), page ID (1:24334) contains an incorrect page ID in its page header. The PageId in the page header = (0:0). CHECKDB found 0 allocation errors and 4 consistency errors not associated with any single object. Msg 8928, Level 16, State 1, Line 1 Object ID 1093578934, index ID 1, partition ID 353143765729280, alloc unit ID 71668789018624 (type In-row data): Page (1:22417) could not be processed. See other errors for details. Msg 8978, Level 16, State 1, Line 1 Table error: Object ID 1093578934, index ID 1, partition ID 353143765729280, alloc unit ID 71668789018624 (type In-row data). Page (1:521649) is missing a reference from previous page (1:22417). Possible chain linkage problem. Msg 8939, Level 16, State 98, Line 1 Table error: Object ID 1093578934, index ID 1, partition ID 353143765729280, alloc unit ID 353143765729280 (type In-row data), page (1:22417). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29362185 and -1. Msg 8976, Level 16, State 1, Line 1 Table error: Object ID 1093578934, index ID 1, partition ID 353143765729280, alloc unit ID 353143765729280 (type In-row data). Page (1:22417) was not seen in the scan although its parent (1:479) and previous (1:715544) refer to it. Check any previous errors. CHECKDB found 0 allocation errors and 4 consistency errors in table 'WebGroups' (object ID 1093578934). Msg 8929, Level 16, State 1, Line 1 Object ID 1993058136, index ID 1, partition ID 412092034711552, alloc unit ID 130617058000896 (type In-row data): Errors found in off-row data with ID 1606680576 owned by data record identified by RID = (1:1620895:7) Msg 8929, Level 16, State 1, Line 1 Object ID 1993058136, index ID 1, partition ID 412092034711552, alloc unit ID 130617058000896 (type In-row data): Errors found in off-row data with ID 1606811648 owned by data record identified by RID = (1:1620895:8) Msg 8929, Level 16, State 1, Line 1 Object ID 1993058136, index ID 1, partition ID 412092034711552, alloc unit ID 130617058000896 (type In-row data): Errors found in off-row data with ID 1607073792 owned by data record identified by RID = (1:1620895:10) Msg 8929, Level 16, State 1, Line 1 Object ID 1993058136, index ID 1, partition ID 412092034711552, alloc unit ID 130617058000896 (type In-row data): Errors found in off-row data with ID 1607204864 owned by data record identified by RID = (1:1620895:11) Msg 8929, Level 16, State 1, Line 1 Object ID 1993058136, index ID 1, partition ID 412092034711552, alloc unit ID 130617058000896 (type In-row data): Errors found in off-row data with ID 1608908800 owned by data record identified by RID = (1:1620896:10) Msg 8928, Level 16, State 1, Line 1 Object ID 1993058136, index ID 1, partition ID 412092034711552, alloc unit ID 71906736119218176 (type LOB data): Page (1:24301) could not be processed. See other errors for details. Msg 8965, Level 16, State 1, Line 1 Table error: Object ID 1993058136, index ID 1, partition ID 412092034711552, alloc unit ID 71906736119218176 (type LOB data). The off-row data node at page (1:24301), slot 0, text ID 1606680576 is referenced by page (1:24298), slot 0, but was not seen in the scan. Msg 8928, Level 16, State 1, Line 1 Object ID 1993058136, index ID 1, partition ID 412092034711552, alloc unit ID 71906736119218176 (type LOB data): Page (1:24334) could not be processed. See other errors for details. Msg 8965, Level 16, State 1, Line 1 Table error: Object ID 1993058136, index ID 1, partition ID 412092034711552, alloc unit ID 71906736119218176 (type LOB data). The off-row data node at page (1:24334), slot 0, text ID 1606811648 is referenced by page (1:24331), slot 0, but was not seen in the scan. Msg 8928, Level 16, State 1, Line 1 Object ID 1993058136, index ID 1, partition ID 412092034711552, alloc unit ID 71906736119218176 (type LOB data): Page (1:24462) could not be processed. See other errors for details. Msg 8939, Level 16, State 98, Line 1 Table error: Object ID 1993058136, index ID 1, partition ID 412092034711552, alloc unit ID 71906736119218176 (type LOB data), page (1:24462). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29362185 and -1. Msg 8965, Level 16, State 1, Line 1 Table error: Object ID 1993058136, index ID 1, partition ID 412092034711552, alloc unit ID 71906736119218176 (type LOB data). The off-row data node at page (1:24462), slot 0, text ID 1607073792 is referenced by page (1:24429), slot 0, but was not seen in the scan. Msg 8928, Level 16, State 1, Line 1 Object ID 1993058136, index ID 1, partition ID 412092034711552, alloc unit ID 71906736119218176 (type LOB data): Page (1:24589) could not be processed. See other errors for details. Msg 8965, Level 16, State 1, Line 1 Table error: Object ID 1993058136, index ID 1, partition ID 412092034711552, alloc unit ID 71906736119218176 (type LOB data). The off-row data node at page (1:24589), slot 0, text ID 1607204864 is referenced by page (1:24591), slot 0, but was not seen in the scan. Msg 8928, Level 16, State 1, Line 1 Object ID 1993058136, index ID 1, partition ID 412092034711552, alloc unit ID 71906736119218176 (type LOB data): Page (1:26483) could not be processed. See other errors for details. Msg 8965, Level 16, State 1, Line 1 Table error: Object ID 1993058136, index ID 1, partition ID 412092034711552, alloc unit ID 71906736119218176 (type LOB data). The off-row data node at page (1:26483), slot 0, text ID 1608908800 is referenced by page (1:26470), slot 0, but was not seen in the scan. CHECKDB found 0 allocation errors and 16 consistency errors in table 'Docs' (object ID 1993058136). CHECKDB found 0 allocation errors and 24 consistency errors in database 'MyDB'. repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (MyDB).
SQL 2005 I ran the following: DBCC CHECKDB (€˜DATABASENAME€™) Errors are produced DBCC CHECKDB ('DATABASENAME')
DBCC results for 'AllDocStreams'. Msg 8914, Level 16, State 1, Line 1 Incorrect PFS free space information for page (1:26839) in object ID 181575685, index ID 1, partition ID 293374720802816, alloc unit ID 71788018805309440 (type LOB data). Expected value 0_PCT_FULL, actual value 100_PCT_FULL.
I wanted to view the PAGE by doing
dbcc traceon(3604)
DBCC PAGE (1,26839,1) (But keeps telling me there is no page)
So i tried DBCC IND('TEST','AllDocStreams',1) Found the PagePID of 26839 then i found IAMFID so i tried
DBCC PAGE (1,1577,3) still no page
I was trying to find the PCT FULL on the page? but can't find the page its talking about.
I can do a REPAIR_WITH_DATA_LOSS but i wanted to figure out what it is actually repairing and what the message is really telling me
My Maintenance plan is failing because of this error.
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID 569873197. The text, ntext, or image node at page (1:13952), slot 42, text ID 49266360320 is not referenced.
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 12 consistency errors in table 'Orientation_ChkList' (object ID 569873197). [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 12 consistency errors in database.
How can I check which rows in this table is corrupted? I have three image fields in this table. This is happening since long time and restore from backup won't work here.
Recently, I've started to get DBCC Checkdb errors against a few databases - seems to be since applying sp3a.
The error (2537) affects certain tables that contain SQL_Variant fields. I just completed an exercise to run DBCC CHECKDB ('dbname', REPAIR_ALLOW_DATA_LOSS) against a copy of the offending table - then comparing the original table and the repaired table to isolate the rows that throw up the consistency errors. What I found was that all the rows trapped by DBCC CHECKDB for error 2537 contain real numbers in the SQL_Variant field. All other rows with text or integer contents in the SQL_Variant field do not throw up errors.
I tried a MS hotfix for error 2537 but it didn't fix the problem. Any ideas?
I'm using WSUS2 to deploy software updates at my company, WSUS2 uses WMSDE (SQL Server Desktop Engine 2000 SP4) to store its database.
WSUS2 suddenly stopped working, I identified problems at the Database Log reading like this:
quote: 2006-05-11 12:17:52.64 spid54 Error: 7105, Severity: 22, State: 6 2006-05-11 12:17:52.64 spid54 Page (1:79), slot 29 for text, ntext, or image node does not exist.. [...]
So I ran a CHECKDB via osql on the commandline and got errors which should be repaired with a minimum of REPAIR_ALLOW_DATA_LOSS.
So I ran the following command on the corruprt Datebase 'SUSDB' after putting the DB into single user mode:
1> DBCC CHECKDB ('SUSDB',REPAIR_ALLOW_DATA_LOSS) WITH NO_INFOMSGS 2> GO
And I got the fowllowing output (condensed):
quote: Msg 8929, Level 16, State 1, Server FILESWSUS, Line 1 Object ID 2: Errors found in text ID 131203072 owned by data record identified by RID = (1:24:2) id = 1 and indid = 3. Msg 8929, Level 16, State 1, Server FILESWSUS, Line 1 Object ID 2: Errors found in text ID 131268608 owned by data record identified by RID = (1:24:6) id = 3 and indid = 2. Msg 8929, Level 16, State 1, Server FILESWSUS, Line 1 Object ID 2: Errors found in text ID 131334144 owned by data record identified by RID = (1:24:7) id = 4 and indid = 1. Msg 8929, Level 16, State 1, Server FILESWSUS, Line 1 Object ID 2: Errors found in text ID 131399680 owned by data record identified by RID = (1:24:8) id = 4 and indid = 2. Msg 8929, Level 16, State 1, Server FILESWSUS, Line 1 Object ID 2: Errors found in text ID 131465216 owned by data record identified by RID = (1:24:13) id = 10 and indid = 2. Msg 8929, Level 16, State 1, Server FILESWSUS, Line 1 Object ID 2: Errors found in text ID 131530752 owned by data record identified by RID = (1:24:15) id = 11 and indid = 1.
[... MANY MANY MORE OF THOSE FAILURES WITH DIFFERENT IDs ...]
Object ID 2: Errors found in text ID 459538432 owned by data record identified by RID = (1:104:27) id = 1858105660 and indid = 3. The repair level on the DBCC statement caused this repair to be bypassed. The system cannot self repair this error. The system cannot self repair this error. The system cannot self repair this error. The system cannot self repair this error. The system cannot self repair this error. The system cannot self repair this error. The system cannot self repair this error. The system cannot self repair this error. The system cannot self repair this error. The system cannot self repair this error. The system cannot self repair this error. The system cannot self repair this error. The system cannot self repair this error. The system cannot self repair this error. The system cannot self repair this error. The system cannot self repair this error. The system cannot self repair this error. The system cannot self repair this error. The system cannot self repair this error. The system cannot self repair this error. The system cannot self repair this error. The system cannot self repair this error. The system cannot self repair this error. The system cannot self repair this error. The system cannot self repair this error. The system cannot self repair this error. The system cannot self repair this error. The system cannot self repair this error. Msg 8929, Level 16, State 1, Server FILESWSUS, Line 1 Object ID 2: Errors found in text ID 459735040 owned by data record identified by RID = (1:104:28) id = 1858105660 and indid = 4. Msg 8929, Level 16, State 1, Server FILESWSUS, Line 1 Object ID 2: Errors found in text ID 4462411776 owned by data record identified by RID = (1:107:5) id = 373576369 and indid = 6. Msg 8929, Level 16, State 1, Server FILESWSUS, Line 1 Object ID 2: Errors found in text ID 327745536 owned by data record identified by RID = (1:107:10) id = 487672785 and indid = 1.
[... MANY MANY MORE OF THOSE FAILURES WITH DIFFERENT IDs ...]
Msg 8964, Level 16, State 1, Server FILESWSUS, Line 1 Table error: Object ID 2. The text, ntext, or image node at page (1:64), slot 4, text ID 459735040 is not referenced. Msg 8964, Level 16, State 1, Server FILESWSUS, Line 1 Table error: Object ID 2. The text, ntext, or image node at page (1:68), slot 7, text ID 197459968 is not referenced. Msg 8964, Level 16, State 1, Server FILESWSUS, Line 1 Table error: Object ID 2. The text, ntext, or image node at page (1:69), slot 0, text ID 197263360 is not referenced. Msg 8964, Level 16, State 1, Server FILESWSUS, Line 1 Table error: Object ID 2. The text, ntext, or image node at page (1:70), slot 0, text ID 4462411776 is not referenced. Msg 8964, Level 16, State 1, Server FILESWSUS, Line 1 Table error: Object ID 2. The text, ntext, or image node at page (1:71), slot 5, text ID 197197824 is not referenced. Msg 8928, Level 16, State 1, Server FILESWSUS, Line 1 Object ID 2, index ID 255: Page (1:79) could not be processed. See other errors for details. Msg 8965, Level 16, State 1, Server FILESWSUS, Line 1 Table error: Object ID 2. The text, ntext, or image node at page (1:79), slot 0, text ID 327745536 is referenced by page (1:107), slot 10, but was not seen in the scan.
[... MANY MANY MORE OF THOSE FAILURES WITH DIFFERENT IDs ...]
The repair level on the DBCC statement caused this repair to be bypassed. The repair level on the DBCC statement caused this repair to be bypassed. The repair level on the DBCC statement caused this repair to be bypassed. The repair level on the DBCC statement caused this repair to be bypassed. The repair level on the DBCC statement caused this repair to be bypassed. CHECKDB found 0 allocation errors and 97 consistency errors in table 'sysindexes' (object ID 2). CHECKDB found 0 allocation errors and 97 consistency errors in database 'SUSDB'.
None of the errors are repaired, what can I do to repair the Database?
I have a database that is being restored to another instance of SQL server 2000 sp4 by attatching the mdf and ldf files. I then run EXEC sp_change_users_login to sync the users. When I try to run some delete commands on the new restored database I get 'Fatal error 8908'
I then run a DBCC CHECKDB on the database and told to run it again with REPAIR_ALLOW_DATA_LOSS
I have noticed that when I create a new databse and restore a .bak over this the delete commands work.
Am I correct in thinking that I can get rid of the corruption on the original database by creating a new database then restoring a valid .bak backup on this new database.
Hi all, Here is my DBCC CHECKDB output. I keep REPAIRing the problem and it keeps coming back. I would love to get rid of the objectID in question, but do not know how, or if that would fix the problem. This is running on a MSDE 2000 SP3a. It is also only the "Events" Table that seems to be affected.
Server: Msg 2511, Level 16, State 1, Line 1 Table error: Object ID 562101043, Index ID 2. Keys out of order on page (1:67702), slots 174 and 175. Server: Msg 2511, Level 16, State 1, Line 1 Table error: Object ID 562101043, Index ID 2. Keys out of order on page (1:67875), slots 246 and 247. DBCC results for 'AccessControl'. DBCC results for 'sysobjects'. There are 1130 rows in 20 pages for object 'sysobjects'. DBCC results for 'sysindexes'. There are 1397 rows in 55 pages for object 'sysindexes'. DBCC results for 'syscolumns'. There are 3047 rows in 47 pages for object 'syscolumns'. DBCC results for 'systypes'. There are 26 rows in 1 pages for object 'systypes'. DBCC results for 'syscomments'. There are 572 rows in 52 pages for object 'syscomments'. DBCC results for 'sysfiles1'. There are 2 rows in 1 pages for object 'sysfiles1'. DBCC results for 'syspermissions'. There are 51 rows in 1 pages for object 'syspermissions'. DBCC results for 'sysusers'. There are 13 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 1017 rows in 6 pages for object 'sysdepends'. DBCC results for 'sysreferences'. There are 13 rows in 1 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 'GLOBAL_IO_LINKAGE'. There are 0 rows in 0 pages for object 'GLOBAL_IO_LINKAGE'. DBCC results for 'PANEL_USER_GROUP'. There are 0 rows in 0 pages for object 'PANEL_USER_GROUP'. DBCC results for 'PRECACGRP'. There are 0 rows in 0 pages for object 'PRECACGRP'. DBCC results for 'GLOBAL_IO_OUTPUT_ACTION'. There are 0 rows in 0 pages for object 'GLOBAL_IO_OUTPUT_ACTION'. DBCC results for 'PANEL_USER'. There are 0 rows in 0 pages for object 'PANEL_USER'. DBCC results for 'USERS_ACCESSLEVEL_LINK'. There are 0 rows in 0 pages for object 'USERS_ACCESSLEVEL_LINK'. DBCC results for 'PRECGRPLINK'. There are 0 rows in 0 pages for object 'PRECGRPLINK'. DBCC results for 'EMP_SEGMENT_LINK'. There are 0 rows in 0 pages for object 'EMP_SEGMENT_LINK'. DBCC results for 'KNOWHO_SERVER'. There are 0 rows in 0 pages for object 'KNOWHO_SERVER'. DBCC results for 'ASSET_MMOBJS'. There are 0 rows in 0 pages for object 'ASSET_MMOBJS'. DBCC results for 'GOS_MESSAGE'. There are 1 rows in 1 pages for object 'GOS_MESSAGE'. DBCC results for 'QUEUED_EVENTS'. There are 0 rows in 1 pages for object 'QUEUED_EVENTS'. DBCC results for 'DDTBL'. There are 23 rows in 1 pages for object 'DDTBL'. DBCC results for 'ACCESSLVL_ASSIGNABLE_SEGMENT'. There are 0 rows in 0 pages for object 'ACCESSLVL_ASSIGNABLE_SEGMENT'. DBCC results for 'PERSON_DATA_SOURCE'. There are 6 rows in 1 pages for object 'PERSON_DATA_SOURCE'. DBCC results for 'IE_BADGE_ACC'. There are 0 rows in 0 pages for object 'IE_BADGE_ACC'. DBCC results for 'DEPT'. There are 1 rows in 1 pages for object 'DEPT'. DBCC results for 'USER_PERM_REPORT_GROUP_MEMBER'. There are 0 rows in 0 pages for object 'USER_PERM_REPORT_GROUP_MEMBER'. DBCC results for 'DEVICE_GROUP'. There are 3 rows in 1 pages for object 'DEVICE_GROUP'. DBCC results for 'BADGE_AREA_LOCATION_REPL'. There are 0 rows in 0 pages for object 'BADGE_AREA_LOCATION_REPL'. DBCC results for 'ACCTRANS_RESTORED'. There are 2478 rows in 47 pages for object 'ACCTRANS_RESTORED'. DBCC results for 'LNL_CERTIFICATE'. There are 0 rows in 0 pages for object 'LNL_CERTIFICATE'. DBCC results for 'TRANSMITTER'. There are 0 rows in 0 pages for object 'TRANSMITTER'. DBCC results for 'DEVICE_GROUP_LINK'. There are 186 rows in 1 pages for object 'DEVICE_GROUP_LINK'. DBCC results for 'ALARM_ACK_ACTION'. There are 0 rows in 0 pages for object 'ALARM_ACK_ACTION'. DBCC results for 'ACCTRANS_REPL'. There are 0 rows in 0 pages for object 'ACCTRANS_REPL'. DBCC results for 'CERTIFICATE_AUTHORITY'. There are 0 rows in 0 pages for object 'CERTIFICATE_AUTHORITY'. DBCC results for 'ACCTRANS'. There are 22500 rows in 435 pages for object 'ACCTRANS'. DBCC results for 'DIALUP'. There are 0 rows in 0 pages for object 'DIALUP'. DBCC results for 'ICONTYPE_COMMAND'. There are 3 rows in 1 pages for object 'ICONTYPE_COMMAND'. DBCC results for 'CARDHOLDER_ACCOUNT'. There are 0 rows in 0 pages for object 'CARDHOLDER_ACCOUNT'. DBCC results for 'ACCESSLVL_EXTENDED'. There are 0 rows in 0 pages for object 'ACCESSLVL_EXTENDED'. DBCC results for 'RDR_CARDFORMATS'. There are 0 rows in 0 pages for object 'RDR_CARDFORMATS'. DBCC results for 'DIVISION'. There are 1 rows in 1 pages for object 'DIVISION'. DBCC results for 'MOBILE_VERIFY_GATE'. There are 0 rows in 0 pages for object 'MOBILE_VERIFY_GATE'. DBCC results for 'DOWNLOADDB'. There are 0 rows in 0 pages for object 'DOWNLOADDB'. DBCC results for 'ACCGPLINK'. There are 0 rows in 0 pages for object 'ACCGPLINK'. DBCC results for 'ARCHIVE_SERVER'. There are 1 rows in 1 pages for object 'ARCHIVE_SERVER'. DBCC results for 'RDTZCTLIST'. There are 0 rows in 0 pages for object 'RDTZCTLIST'. DBCC results for 'ELEVATORHW'. There are 0 rows in 0 pages for object 'ELEVATORHW'. DBCC results for 'ACCLVLINK'. There are 0 rows in 0 pages for object 'ACCLVLINK'. DBCC results for 'ARCHIVE_SERVER_LOCATION'. There are 1 rows in 1 pages for object 'ARCHIVE_SERVER_LOCATION'. DBCC results for 'BDG2TRN'. There are 0 rows in 0 pages for object 'BDG2TRN'. DBCC results for 'READER'. There are 0 rows in 0 pages for object 'READER'. DBCC results for 'MOBILE_VERIFY_GATE_RDR_LINK'. There are 0 rows in 0 pages for object 'MOBILE_VERIFY_GATE_RDR_LINK'. DBCC results for 'TRANSMITTER_INPUT'. There are 0 rows in 0 pages for object 'TRANSMITTER_INPUT'. DBCC results for 'EVENT'. There are 1249 rows in 11 pages for object 'EVENT'. DBCC results for 'USER_OPTIONS'. There are 5 rows in 1 pages for object 'USER_OPTIONS'. DBCC results for 'NV_FIRMWARE_DOWNLOAD_ACTION'. There are 0 rows in 0 pages for object 'NV_FIRMWARE_DOWNLOAD_ACTION'. DBCC results for 'READER_ENTRANCE'. There are 0 rows in 0 pages for object 'READER_ENTRANCE'. DBCC results for 'TRANSMITTER_LINK'. There are 0 rows in 0 pages for object 'TRANSMITTER_LINK'. DBCC results for 'EA_DIAGNOSTIC_CFG'. There are 0 rows in 0 pages for object 'EA_DIAGNOSTIC_CFG'. DBCC results for 'NV_FIRMWARE_DOWNLOAD_DEVICE'. There are 0 rows in 0 pages for object 'NV_FIRMWARE_DOWNLOAD_DEVICE'. DBCC results for 'READER_ENTRANCE_LOITERING'. There are 0 rows in 0 pages for object 'READER_ENTRANCE_LOITERING'. DBCC results for 'RELAYOUTPT'. There are 0 rows in 0 pages for object 'RELAYOUTPT'. DBCC results for 'EVENT_GIOFUNCLISTLINK'. There are 0 rows in 0 pages for object 'EVENT_GIOFUNCLISTLINK'. DBCC results for 'ACISLOG'. There are 8 rows in 1 pages for object 'ACISLOG'. DBCC results for 'VISIT_TYPE'. There are 1 rows in 1 pages for object 'VISIT_TYPE'. DBCC results for 'BADGE_EXPECTED_PASSAGE'. There are 0 rows in 0 pages for object 'BADGE_EXPECTED_PASSAGE'. DBCC results for 'ALARM'. There are 1249 rows in 18 pages for object 'ALARM'. DBCC results for 'EA_RESULTCOL_CFG'. There are 1 rows in 1 pages for object 'EA_RESULTCOL_CFG'. DBCC results for 'REPORTCFG'. There are 126 rows in 5 pages for object 'REPORTCFG'. DBCC results for 'EVENTGRP'. There are 1 rows in 1 pages for object 'EVENTGRP'. DBCC results for 'VISIT_RESTORED'. There are 0 rows in 0 pages for object 'VISIT_RESTORED'. DBCC results for 'SNMP_MIB_DATA'. There are 0 rows in 0 pages for object 'SNMP_MIB_DATA'. DBCC results for 'ALARMINPUT'. There are 48 rows in 2 pages for object 'ALARMINPUT'. DBCC results for 'EA_RESULTCOL_DDFLD_LINK'. There are 5 rows in 1 pages for object 'EA_RESULTCOL_DDFLD_LINK'. DBCC results for 'RESISTOR'. There are 0 rows in 0 pages for object 'RESISTOR'. DBCC results for 'EVENTGRPLNK'. There are 316 rows in 2 pages for object 'EVENTGRPLNK'. DBCC results for 'GOS_EA_ALERT'. There are 0 rows in 0 pages for object 'GOS_EA_ALERT'. DBCC results for 'EVENTS_VIDEO_RESTORED'. There are 0 rows in 0 pages for object 'EVENTS_VIDEO_RESTORED'. DBCC results for 'SNMP_AGENT'. There are 0 rows in 0 pages for object 'SNMP_AGENT'. DBCC results for 'ALARMMASKGROUP'. There are 0 rows in 0 pages for object 'ALARMMASKGROUP'. DBCC results for 'USER_LNL_DB_LINK'. There are 0 rows in 0 pages for object 'USER_LNL_DB_LINK'. DBCC results for 'SAVEDEVENTS'. There are 2611 rows in 41 pages for object 'SAVEDEVENTS'. DBCC results for 'EVENT_PARAM'. There are 340 rows in 4 pages for object 'EVENT_PARAM'. DBCC results for 'ACTION_REPLICATOR'. There are 0 rows in 0 pages for object 'ACTION_REPLICATOR'. DBCC results for 'OPC_SOURCE'. There are 0 rows in 0 pages for object 'OPC_SOURCE'. DBCC results for 'ALARMMASKGROUPLINK'. There are 0 rows in 0 pages for object 'ALARMMASKGROUPLINK'. DBCC results for 'AUTO_TOUR_ACTION'. There are 0 rows in 0 pages for object 'AUTO_TOUR_ACTION'. DBCC results for 'VERSIT'. There are 29 rows in 1 pages for object 'VERSIT'. DBCC results for 'EVENT_TO_EVENT_PARAM_LINK'. There are 936 rows in 3 pages for object 'EVENT_TO_EVENT_PARAM_LINK'. DBCC results for 'USER_PTZ_PRIORITY'. There are 4 rows in 1 pages for object 'USER_PTZ_PRIORITY'. DBCC results for 'GSC'. There are 46 rows in 1 pages for object 'GSC'. DBCC results for 'ALARMPANEL'. There are 4 rows in 1 pages for object 'ALARMPANEL'. DBCC results for 'AUTO_TOUR_MONSTATION_LINK'. There are 0 rows in 0 pages for object 'AUTO_TOUR_MONSTATION_LINK'. DBCC results for 'ASSET_CLASS'. There are 0 rows in 0 pages for object 'ASSET_CLASS'. DBCC results for 'EVENTS'. There are 3692794 rows in 53947 pages for object 'EVENTS'. CHECKDB found 0 allocation errors and 2 consistency errors in table 'EVENTS' (object ID 562101043). DBCC results for 'LNL_DIRECTORY'. There are 1 rows in 1 pages for object 'LNL_DIRECTORY'. DBCC results for 'SWEVENT_GUARANTEE'. There are 0 rows in 0 pages for object 'SWEVENT_GUARANTEE'. DBCC results for 'DMV'. There are 29 rows in 1 pages for object 'DMV'. DBCC results for 'ASSET_GROUP_ASSET_CLASS_LINK'. There are 0 rows in 0 pages for object 'ASSET_GROUP_ASSET_CLASS_LINK'. DBCC results for 'PTZ_PRIORITY_LOCK'. There are 0 rows in 0 pages for object 'PTZ_PRIORITY_LOCK'. DBCC results for 'ALARMPANELLINKS'. There are 0 rows in 0 pages for object 'ALARMPANELLINKS'. DBCC results for 'IVCHANNELCONFIG'. There are 0 rows in 0 pages for object 'IVCHANNELCONFIG'. DBCC results for 'EVENTS_GUARANTEE'. There are 0 rows in 0 pages for object 'EVENTS_GUARANTEE'. DBCC results for 'CAC'. There are 41 rows in 1 pages for object 'CAC'. DBCC results for 'ASSET_ASSET_CLASS_LINK'. There are 0 rows in 0 pages for object 'ASSET_ASSET_CLASS_LINK'. DBCC results for 'SEGMENT_GROUP_MEMBER'. There are 0 rows in 0 pages for object 'SEGMENT_GROUP_MEMBER'. DBCC results for 'ALARMSACK'. There are 30309 rows in 239 pages for object 'ALARMSACK'. DBCC results for 'EVENTS_GUARANTEE_DONE'. There are 0 rows in 0 pages for object 'EVENTS_GUARANTEE_DONE'. DBCC results for 'CISCO_AIC_DEVICE'. There are 0 rows in 0 pages for object 'CISCO_AIC_DEVICE'. DBCC results for 'CAMERA_PRESET_TOUR'. There are 0 rows in 0 pages for object 'CAMERA_PRESET_TOUR'. DBCC results for 'CHASSIS'. There are 3 rows in 1 pages for object 'CHASSIS'. DBCC results for 'STAZONLINK'. There are 4 rows in 1 pages for object 'STAZONLINK'. DBCC results for 'EVENTS_LASTSERIALNUM'. There are 44 rows in 1 pages for object 'EVENTS_LASTSERIALNUM'. DBCC results for 'ALARMSACK_RESTORED'. There are 0 rows in 0 pages for object 'ALARMSACK_RESTORED'. DBCC results for 'USER_ACCOUNT'. There are 23 rows in 4 pages for object 'USER_ACCOUNT'. DBCC results for 'TWO_MAN_TYPE'. There are 3 rows in 1 pages for object 'TWO_MAN_TYPE'. DBCC results for 'PURGE_HISTORYLOGS_ACTION'. There are 0 rows in 0 pages for object 'PURGE_HISTORYLOGS_ACTION'. DBCC results for 'CAMERA_PRESET_COMMAND'. There are 0 rows in 0 pages for object 'CAMERA_PRESET_COMMAND'. DBCC results for 'LOCKSET_MEMORY'. There are 1 rows in 1 pages for object 'LOCKSET_MEMORY'. DBCC results for 'SYSTEMCARDS'. There are 1 rows in 1 pages for object 'SYSTEMCARDS'. DBCC results for 'EVENTS_RESTORED'. There are 0 rows in 0 pages for object 'EVENTS_RESTORED'. DBCC results for 'ARCHIVE_CONFIG'. There are 6 rows in 1 pages for object 'ARCHIVE_CONFIG'. DBCC results for 'SINGLE_DEVICE_ACTION'. There are 0 rows in 0 pages for object 'SINGLE_DEVICE_ACTION'. DBCC results for 'SWEVENT_GUARANTEE_DONE'. There are 0 rows in 0 pages for object 'SWEVENT_GUARANTEE_DONE'. DBCC results for 'PROCESSORTYPE'. There are 3 rows in 1 pages for object 'PROCESSORTYPE'. DBCC results for 'HWTRANS_REPL'. There are 0 rows in 0 pages for object 'HWTRANS_REPL'. DBCC results for 'IVPROCESSORS_IN_USE'. There are 1 rows in 1 pages for object 'IVPROCESSORS_IN_USE'. DBCC results for 'ARCHIVE_DETAIL'. There are 29 rows in 1 pages for object 'ARCHIVE_DETAIL'. DBCC results for 'DEVICE_GROUP_ACTION'. There are 0 rows in 0 pages for object 'DEVICE_GROUP_ACTION'. DBCC results for 'EVENTCRITERIA'. There are 0 rows in 0 pages for object 'EVENTCRITERIA'. DBCC results for 'WORLDTZ_BAK'. There are 62 rows in 2 pages for object 'WORLDTZ_BAK'. DBCC results for 'AREAAPB'. There are 1 rows in 1 pages for object 'AREAAPB'. DBCC results for 'MUSTER_INITIATION_ACTION'. There are 0 rows in 0 pages for object 'MUSTER_INITIATION_ACTION'. DBCC results for 'TEXT_BASED_EVENTS'. There are 0 rows in 0 pages for object 'TEXT_BASED_EVENTS'. DBCC results for 'EVENTS_REPL'. There are 0 rows in 0 pages for object 'EVENTS_REPL'. DBCC results for 'SUPPORTED_BIOMETRIC_TYPES'. There are 0 rows in 0 pages for object 'SUPPORTED_BIOMETRIC_TYPES'. DBCC results for 'TEXTOBJ'. There are 1249 rows in 13 pages for object 'TEXTOBJ'. DBCC results for 'EVENTYPE'. There are 27 rows in 1 pages for object 'EVENTYPE'. DBCC results for 'ASSET_TYPE'. There are 1 rows in 1 pages for object 'ASSET_TYPE'. DBCC results for 'AREATZCTLIST'. There are 0 rows in 0 pages for object 'AREATZCTLIST'. DBCC results for 'SWEVENT'. There are 0 rows in 0 pages for object 'SWEVENT'. DBCC results for 'TIMEZONE'. There are 5 rows in 1 pages for object 'TIMEZONE'. DBCC results for 'EVTALMLINK'. There are 1249 rows in 6 pages for object 'EVTALMLINK'. DBCC results for 'ASSET_SUBTYPE'. There are 1 rows in 1 pages for object 'ASSET_SUBTYPE'. DBCC results for 'POS_REGISTER'. There are 0 rows in 0 pages for object 'POS_REGISTER'. DBCC results for 'MU_ALARM_MASK_GROUP_ACTION'. There are 0 rows in 0 pages for object 'MU_ALARM_MASK_GROUP_ACTION'. DBCC results for 'TITLE'. There are 1 rows in 1 pages for object 'TITLE'. DBCC results for 'ASSET_LASTLOCATION'. There are 0 rows in 0 pages for object 'ASSET_LASTLOCATION'. DBCC results for 'REPL_SCHEDULE'. There are 0 rows in 0 pages for object 'REPL_SCHEDULE'. DBCC results for 'TRANSLOG'. There are 0 rows in 0 pages for object 'TRANSLOG'. DBCC results for 'VISITOR_SIGNOUT_ACTION'. There are 0 rows in 0 pages for object 'VISITOR_SIGNOUT_ACTION'. DBCC results for 'ARCHIVE_PURGE_DATABASE_ACTION'. There are 1 rows in 1 pages for object 'ARCHIVE_PURGE_DATABASE_ACTION'. DBCC results for 'TZINTERVAL'. There are 6 rows in 1 pages for object 'TZINTERVAL'. DBCC results for 'FAILEDRPC'. There are 0 rows in 1 pages for object 'FAILEDRPC'. DBCC results for 'ASSET_GROUP'. There are 1 rows in 1 pages for object 'ASSET_GROUP'. DBCC results for 'CONTINUOUS_VIDEO'. There are 0 rows in 0 pages for object 'CONTINUOUS_VIDEO'. DBCC results for 'DEACTIVATE_BADGE_ACTION'. There are 0 rows in 0 pages for object 'DEACTIVATE_BADGE_ACTION'. DBCC results for 'INTERCOM_CALL_ACTION'. There are 0 rows in 0 pages for object 'INTERCOM_CALL_ACTION'. DBCC results for 'UDFEMP'. There are 1 rows in 1 pages for object 'UDFEMP'. DBCC results for 'EMP'. There are 1 rows in 1 pages for object 'EMP'. DBCC results for 'FLOORLINK'. There are 128 rows in 1 pages for object 'FLOORLINK'. DBCC results for 'CHANGE_PASSWORD_ACTION'. There are 0 rows in 0 pages for object 'CHANGE_PASSWORD_ACTION'. DBCC results for 'ISC_DATABASE_DOWNLOAD_ACTION'. There are 0 rows in 0 pages for object 'ISC_DATABASE_DOWNLOAD_ACTION'. DBCC results for 'LNL_RELATION'. There are 11 rows in 1 pages for object 'LNL_RELATION'. DBCC results for 'UDFOBJS'. There are 202 rows in 7 pages for object 'UDFOBJS'. DBCC results for 'NET_DOMAIN'. There are 0 rows in 0 pages for object 'NET_DOMAIN'. DBCC results for 'FLOORLIST'. There are 3 rows in 1 pages for object 'FLOORLIST'. DBCC results for 'CHANGE_PASSWORD_DEVICE'. There are 0 rows in 0 pages for object 'CHANGE_PASSWORD_DEVICE'. DBCC results for 'CARD_PRINTER_TYPE'. There are 8 rows in 1 pages for object 'CARD_PRINTER_TYPE'. DBCC results for 'ISC_DATABASE_DOWNLOAD_PANEL'. There are 0 rows in 0 pages for object 'ISC_DATABASE_DOWNLOAD_PANEL'. DBCC results for 'IVAPPLICATION'. There are 0 rows in 0 pages for object 'IVAPPLICATION'. DBCC results for 'NET_EMP_SID'. There are 0 rows in 0 pages for object 'NET_EMP_SID'. DBCC results for 'GIOFUNCLIST'. There are 0 rows in 0 pages for object 'GIOFUNCLIST'. DBCC results for 'TEXT_LIBRARY'. There are 0 rows in 0 pages for object 'TEXT_LIBRARY'. DBCC results for 'SEGMENT'. There are 1 rows in 1 pages for object 'SEGMENT'. DBCC results for 'ISC_FIRMWARE_DOWNLOAD_ACTION'. There are 0 rows in 0 pages for object 'ISC_FIRMWARE_DOWNLOAD_ACTION'. DBCC results for 'ENCODER'. There are 0 rows in 0 pages for object 'ENCODER'. DBCC results for 'GIOFUNCLISTLINK'. There are 0 rows in 0 pages for object 'GIOFUNCLISTLINK'. DBCC results for 'IVAPPLICATIONTYPE'. There are 0 rows in 0 pages for object 'IVAPPLICATIONTYPE'. DBCC results for 'CCTVDEVICE_FAILOVER'. There are 0 rows in 0 pages for object 'CCTVDEVICE_FAILOVER'. DBCC results for 'HOLIDAYS'. There are 1 rows in 1 pages for object 'HOLIDAYS'. DBCC results for 'ISC_FIRMWARE_DOWNLOAD_PANEL'. There are 0 rows in 0 pages for object 'ISC_FIRMWARE_DOWNLOAD_PANEL'. DBCC results for 'IVAPP_CRITERIA_LOCK'. There are 0 rows in 0 pages for object 'IVAPP_CRITERIA_LOCK'. DBCC results for 'UDFPAGES'. There are 2 rows in 1 pages for object 'UDFPAGES'. DBCC results for 'USER_PERM_DEVICE_GROUP_LINK'. There are 0 rows in 0 pages for object 'USER_PERM_DEVICE_GROUP_LINK'. DBCC results for 'PTZ_SERVER_TYPE'. There are 5 rows in 1 pages for object 'PTZ_SERVER_TYPE'. DBCC results for 'HOLIDAY_TYPE'. There are 8 rows in 1 pages for object 'HOLIDAY_TYPE'. DBCC results for 'RESET_GLOBAL_APB_ACTION'. There are 0 rows in 0 pages for object 'RESET_GLOBAL_APB_ACTION'. DBCC results for 'PANEL_SELECTIVE_DOWNLOAD'. There are 0 rows in 0 pages for object 'PANEL_SELECTIVE_DOWNLOAD'. DBCC results for 'USER_PERM'. There are 12 rows in 1 pages for object 'USER_PERM'. DBCC results for 'ACCTRANS_OPERATION'. There are 60 rows in 1 pages for object 'ACCTRANS_OPERATION'. DBCC results for 'BADGETYPE_CARDFORMAT_LINK'. There are 0 rows in 0 pages for object 'BADGETYPE_CARDFORMAT_LINK'. DBCC results for 'AIMS'. There are 0 rows in 0 pages for object 'AIMS'. DBCC results for 'HOLIDAY_LNK'. There are 1 rows in 1 pages for object 'HOLIDAY_LNK'. DBCC results for 'RESET_GLOBAL_APB_SEGMENT'. There are 0 rows in 0 pages for object 'RESET_GLOBAL_APB_SEGMENT'. DBCC results for 'ACCTRANS_OBJECT'. There are 128 rows in 1 pages for object 'ACCTRANS_OBJECT'. DBCC results for 'USER_PERM_UDF'. There are 2 rows in 1 pages for object 'USER_PERM_UDF'. DBCC results for 'IDS_ALLOCATED'. There are 0 rows in 0 pages for object 'IDS_ALLOCATED'. DBCC results for 'REPORT_PRINT_ACTION'. There are 0 rows in 0 pages for object 'REPORT_PRINT_ACTION'. DBCC results for 'BADGE_ENCODING'. There are 0 rows in 0 pages for object 'BADGE_ENCODING'. DBCC results for 'LASTLOCATION_REPL'. There are 0 rows in 0 pages for object 'LASTLOCATION_REPL'. DBCC results for 'USER_PERM_UDF_FIELDS'. There are 161 rows in 2 pages for object 'USER_PERM_UDF_FIELDS'. DBCC results for 'IE_ACISFLDS'. There are 0 rows in 0 pages for object 'IE_ACISFLDS'. DBCC results for 'CONTINUOUS_VIDEO_RESTORED'. There are 0 rows in 0 pages for object 'CONTINUOUS_VIDEO_RESTORED'. DBCC results for 'DESERVERHOST'. There are 0 rows in 0 pages for object 'DESERVERHOST'. DBCC results for 'USER_PERM_UDF_PAGES'. There are 2 rows in 1 pages for object 'USER_PERM_UDF_PAGES'. DBCC results for 'IE_ACISINI'. There are 0 rows in 0 pages for object 'IE_ACISINI'. DBCC results for 'LASTLOCATION_REPL_STAGE'. There are 0 rows in 0 pages for object 'LASTLOCATION_REPL_STAGE'. DBCC results for 'CCTVDEVICE_IO'. There are 0 rows in 0 pages for object 'CCTVDEVICE_IO'. DBCC results for 'IE_RELATION'. There are 0 rows in 0 pages for object 'IE_RELATION'. DBCC results for 'ASSET'. There are 0 rows in 0 pages for object 'ASSET'. DBCC results for 'DE_ACTION'. There are 0 rows in 0 pages for object 'DE_ACTION'. DBCC results for 'ACCOUNT'. There are 0 rows in 0 pages for object 'ACCOUNT'. DBCC results for 'USER_PERM_REPORT_GROUP'. There are 0 rows in 0 pages for object 'USER_PERM_REPORT_GROUP'. DBCC results for 'INTERCOM_STATION'. There are 0 rows in 0 pages for object 'INTERCOM_STATION'. DBCC results for 'LNL_DEFAULT'. There are 0 rows in 0 pages for object 'LNL_DEFAULT'. DBCC results for 'DE_CONDITION'. There are 0 rows in 0 pages for object 'DE_CONDITION'. DBCC results for 'USERS'. There are 24 rows in 1 pages for object 'USERS'. DBCC results for 'DE_CONFIGURATION'. There are 0 rows in 0 pages for object 'DE_CONFIGURATION'. DBCC results for 'ACCOUNT_ZONE'. There are 0 rows in 0 pages for object 'ACCOUNT_ZONE'. DBCC results for 'LASTLOCATION'. There are 0 rows in 0 pages for object 'LASTLOCATION'. DBCC results for 'ASSET_ASSIGNMENT'. There are 0 rows in 0 pages for object 'ASSET_ASSIGNMENT'. DBCC results for 'ACCOUNT_AREA'. There are 0 rows in 0 pages for object 'ACCOUNT_AREA'. DBCC results for 'LOGON_AUTH'. There are 1 rows in 1 pages for object 'LOGON_AUTH'. DBCC results for 'USER_SEGMENT_LINK'. There are 0 rows in 0 pages for object 'USER_SEGMENT_LINK'. DBCC results for 'MONITOR_CCTV_DEVICE_LINK'. There are 0 rows in 0 pages for object 'MONITOR_CCTV_DEVICE_LINK'. DBCC results for 'LAYGRAPH'. There are 6 rows in 1 pages for object 'LAYGRAPH'. DBCC results for 'AUDIO'. There are 0 rows in 0 pages for object 'AUDIO'. DBCC results for 'DE_EXCHANGE_MAP'. There are 0 rows in 0 pages for object 'DE_EXCHANGE_MAP'. DBCC results for 'EVENT_CODE_TEMPLATE'. There are 18 rows in 1 pages for object 'EVENT_CODE_TEMPLATE'. DBCC results for 'VISITOR_UDF'. There are 0 rows in 0 pages for object 'VISITOR_UDF'. DBCC results for 'DE_EXPRESSION'. There are 0 rows in 0 pages for object 'DE_EXPRESSION'. DBCC results for 'LAYOUTS'. There are 1 rows in 1 pages for object 'LAYOUTS'. DBCC results for 'BADGE'. There are 1 rows in 1 pages for object 'BADGE'. DBCC results for 'DE_IO_DEFINITION'. There are 0 rows in 0 pages for object 'DE_IO_DEFINITION'. DBCC results for 'BADGE_USES_LEFT_PER_PANEL'. There are 0 rows in 0 pages for object 'BADGE_USES_LEFT_PER_PANEL'. DBCC results for 'EVENT_CODE_MAP'. There are 1284 rows in 6 pages for object 'EVENT_CODE_MAP'. DBCC results for 'VISIT'. There are 0 rows in 0 pages for object 'VISIT'. DBCC results for 'DE_IO_SET_DEFINITION'. There are 0 rows in 0 pages for object 'DE_IO_SET_DEFINITION'. DBCC results for 'LINEPRINTER_COLUMN'. There are 0 rows in 0 pages for object 'LINEPRINTER_COLUMN'. DBCC results for 'DE_IO_SET_LINK'. There are 0 rows in 0 pages for object 'DE_IO_SET_LINK'. DBCC results for 'TOUR'. There are 0 rows in 0 pages for object 'TOUR'. DBCC results for 'WORLDTZ'. There are 85 rows in 2 pages for object 'WORLDTZ'. DBCC results for 'DE_IO_SET_UNIT'. There are 0 rows in 0 pages for object 'DE_IO_SET_UNIT'. DBCC results for 'LINEPRINTER_LAYOUT'. There are 0 rows in 0 pages for object 'LINEPRINTER_LAYOUT'. DBCC results for 'TOUR_CHECKPOINT'. There are 0 rows in 0 pages for object 'TOUR_CHECKPOINT'. DBCC results for 'WRKLAYLNK'. There are 0 rows in 0 pages for object 'WRKLAYLNK'. DBCC results for 'DE_LOOKUP_PARAM'. There are 0 rows in 0 pages for object 'DE_LOOKUP_PARAM'. DBCC results for 'LINKAGESERVERHOST'. There are 1 rows in 1 pages for object 'LINKAGESERVERHOST'. DBCC results for 'LINXPROCCMDS'. There are 0 rows in 0 pages for object 'LINXPROCCMDS'. DBCC results for 'TOUR_CHECKPOINT_ACTION'. There are 0 rows in 0 pages for object 'TOUR_CHECKPOINT_ACTION'. DBCC results for 'DE_OPERATION'. There are 0 rows in 0 pages for object 'DE_OPERATION'. DBCC results for 'LNR_SOURCE_CAPS'. There are 0 rows in 0 pages for object 'LNR_SOURCE_CAPS'. DBCC results for 'GOS_DEVICE'. There are 1 rows in 1 pages for object 'GOS_DEVICE'. DBCC results for 'LNLCONFIG'. There are 18 rows in 2 pages for object 'LNLCONFIG'. DBCC results for 'BADGELINK'. There are 0 rows in 0 pages for object 'BADGELINK'. DBCC results for 'TOUR_CHECKPOINT_MESSAGE'. There are 0 rows in 0 pages for object 'TOUR_CHECKPOINT_MESSAGE'. DBCC results for 'FIRE_DEVICES'. There are 0 rows in 0 pages for object 'FIRE_DEVICES'. DBCC results for 'LNL_DB'. There are 0 rows in 0 pages for object 'LNL_DB'. DBCC results for 'BADGETYP'. There are 4 rows in 1 pages for object 'BADGETYP'. DBCC results for 'TOUR_MONSTATION'. There are 0 rows in 0 pages for object 'TOUR_MONSTATION'. DBCC results for 'FIRE_DEVICE_INPUTS_OUTPUTS'. There are 0 rows in 0 pages for object 'FIRE_DEVICE_INPUTS_OUTPUTS'. DBCC results for 'GOS_ALARMMESSAGELINK'. There are 1 rows in 1 pages for object 'GOS_ALARMMESSAGELINK'. DBCC results for 'BADGEID_RANGE'. There are 0 rows in 0 pages for object 'BADGEID_RANGE'. DBCC results for 'TOUR_LIST'. There are 0 rows in 0 pages for object 'TOUR_LIST'. DBCC results for 'RESET_USE_LIMIT_ACTION'. There are 0 rows in 0 pages for object 'RESET_USE_LIMIT_ACTION'. DBCC results for 'GOS_RECIPIENT'. There are 0 rows in 1 pages for object 'GOS_RECIPIENT'. DBCC results for 'TOUR_LIST_LINK'. There are 0 rows in 0 pages for object 'TOUR_LIST_LINK'. DBCC results for 'dtproperties'. There are 0 rows in 0 pages for object 'dtproperties'. DBCC results for 'LOCATION'. There are 1 rows in 1 pages for object 'LOCATION'. DBCC results for 'RESET_USE_LIMIT_PANEL'. There are 0 rows in 0 pages for object 'RESET_USE_LIMIT_PANEL'. DBCC results for 'GOS_RECIPIENTADDRESS'. There are 0 rows in 1 pages for object 'GOS_RECIPIENTADDRESS'. DBCC results for 'LPRIORITY'. There are 4 rows in 1 pages for object 'LPRIORITY'. DBCC results for 'TOUR_EMP_TOUR_LIST_LINK'. There are 0 rows in 0 pages for object 'TOUR_EMP_TOUR_LIST_LINK'. DBCC results for 'EOL_TABLE'. There are 4 rows in 1 pages for object 'EOL_TABLE'. DBCC results for 'GOS_MESSAGERECIPIENT'. There are 0 rows in 1 pages for object 'GOS_MESSAGERECIPIENT'. DBCC results for 'MAP'. There are 1 rows in 1 pages for object 'MAP'. DBCC results for 'TOUR_LOG'. There are 0 rows in 0 pages for object 'TOUR_LOG'. DBCC results for 'EOL_TABLE_LINK'. There are 0 rows in 0 pages for object 'EOL_TABLE_LINK'. DBCC results for 'ALARMVIDEOCONFIG'. There are 4 rows in 1 pages for object 'ALARMVIDEOCONFIG'. DBCC results for 'MAPICON'. There are 134 rows in 2 pages for object 'MAPICON'. DBCC results for 'BADGETYPE_SEGMENT_LINK'. There are 0 rows in 0 pages for object 'BADGETYPE_SEGMENT_LINK'. DBCC results for 'INTRUSION_DEVICE'. There are 0 rows in 0 pages for object 'INTRUSION_DEVICE'. DBCC results for 'MAPICONGRP'. There are 43 rows in 1 pages for object 'MAPICONGRP'. DBCC results for 'ACTION_TYPE'. There are 38 rows in 1 pages for object 'ACTION_TYPE'. DBCC results for 'CCTV_DEVICE_LINK'. There are 94 rows in 3 pages for object 'CCTV_DEVICE_LINK'. DBCC results for 'BADGSTAT'. There are 4 rows in 1 pages for object 'BADGSTAT'. DBCC results for 'CAMERATYPE'. There are 37 rows in 1 pages for object 'CAMERATYPE'. DBCC results for 'MAPICONGRP_MEMBER'. There are 143 rows in 1 pages for object 'MAPICONGRP_MEMBER'. DBCC results for 'ACTION'. There are 1 rows in 1 pages for object 'ACTION'. DBCC results for 'CCTVDEVICE'. There are 202 rows in 10 pages for object 'CCTVDEVICE'. DBCC results for 'SERVERCAMERATYPE'. There are 37 rows in 1 pages for object 'SERVERCAMERATYPE'. DBCC results for 'MAPITEM'. There are 48 rows in 1 pages for object 'MAPITEM'. DBCC results for 'ACTION_LOG'. There are 29 rows in 1 pages for object 'ACTION_LOG'. DBCC results for 'BDGPRECLINK'. There are 0 rows in 0 pages for object 'BDGPRECLINK'. DBCC results for 'VISIT_EMAIL_LINK'. There are 0 rows in 0 pages for object 'VISIT_EMAIL_LINK'. DBCC results for 'DEFAULTMAPICON'. There are 56 rows in 1 pages for object 'DEFAULTMAPICON'. DBCC results for 'BDGREQFLDLINK'. There are 0 rows in 0 pages for object 'BDGREQFLDLINK'. DBCC results for 'ACTION_GROUP'. There are 0 rows in 1 pages for object 'ACTION_GROUP'. DBCC results for 'MARKEDVIDEO'. There are 0 rows in 1 pages for object 'MARKEDVIDEO'. DBCC results for 'BUILDING'. There are 1 rows in 1 pages for object 'BUILDING'. DBCC results for 'MMOBJS'. There are 3 rows in 1 pages for object 'MMOBJS'. DBCC results for 'CARDFORMAT'. There are 13 rows in 1 pages for object 'CARDFORMAT'. DBCC results for 'SEGMENT_EMAIL_LINK'. There are 0 rows in 0 pages for object 'SEGMENT_EMAIL_LINK'. DBCC results for 'EXECFUNCLISTACTION'. There are 0 rows in 0 pages for object 'EXECFUNCLISTACTION'. DBCC results for 'ACTION_SCHEDULE'. There are 1 rows in 1 pages for object 'ACTION_SCHEDULE'. DBCC results for 'MMOBJTYPS'. There are 2 rows in 1 pages for object 'MMOBJTYPS'. DBCC results for 'WRKSTATION'. There are 2 rows in 1 pages for object 'WRKSTATION'. DBCC results for 'VISIT_SEARCH'. There are 2 rows in 1 pages for object 'VISIT_SEARCH'. DBCC results for 'EXPECTED_TRANSACTION_TIME'. There are 0 rows in 0 pages for object 'EXPECTED_TRANSACTION_TIME'. DBCC results for 'MOBILE_ID_CONTROL'. There are 10 rows in 1 pages for object 'MOBILE_ID_CONTROL'. DBCC results for 'VISIT_SEARCH_ELEMENT'. There are 58 rows in 1 pages for object 'VISIT_SEARCH_ELEMENT'. DBCC results for 'ARCHIVELOCATION'. There are 2 rows in 1 pages for object 'ARCHIVELOCATION'. DBCC results for 'ACCOUNT_GROUP'. There are 0 rows in 0 pages for object 'ACCOUNT_GROUP'. DBCC results for 'MONDEVLINK'. There are 22 rows in 2 pages for object 'MONDEVLINK'. DBCC results for 'CARDFORMAT_SEGMENT_LINK'. There are 0 rows in 0 pages for object 'CARDFORMAT_SEGMENT_LINK'. DBCC results for 'EVENTS_VIDEO'. There are 39 rows in 1 pages for object 'EVENTS_VIDEO'. DBCC results for 'IPCAMERA_FW_DOWNLOAD_ACTION'. There are 0 rows in 0 pages for object 'IPCAMERA_FW_DOWNLOAD_ACTION'. DBCC results for 'ACCESSGRP'. There are 0 rows in 0 pages for object 'ACCESSGRP'. DBCC results for 'BADGE_AREA_LOCATION'. There are 0 rows in 0 pages for object 'BADGE_AREA_LOCATION'. DBCC results for 'MONSTATION'. There are 14 rows in 1 pages for object 'MONSTATION'. DBCC results for 'CCTVCONTROL'. There are 0 rows in 0 pages for object 'CCTVCONTROL'. DBCC results for 'IPCAMERA_FW_DOWNLOAD_CAMERA'. There are 0 rows in 0 pages for object 'IPCAMERA_FW_DOWNLOAD_CAMERA'. DBCC results for 'ACCESSLVL'. There are 0 rows in 0 pages for object 'ACCESSLVL'. DBCC results for 'MUSTER_ZONE_SAFE_LOCATIONS'. There are 0 rows in 0 pages for object 'MUSTER_ZONE_SAFE_LOCATIONS'. DBCC results for 'MONZONE'. There are 1 rows in 1 pages for object 'MONZONE'. DBCC results for 'DDCONNECT'. There are 1 rows in 1 pages for object 'DDCONNECT'. DBCC results for 'LNL_QUEUE'. There are 0 rows in 0 pages for object 'LNL_QUEUE'. DBCC results for 'ACCESSPANE'. There are 23 rows in 2 pages for object 'ACCESSPANE'. DBCC results for 'INPUT_EVENT'. There are 0 rows in 0 pages for object 'INPUT_EVENT'. DBCC results for 'PANELTYPE'. There are 60 rows in 1 pages for object 'PANELTYPE'. DBCC results for 'DDFLD'. There are 128 rows in 3 pages for object 'DDFLD'. CHECKDB found 0 allocation errors and 2 consistency errors in database 'AccessControl'. repair_rebuild is the minimum repair level for the errors found by DBCC CHECKDB (AccessControl ). DBCC execution completed. If DBCC printed error messages, contact your system administrator.
I'm in the process of trying to cutover SLQ 2000 database activity to a newer used server running Windows 2003. All the latest Win & SQL Service Packs through late Feb 2007 have been installed. The server has a Promise Fast Track S150 TX2plus SCSI raid with 2 80 gb drives. I have been using at as database development system for 3 months without any issues.
This morning I restored the latest full backup and 2 intervening transaction log backups. I am the only user on the system today. I ran DBDCC CHECKDB WITH TABLERESULTS 5 times over a 45 minute period and received 5 different results!
Run 1 - No Error
Run 2 - Following Errors:
2511162Table error: Object ID 754101727, Index ID 0. Keys out of order on page (1:631938), slots 40 and 41.repair_rebuild
8990101CHECKDB found 0 allocation errors and 1 consistency errors in table 'DatabaseEventLog' (object ID 754101727).
8928161Object ID 1218103380, index ID 255: Page (1:373888) could not be processed. See other errors for details.repair_allow_data_loss
8990101CHECKDB found 0 allocation errors and 1 consistency errors in table 'WeatherTransaction' (object ID 1218103380).
Run 3 - Following Errors:
2511162Table error: Object ID 754101727, Index ID 0. Keys out of order on page (1:631938), slots 40 and 41.repair_rebuild
8990101CHECKDB found 0 allocation errors and 1 consistency errors in table 'DatabaseEventLog' (object ID 754101727).
8928161Object ID 1218103380, index ID 255: Page (1:373888) could not be processed. See other errors for details.repair_allow_data_loss
8990101CHECKDB found 0 allocation errors and 1 consistency errors in table 'WeatherTransaction' (object ID 1218103380).
Run 4 - Following Errors:
2511162Table error: Object ID 754101727, Index ID 0. Keys out of order on page (1:631938), slots 40 and 41.repair_rebuild
8990101CHECKDB found 0 allocation errors and 1 consistency errors in table 'DatabaseEventLog' (object ID 754101727).
8928161Object ID 1218103380, index ID 255: Page (1:373888) could not be processed. See other errors for details.repair_allow_data_loss
894116102Table error: Object ID 1218103380, index ID 255, page (1:373888). Test (sorted [i].offset >= PAGEHEADSIZE) failed. Slot 8, offset 0x2 is invalid.repair_allow_data_loss
894216101Table error: Object ID 1218103380, index ID 255, page (1:373888). Test (sorted[i].offset >= max) failed. Slot 0, offset 0x8 overlaps with the prior row.repair_allow_data_loss
8990101CHECKDB found 0 allocation errors and 3 consistency errors in table 'WeatherTransaction' (object ID 1218103380).
Run 5 - No Error!
I ran several of the obligatory CHKDSK and had no errors:
c:>chkdsk The type of the file system is NTFS.
WARNING! F parameter not specified. Running CHKDSK in read-only mode.
CHKDSK is verifying files (stage 1 of 3)... File verification completed. CHKDSK is verifying indexes (stage 2 of 3)... Index verification completed. CHKDSK is verifying security descriptors (stage 3 of 3)... Security descriptor verification completed.
78116030 KB total disk space. 45291176 KB in 33231 files. 10496 KB in 3135 indexes. 0 KB in bad sectors. 121086 KB in use by the system. 65536 KB occupied by the log file. 32693272 KB available on disk.
4096 bytes in each allocation unit. 19529007 total allocation units on disk. 8173318 allocation units available on disk.
Are these DBDCC CHECKDB WTIH TABLERESULTS differences normal or is this a bug or hardware issue? Any advice you can offer would be appreciated.
After restoring the SQL Server 2000 user database backup into one of the SQL Server 2000 instances I get database consistency errors. I restored this database on this particular server a several times already and every time the consistency errors were detected by dbcc checkdb; however the errors are not consistent - different types of errors, different tables and indexes are affected. I restored the same database backup into a different server and ran dbcc checkdb over it - no errors occurred. Something causes corruption in the database on one particular server. Here are the initial errors:
DBCC results for 'tTREE_COMPONENTS'. Server: Msg 8928, Level 16, State 1, Line 1 Object ID 1467308437, index ID 0: Page (1:251481) could not be processed. See other errors for details. Server: Msg 8944, Level 16, State 1, Line 1 Table error: Object ID 1467308437, index ID 0, page (1:251481), row 44. Test (ColumnOffsets <= (nextRec - pRec)) failed. Values are 87 and 57. There are 663 rows in 16 pages for object 'tTREE_COMPONENTS'.
DBCC results for 'tACCUMULATORS'. There are 10234724 rows in 97149 pages for object 'tACCUMULATORS'. CHECKDB found 0 allocation errors and 2 consistency errors in table 'tACCUMULATORS' (object ID 1467308437).
DBCC results for 'WATSTARTDATETP'. Server: Msg 8928, Level 16, State 1, Line 1 Object ID 1905493917, index ID 4: Page (3:224866) could not be processed. See other errors for details.
Server: Msg 8941, Level 16, State 1, Line 1 Table error: Object ID 1905493917, index ID 4, page (3:224866). Test (sorted .offset >= PAGEHEADSIZE) failed. Slot 159, offset 0x1 is invalid.
Server: Msg 8942, Level 16, State 1, Line 1 Table error: Object ID 1905493917, index ID 4, page (3:224866). Test (sorted.offset >= max) failed. Slot 0, offset 0x9f overlaps with the prior row. There are 4 rows in 1 pages for object 'WATSTARTDATETP'.
DBCC results for 'ACCRUALTRAN'. There are 5919148 rows in 150538 pages for object 'ACCRUALTRAN'. CHECKDB found 0 allocation errors and 3 consistency errors in table 'ACCRUALTRAN' (object ID 1905493917).
If you could please take a look at the errors and give me your thoughts on what could be the cause for the errors I would greatly appreciate it.
we''re currently performing a dry run of migrating some large (100GB+) SQL Server 2000 databases from a SQL 2000 cluster onto a new 2005 mirrorred database pair. The new configuration has completely separate database servers and a new dedicated SAN.
Upon restoring our largest database we are seeing the following errors recorded in the log after setting up mirroring and then trying to run DBCC CHECKDB:
"Unable to read and latch page (1:1323852) with latch type SH. 21(The device is not ready.) failed."
We are currently investigating the SAN hardware logs to determine if this might be a physical issue as it would seem to indicate, however has anyone any experience of this or insight into what may cause this error?
I have a very strange problem. I have installed MS WS2003 SP2 and MS SQL 9.0.3054 SP2. I have database dbTraceIT with data file on D drive and log file on E drive. If I run T-SQL command:
use dbTraceIT go dbcc checkdb or Integration Services Package (task: Check Database Integrity Task, developed with MS VS)
this comand/or task has generated the hard disk errors on D drive. The chkdsk tool reports errors when hdd index verification has been completed. After hdd errors€™ repairing, if I run checkdb T-sql command the situation is repeated again. Question: is it a bug or something different? Do you have similar disk error if you use e.g. Integration Service Packages (for instance index rebuild or whatever)?
Regards, Dariusz
PS Steps to reproduce
Find any DB on your MS SQL. Run chkdsk command on hard drive where DB€™s data file is stored. Verify that everything is OK. Run t-sql command use dbTraceIT go dbcc checkdb 3. Run chkdsk again. It should show hdd errors.
I am looking for the best way to get notifications if DBCC CHECKDB indicates an error on a database it checks. So lets say I create a maintenance plan that runs CHECKDB at 2AM for all user databases. What is the best method to get notifications that the command reported issues on one of the databases?
1) When I run a query Select * from MY_Table the query never completes. If I press cancel in Query Analyzer after 1 second or 2 minutes, it always shows the same 174 records. The total table size is 800 KB with 3148 rows .. according to TaskPad
2) No queries, even queries that would return only 1 record complete execution against that table
3) I am unable to rename the table, if I try to rename the table Enterprise Manager becomes unresponsive and has to be closed.
4) If I try to browse the rows through Enterprise manager by scrolling through the records, it allows me to go down through a number of rows and then Enterprise manager gives me a timeout expired error.
5) I ran a DBCC CheckDB command ran for 1 hr and 7 minutes. It says there are 0 allocation errors and 0 consistency errors in the database.
6) The other database tables seem to be OK and the Database is operational except for calls involving the 1 Table
I have a basic load proc (loading a staging area.) that truncates a target table just before inserting fresh data in said table, all wrapped in a distributed transaction. What happens (only with certain tables and very inconsistently.) is the truncate will fail (no error) and duplicate data ends up in the target table since no wipe actually occurs. This proc only started having this issue when we went from SQL 2008 to SQL 2014.
I'm programmatically loading a package that was created with VS 2005. The last task in the package is a Send Mail Task. It has two properties, FileAttachments and ToLine, which are set to expressions whose values come directly from package variables. The package runs in debug and non-debug (under VS) correctly.
I followed the advice of Paul Randal, but Im stumped as I am not able to determin what the corruption issues are. This is SQL 2000 and the database is a Solomon database that was recently upgraded to 6.5. the error I get when running the DBCC checkdb is as follows:
Server: Msg 8966, Level 16, State 1, Line 1 Could not read and latch page (1:18645) with latch type SH. sysindexes failed. DBCC execution completed. If DBCC printed error messages, contact your system administrator.
DBCC execution completed. If DBCC printed error messages, contact your system administrator. DBCC execution completed. If DBCC printed error messages, contact your system administrator.
Now, the bad news. I am a bit of a novice and have picked this up from someone who left my company. It appears the latch error has been around for some time and only reared up when I instituted a new back up system that runs a dbcc check befor backing up. I don't think I have any clean backups.
I recently updated the datatype of a sproc parameter from bit to tinyint. When I executed the sproc with the updated parameters the sproc appeared to succeed and returned "1 row(s) affected" in the console. However, the update triggered by the sproc did not actually work.
The table column was a bit which only allows 0 or 1 and the sproc was passing a value of 2 so the table was rejecting this value. However, the sproc did not return an error and appeared to return success. So is there a way to configure the database or sproc to return an error message when this type of error occurs?
I have a parent package that calls child packages inside a For Each container. When I debug/run the parent package (from VS), I get the following error message: Warning: The Execution method succeeded, but the number of errors raised (3) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.
It appears to be failing while executing the child package. However, the logs (via the "progress" tab) for both the parent package and the child package show no errors other than the one listed above (and that shows in the parent package log). The child package appears to validate completely without error (all components are green and no error messages in the log). I turned on SSIS logging to a text file and see nothing in there either.
If I bump up the MaximumErrorCount in the parent package and in the Execute Package Task that calls the child package to 4 (to go one above the error count indicated in the message above), the whole thing executes sucessfully. I don't want to leave the Max Error Count set like this. Is there something I am missing? For example are there errors that do not get logged by default? I get some warnings, do a certain number of warnings equal an error?
Starwin writes "when i execute DBCC CHECKDB, DBCC CHECKCATALOG I reveived the following error. how to solve it?
Server: Msg 8909, Level 16, State 1, Line 1 Table error: Object ID -2093955965, index ID 711, page ID (3:2530). The PageId in the page header = (34443:343146507). . . . . . . . .
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID -1635188736)' (object ID -1635188736). CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID -1600811521)' (object ID -1600811521).
. . . . . . . .
Server: Msg 8909, Level 16, State 1, Line 1 Table error: Object ID -8748568, index ID 50307, page ID (3:2497). The PageId in the page header = (26707:762626875). Server: Msg 8909, Level 16, State 1, Line 1 Table error: Object ID -7615284, index ID 35836, page ID (3:2534). The PageId in the page heade"
I have a few extremely large databases in SQL Server 6.5 sp3 (soon to be 5a - but we won't talk about that!!) NT 4.0 sp4 (about 10 GIG each). I don't have a big window of down-time in order to do any maintenance. Does anyone know of a way to be able to run dbcc checkdb or other dbcc's that I can run to verify the database yet complete within a reasonable amount of time? The last time dbcc checkdb was run, it was started Friday night and still not complete Sunday night. Over a weekend, I may have up to a 24 hour maintenance window.
Any suggestions would be appreciated. Thanks! Toni
Hai , When I ran DBCC CHECK DB of userdatabase, its reporting along with usual messages as Descriptor for system table '8' in database '8' not found in the descriptor hash table. I could'nt understand being familiar error encounterd . Any one will appreciate for the help
I recently took over a SQL server with 300 MB of data. I am relatively new to SQL 6.5 and have been reading that DBCC checkdb and checkalloc should be run at least once per week. Apparently the person before me never ran any of those checks. Is not running the database consistency checks for so long going to present a problem? has anyone run into problems when running those checks? Any advise is greatly appreciated.
I ran "dbcc checkdb(MCMSdb) with no_infomsgs" and I get the following: Server: Msg 8946, Level 16, State 12, Line 2 Table error: Allocation page (1:274992) has invalid PFS_PAGE page header values. Type is 0. Check type, object ID and page ID on the page.
What cane be done to correct this problem? Can this error prevent a user from connecting to the database?
I ran checkdb and found 4 error message on the db.. it seen like same object.. can anyone tell me what it is.. and how can i fix it? thanks !!!!
1. Server: Msg 8976, Level 16, State 1, Line 35 Table error: Object ID 2094630505, index ID 1. Page (1:809859) was not seen in the scan although its parent (1:77885) and previous (1:809767) refer to it. Check any previous errors. 2. Server: Msg 8978, Level 16, State 1, Line 35 Table error: Object ID 2094630505, index ID 1. Page (1:809860) is missing a reference from previous page (1:809859). Possible chain linkage problem. 3. Server: Msg 8976, Level 16, State 1, Line 35 Table error: Object ID 2094630505, index ID 1. Page (1:1453795) was not seen in the scan although its parent (1:1453347) and previous (1:1453796) refer to it. Check any previous errors. 4. Server: Msg 8978, Level 16, State 1, Line 35 Table error: Object ID 2094630505, index ID 1. Page (1:1453801) is missing a reference from previous page (1:1453795). Possible chain linkage problem.
Does anybody know if the results of DBCC CHECKDB are stored anywhere? If yes, where? Also, if you don't select "attempt to repair minor problems" option when you set up the maintenance plan, will SQL Server let you know about any errors Integrity check encounters? If yes, where the erros can be found?
in the SQL 6.5 documentation it says when running the DBCC CHECKDB, you should make the database read Only or DBO use only. Do you guys know if SQL 6.5 locks rows while this runs? In SQL 7.0/2000 it only locks the schema.
I am using windows nt40 and sql server 6.5 on a DEC ALPHA and accidentlly started a dbcc checkdb. Is it possible to stop the process with out damaging the database?
