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.
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.
every few days i'm getting an error in the application log , eventID 824, saying 'SQL Server detected a logical consistency-based i/o error; incorrect checksum. it then recommends completing a full database consistency check (dbcc checkdb).
i have run the dbcc checkdb ('databasename') and it is returning an error msg of:
Msg 8697, Level 16, State 215, Line 1 An internal error occurred in DBCC which prevented further processing Msg 8921, Level 16, State 1, Line 1 Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors
i have oodles of disk space left. any ideas on where to go from here.
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.
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 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 would need help to debug the following allocation errors on DBCC:
Msg 2576, Sev 16: IAM page (0:0) is pointed to by the previous pointer of IAM page (1:958608) object ID 16 index ID 0 but was not detected in the scan. [SQLSTATE 42000] Msg 2576, Sev 16: IAM page (0:0) is pointed to by the previous pointer of IAM page (1:985853) object ID 16 index ID 2 but was not detected in the scan. [SQLSTATE 42000] Msg 2576, Sev 16: IAM page (0:0) is pointed to by the previous pointer of IAM page (1:958600) object ID 16 index ID 255 but was not detected in the scan. [SQLSTATE 42000] Msg 2576, Sev 16: IAM page (0:0) is pointed to by the previous pointer of IAM page (1:1067763) object ID 17 index ID 0 but was not detected in the scan. [SQLSTATE 42000] Msg 2576, Sev 16: IAM page (0:0) is pointed to by the previous pointer of IAM page (1:1120026) object ID 17 index ID 2 but was not detected in the scan. [SQLSTATE 42000] Msg 2576, Sev 16: IAM page (0:0) is pointed to by the previous pointer of IAM page (1:1154482) object ID 17 index ID 3 but was not detected in the scan. [SQLSTATE 42000] Msg 2536, Sev 16: DBCC results for 'SalesHistoryDB'. [SQLSTATE 01000] Msg 2536, Sev 16: DBCC results for 'sysobjects'. [SQLSTATE 01000] Msg 2593, Sev 16: There are 289 rows in 7 pages for object 'sysobjects'. [SQLSTATE 01000] Msg 2536, Sev 16: DBCC results for 'sysindexes'. [SQLSTATE 01000] Msg 2593, Sev 16: There are 277 rows in 19 pages for object 'sysindexes'. [SQLSTATE 01000] Msg 2536, Sev 16: DBCC results for 'syscolumns'. [SQLSTATE 01000] Msg 2593, Sev 16: There are 1809 rows in 43 pages for object 'syscolumns'. [SQLSTATE 01000] Msg 2536, Sev 16: DBCC results for 'systypes'. [SQLSTATE 01000] Msg 2593, Sev 16: There are 28 rows in 1 pages for object 'systypes'. [SQLSTATE 01000] Msg 2536, Sev 16: DBCC results for 'syscomments'. [SQLSTATE 01000] Msg 2593, Sev 16: There are 301 rows in 101 pages for object 'syscomments'. [SQLSTATE 01000] Msg 2536, Sev 16: DBCC results for 'sysfiles1'. [SQLSTATE 01000] Msg 2593, Sev 16: There are 2 rows in 1 pages for object 'sysfiles1'. [SQLSTATE 01000] Msg 2536, Sev 16: DBCC results for 'syspermissions'. [SQLSTATE 01000] Msg 2593, Sev 16: There are 311 rows in 3 pages for object 'syspermissions'. [SQLSTATE 01000] Msg 2536, Sev 16: DBCC results for 'sysusers'. [SQLSTATE 01000] Msg 2593, Sev 16: There are 28 rows in 1 pages for object 'sysusers'. [SQLSTATE 01000] Msg 2536, Sev 16: DBCC results for 'sysproperties'. [SQLSTATE 01000] Msg 2593, Sev 16: There are 199 rows in 6 pages for object 'sysproperties'. [SQLSTATE 01000] Msg 2536, Sev 16: DBCC results for 'sysdepends'. [SQLSTATE 01000] Msg 2593, Sev 16: There are 1768 rows in 11 pages for object 'sysdepends'. [SQLSTATE 01000] Msg 2536, Sev 16: DBCC results for 'sysreferences'. [SQLSTATE 01000] Msg 2593, Sev 16: There are 0 rows in 1 pages for object 'sysreferences'. [SQLSTATE 01000] Msg 8990, Sev 16: CHECKDB found 3 allocation errors and 0 consistency errors in table '(Object ID 16)' (object ID 16). [SQLSTATE 01000] Msg 8990, Sev 16: CHECKDB found 3 allocation errors and 0 consistency errors in table '(Object ID 17)' (object ID 17). [SQLSTATE 01000] Msg 2536, Sev 16: DBCC results for 'sysfulltextcatalogs'. [SQLSTATE 01000] Msg 2593, Sev 16: There are 0 rows in 1 pages for object 'sysfulltextcatalogs'. [SQLSTATE 01000] DBCC results for 'sysfulltextnotify'. [SQLSTATE 01000] There are 0 rows in 0 pages for object 'sysfulltextnotify'. [SQLSTATE 01000] DBCC results for 'sysfilegroups'. [SQLSTATE 01000] There are 1 rows in 1 pages for object 'sysfilegroups'. [SQLSTATE 01000] DBCC results for 'IgnoreSalesRep'. [SQLSTATE 01000] There are 406 rows in 2 pages for object 'IgnoreSalesRep'. [SQLSTATE 01000] DBCC results for 'invnsrc'. [SQLSTATE 01000] There are 6101966 rows in 15067 pages for object 'invnsrc'. [SQLSTATE 01000] DBCC results for 'INVO_ERRS'. [SQLSTATE 01000] There are 333 rows in 12 pages for object 'INVO_ERRS'. [SQLSTATE 01000] DBCC results for 'INVO_ERRS_old'. [SQLSTATE 01000] There are 152 rows in 3 pages for object 'INVO_ERRS_old'. [SQLSTATE 01000] DBCC results for 'INVO_HIST'. [SQLSTATE 01000] There are 55159551 rows in 937501 pages for object 'INVO_HIST'. [SQLSTATE 01000] DBCC results for 'INVO_HIST_SMALL'. [SQLSTATE 01000] There are 1124659 rows in 21220 pages for object 'INVO_HIST_SMALL'. [SQLSTATE 01000] DBCC results for 'InvoiceHistory'. [SQLSTATE 01000] There are 0 rows in 1 pages for object 'InvoiceHistory'. [SQLSTATE 01000] DBCC results for 'QUAR_INVO_HIST'. [SQLSTATE 01000] There are 1430739 rows in 5379 pages for object 'QUAR_INVO_HIST'. [SQLSTATE 01000] DBCC results for 'MARKETING_REPORTS'. [SQLSTATE 01000] There are 36371 rows in 151 pages for object 'MARKETING_REPORTS'. [SQLSTATE 01000] DBCC results for 'MKP90'. [SQLSTATE 01000] There are 36030746 rows in 205890 pages for object 'MKP90'. [SQLSTATE 01000] DBCC results for 'MR_CLASS_MANU'. [SQLSTATE 01000] There are 12159 rows in 46 pages for object 'MR_CLASS_MANU'. [SQLSTATE 01000] DBCC results for 'MR_GROUP_MANU'. [SQLSTATE 01000] There are 16889 rows in 66 pages for object 'MR_GROUP_MANU'. [SQLSTATE 01000] DBCC results for 'MR_MANU_CLASS'. [SQLSTATE 01000] There are 4876 rows in 19 pages for object 'MR_MANU_CLASS'. [SQLSTATE 01000] DBCC results for 'MR_MANU_GROUP'. [SQLSTATE 01000] There are 15565 rows in 61 pages for object 'MR_MANU_GROUP'. [SQLSTATE 01000] DBCC results for 'PseudoLeaders'. [SQLSTATE 01000] There are 79 rows in 2 pages for object 'PseudoLeaders'. [SQLSTATE 01000] DBCC results for 'InvoiceHeader'. [SQLSTATE 01000] There are 0 rows in 1 pages for object 'InvoiceHeader'. [SQLSTATE 01000] DBCC results for 'FedTeamGoals'. [SQLSTATE 01000] There are 0 rows in 1 pages for object 'FedTeamGoals'. [SQLSTATE 01000] DBCC results for 'SALES_MODIFIER'. [SQLSTATE 01000] There are 1 rows in 1 pages for object 'SALES_MODIFIER'. [SQLSTATE 01000] DBCC results for 'FedTeamPlayers'. [SQLSTATE 01000] There are 0 rows in 1 pages for object 'FedTeamPlayers'. [SQLSTATE 01000] DBCC results for 'CGTempWMS'. [SQLSTATE 01000] There are 25 rows in 1 pages for object 'CGTempWMS'. [SQLSTATE 01000] DBCC results for 'srcinvn'. [SQLSTATE 01000] There are 1 rows in 1 pages for object 'srcinvn'. [SQLSTATE 01000] DBCC results for 'TEMP_ExtranetData'. [SQLSTATE 01000] There are 0 rows in 1 pages for object 'TEMP_ExtranetData'. [SQLSTATE 01000] DBCC results for 'EMP10'. [SQLSTATE 01000] There are 113373 rows in 1471 pages for object 'EMP10'. [SQLSTATE 01000] DBCC results for 'EMP10_UNIQUE'. [SQLSTATE 01000] There are 18947 rows in 245 pages for object 'EMP10_UNIQUE'. [SQLSTATE 01000] DBCC results for 'ITEM_SALES_306090'. [SQLSTATE 01000] There are 310629 rows in 929 pages for object 'ITEM_SALES_306090'. [SQLSTATE 01000] DBCC results for 'temp_SalesSummaryData'. [SQLSTATE 01000] There are 45781 rows in 751 pages for object 'temp_SalesSummaryData'. [SQLSTATE 01000] DBCC results for 'Rob_DeletedFromCustomerPricingMatrix20031107'. [SQLSTATE 01000] There are 1469 rows in 6 pages for object 'Rob_DeletedFromCustomerPricingMatrix20031107'. [SQLSTATE 01000] DBCC results for 'COMMISSION_ADJ'. [SQLSTATE 01000] There are 1645553 rows in 37801 pages for object 'COMMISSION_ADJ'. [SQLSTATE 01000] DBCC results for 'SalesSummaryData'. [SQLSTATE 01000] There are 2288331 rows in 36372 pages for object 'SalesSummaryData'. [SQLSTATE 01000] DBCC results for 'CDW_CODB'. [SQLSTATE 01000] There are 2 rows in 1 pages for object 'CDW_CODB'. [SQLSTATE 01000] DBCC results for 'dtproperties'. [SQLSTATE 01000] There are 14 rows in 1 pages for object 'dtproperties'. [SQLSTATE 01000] DBCC results for 'Temp_SalesData_new'. [SQLSTATE 01000] There are 7275 rows in 94 pages for object 'Temp_SalesData_new'. [SQLSTATE 01000] DBCC results for 'MKP97'. [SQLSTATE 01000] There are 818535 rows in 6628 pages for object 'MKP97'. [SQLSTATE 01000] DBCC results for 'MARKETING_REPORTS_Saved'. [SQLSTATE 01000] There are 28431 rows in 113 pages for object 'MARKETING_REPORTS_Saved'. [SQLSTATE 01000] DBCC results for 'Commission_Adjustment'. [SQLSTATE 01000] There are 0 rows in 1 pages for object 'Commission_Adjustment'. [SQLSTATE 01000] DBCC results for 'F1730A'. [SQLSTATE 01000] There are 1124104 rows in 16059 pages for object 'F1730A'. [SQLSTATE 01000] DBCC results for 'OEP80U'. [SQLSTATE 01000] There are 1357451 rows in 11634 pages for object 'OEP80U'. [SQLSTATE 01000] DBCC results for 'OE40LN'. [SQLSTATE 01000] There are 1281910 rows in 10155 pages for object 'OE40LN'. [SQLSTATE 01000] DBCC results for 'sysarticles'. [SQLSTATE 01000] There are 2 rows in 1 pages for object 'sysarticles'. [SQLSTATE 01000] DBCC results for 'sysschemaarticles'. [SQLSTATE 01000] There are 0 rows in 0 pages for object 'sysschemaarticles'. [SQLSTATE 01000] DBCC results for 'syspublications'. [SQLSTATE 01000] There are 1 rows in 1 pages for object 'syspublications'. [SQLSTATE 01000] DBCC results for 'CommissionGoalsRange'. [SQLSTATE 01000] There are 12 rows in 1 pages for object 'CommissionGoalsRange'. [SQLSTATE 01000] DBCC results for 'LOSGoals'. [SQLSTATE 01000] There are 107 rows in 1 pages for object 'LOSGoals'. [SQLSTATE 01000] DBCC results for 'OrderInstallInfo'. [SQLSTATE 01000] There are 318699 rows in 1241 pages for object 'OrderInstallInfo'. [SQLSTATE 01000] DBCC results for 'syssubscriptions'. [SQLSTATE 01000] There are 4 rows in 1 pages for object 'syssubscriptions'. [SQLSTATE 01000] DBCC results for 'sysarticleupdates'. [SQLSTATE 01000] There are 0 rows in 0 pages for object 'sysarticleupdates'. [SQLSTATE 01000] DBCC results for 'MSpub_identity_range'. [SQLSTATE 01000] There are 0 rows in 0 pages for object 'MSpub_identity_range'. [SQLSTATE 01000] DBCC results for 'systranschemas'. [SQLSTATE 01000] Msg 2576, Sev 16: IAM page (1:1170538) is pointed to by the previous pointer of IAM page (1:1170540) object ID 1583344705 index ID 0 but was not detected in the scan. [SQLSTATE 42000] Msg 8947, Sev 16: Table error: Multiple IAM pages for object ID 1583344705, index ID 0 contain allocations for the same interval. IAM pages (1:1170540) and (1:2502333). [SQLSTATE 42000] Msg 2576, Sev 16: IAM page (1:2502332) is pointed to by the previous pointer of IAM page (1:2502333) object ID 1583344705 index ID 0 but was not detected in the scan. [SQLSTATE 42000] Msg 2593, Sev 16: There are 0 rows in 0 pages for object 'systranschemas'. [SQLSTATE 01000] Msg 8990, Sev 16: CHECKDB found 3 allocation errors and 0 consistency errors in table '(Object ID 1583344705)' (object ID 1583344705). [SQLSTATE 01000] Msg 2536, Sev 16: DBCC results for 'DummyTrans'. [SQLSTATE 01000] Msg 2593, Sev 16: There are 0 rows in 0 pages for object 'DummyTrans'. [SQLSTATE 01000] Msg 2536, Sev 16: DBCC results for 'InvoiceDownloadCheck'. [SQLSTATE 01000] Msg 2593, Sev 16: There are 9 rows in 1 pages for object 'InvoiceDownloadCheck'. [SQLSTATE 01000] Msg 2536, Sev 16: DBCC results for 'ORDER_HIST_MUNICH'. [SQLSTATE 01000] Msg 2593, Sev 16: There are 0 rows in 0 pages for object 'ORDER_HIST_MUNICH'. [SQLSTATE 01000] Msg 2536, Sev 16: DBCC results for 'ACTIONS'. [SQLSTATE 01000] Msg 2593, Sev 16: There are 3864063 rows in 43417 pages for object 'ACTIONS'. [SQLSTATE 01000] Msg 2536, Sev 16: DBCC results for 'CALLVOLUME_REQ'. [SQLSTATE 01000] Msg 2593, Sev 16: There are 24 rows in 1 pages for object 'CALLVOLUME_REQ'. [SQLSTATE 01000] Msg 2536, Sev 16: DBCC results for 'COMMISH_GOALS'. [SQLSTATE 01000] Msg 2593, Sev 16: There are 273 rows in 2 pages for object 'COMMISH_GOALS'. [SQLSTATE 01000] Msg 2536, Sev 16: DBCC results for 'CM210X'. [SQLSTATE 01000] Msg 2593, Sev 16: There are 1826290 rows in 97778 pages for object 'CM210X'. [SQLSTATE 01000] Msg 2536, Sev 16: DBCC results for 'CM30'. [SQLSTATE 01000] Msg 2593, Sev 16: There are 96 rows in 1 pages for object 'CM30'. [SQLSTATE 01000] Msg 2536, Sev 16: DBCC results for 'CM31'. [SQLSTATE 01000] Msg 2593, Sev 16: There are 32 rows in 1 pages for object 'CM31'. [SQLSTATE 01000] Msg 2536, Sev 16: DBCC results for 'COMMISSION_ADJ_INDEX'. [SQLSTATE 01000] Msg 2593, Sev 16: There are 1 rows in 1 pages for object 'COMMISSION_ADJ_INDEX'. [SQLSTATE 01000] Msg 2536, Sev 16: DBCC results for 'COMMISSION_DAILY'. [SQLSTATE 01000] Msg 2593, Sev 16: There are 1659173 rows in 17841 pages for object 'COMMISSION_DAILY'. [SQLSTATE 01000] DBCC results for 'COMMISSION_EMP'. [SQLSTATE 01000] There are 12080 rows in 58 pages for object 'COMMISSION_EMP'. [SQLSTATE 01000] DBCC results for 'CUST_INVO_SUMMARY'. [SQLSTATE 01000] There are 9512732 rows in 65156 pages for object 'CUST_INVO_SUMMARY'. [SQLSTATE 01000] DBCC results for 'DAILY_PHONE'. [SQLSTATE 01000] There are 1918105 rows in 20566 pages for object 'DAILY_PHONE'. [SQLSTATE 01000] DBCC results for 'Dates2Run'. [SQLSTATE 01000] There are 31 rows in 1 pages for object 'Dates2Run'. [SQLSTATE 01000] DBCC results for 'DAILY_PHONE_ERRORS'. [SQLSTATE 01000] There are 1701 rows in 18 pages for object 'DAILY_PHONE_ERRORS'. [SQLSTATE 01000] CHECKDB found 9 allocation errors and 0 consistency errors in database 'SalesHistoryDB'. [SQLSTATE 01000] repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (SalesHistoryDB ). [SQLSTATE 01000] DBCC execution completed. If DBCC printed error messages, contact your system administrator. [SQLSTATE 01000]
Lou writes "Msg 2576, Sev 16: IAM page (0:0) is pointed to by the previous pointer of IAM page (1:958608) object ID 16 index ID 0 but was not detected in the scan. [SQLSTATE 42000] Msg 2576, Sev 16: IAM page (0:0) is pointed to by the previous pointer of IAM page (1:985853) object ID 16 index ID 2 but was not detected in the scan. [SQLSTATE 42000] Msg 2576, Sev 16: IAM page (0:0) is pointed to by the previous pointer of IAM page (1:958600) object ID 16 index ID 255 but was not detected in the scan. [SQLSTATE 42000] Msg 2576, Sev 16: IAM page (0:0) is pointed to by the previous pointer of IAM page (1:1067763) object ID 17 index ID 0 but was not detected in the scan. [SQLSTATE 42000] Msg 2576, Sev 16: IAM page (0:0) is pointed to by the previous pointer of IAM page (1:1120026) object ID 17 index ID 2 but was not detected in the scan. [SQLSTATE 42000] Msg 2576, Sev 16: IAM page (0:0) is pointed to by the previous pointer of IAM page (1:1154482) object ID 17 index ID 3 but was not detected in the scan. [SQLSTATE 42000] Msg 2536, Sev 16: DBCC results for 'SalesHistoryDB'. [SQLSTATE 01000] Msg 2536, Sev 16: DBCC results for 'sysobjects'. [SQLSTATE 01000] Msg 2593, Sev 16: There are 289 rows in 7 pages for object 'sysobjects'. [SQLSTATE 01000] Msg 2536, Sev 16: DBCC results for 'sysindexes'. [SQLSTATE 01000] Msg 2593, Sev 16: There are 277 rows in 19 pages for object 'sysindexes'. [SQLSTATE 01000] Msg 2536, Sev 16: DBCC results for 'syscolumns'. [SQLSTATE 01000] Msg 2593, Sev 16: There are 1809 rows in 43 pages for object 'syscolumns'. [SQLSTATE 01000] Msg 2536, Sev 16: DBCC results for 'systypes'. [SQLSTATE 01000] Msg 2593, Sev 16: There are 28 rows in 1 pages for object 'systypes'. [SQLSTATE 01000] Msg 2536, Sev 16: DBCC results for 'syscomments'. [SQLSTATE 01000] Msg 2593, Sev 16: There are 301 rows in 101 pages for object 'syscomments'. [SQLSTATE 01000] Msg 2536, Sev 16: DBCC results for 'sysfiles1'. [SQLSTATE 01000] Msg 2593, Sev 16: There are 2 rows in 1 pages for object 'sysfiles1'. [SQLSTATE 01000] Msg 2536, Sev 16: DBCC results for 'syspermissions'. [SQLSTATE 01000] Msg 2593, Sev 16: There are 311 rows in 3 pages for object 'syspermissions'. [SQLSTATE 01000] Msg 2536, Sev 16: DBCC results for 'sysusers'. [SQLSTATE 01000] Msg 2593, Sev 16: There are 28 rows in 1 pages for object 'sysusers'. [SQLSTATE 01000] Msg 2536, Sev 16: DBCC results for 'sysproperties'. [SQLSTATE 01000] Msg 2593, Sev 16: There are 199 rows in 6 pages for object 'sysproperties'. [SQLSTATE 01000] Msg 2536, Sev 16: DBCC results for 'sysdepends'. [SQLSTATE 01000] Msg 2593, Sev 16: There are 1768 rows in 11 pages for object 'sysdepends'. [SQLSTATE 01000] Msg 2536, Sev 16: DBCC results for 'sysreferences'. [SQLSTATE 01000] Msg 2593, Sev 16: There are 0 rows in 1 pages for object 'sysreferences'. [SQLSTATE 01000] Msg 8990, Sev 16: CHECKDB found 3 allocation errors and 0 consistency errors in table '(Object ID 16)' (object ID 16). [SQLSTATE 01000] Msg 8990, Sev 16: CHECKDB found 3 allocation errors and 0 consistency errors in table '(Object ID 17)' (object ID 17). [SQLSTATE 01000] Msg 2536, Sev 16: DBCC results for 'sysfulltextcatalogs'. [SQLSTATE 01000] Msg 2593, Sev 16: There are 0 rows in 1 pages for object 'sysfulltextcatalogs'. [SQLSTATE 01000] DBCC results for 'sysfulltextnotify'. [SQLSTATE 01000] There are 0 rows in 0 pages for object 'sysfulltextnotify'. [SQLSTATE 01000] DBCC results for 'sysfilegroups'. [SQLSTATE 01000] There are 1 rows in 1 pages for object 'sysfilegroups'. [SQLSTATE 01000] DBCC results for 'IgnoreSalesRep'. [SQLSTATE 01000] There are 406 rows in 2 pages for object 'IgnoreSalesRep'. [SQLSTATE 01000] DBCC results for 'invnsrc'. [SQLSTATE 01000] There are 6101966 rows in 15067 pages for object 'invnsrc'. [SQLSTATE 01000] DBCC results for 'INVO_ERRS'. [SQLSTATE 01000] There are 333 rows in 12 pages for object 'INVO
I am running SQL Server 2005 (SP2). Recently, DBCC CHECK TABLE reported an error on one of the tables:
... Table error: Object ID 69575286, index ID 1, partition ID 72057594191216640, alloc unit ID 72057594202161152 (type In-row data). Keys out of order on page (1:261791), slots 8 and 9. Msg 8986, Level 16, State 1, Line 1 Too many errors found (201) for object ID 69575286. To see all error messages rerun the statement using "WITH ALL_ERRORMSGS". There are 142506 rows in 6583 pages for object "AllLinks". CHECKTABLE found 0 allocation errors and 1141 consistency errors in table 'AllLinks' (object ID 69575286). repair_rebuild is the minimum repair level for the errors found by DBCC CHECKTABLE (STS_Content_TFS.dbo.AllLinks). DBCC execution completed. If DBCC printed error messages, contact your system administrator.
The interesting thing is that I can query entire table without problems. I managed to pull all data into new table and recreate all indexes. My undertanding is that Index ID 1 is a clustered index. It looks to me this error is not very critical although repair_rebuild is advised.
Any thoughts on this matter is greately appreciated.
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'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
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 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.
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.
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
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?
When running dbcc checkdb from my workstation(nt) I recieve some of the output and then I get "Connection Broken" this is on a 6.5 machine with the service pack 5, what could be causing my ODBC connection to drop during the proccess of running checkdb?
How can I make the dbcc checkdb fail so I can get the errors displayed in the report log? DBCC Checkdb is the step in the integrity job that I run once a month. What I am trying to do is when the dbcc checkdb fails for any reason, I want to get notified so I can correct the problem. I don't want to use repair fast or any other repair parameters that you can select when you run dbcc checkdb function because most of my dbs are 24x7.
I have a job set up that runs the dbcc checkdb and puts the results into a table. Then I run a query against this table to check the results of dbcc checkdb. If there are errors, I get a page that lets me know that there are some problems. When I ran this job on my production server, the job failed stating that there are problems with data integrity. So I copied this db to a dev server and recreated the job just like I have in prod. The job completed successfully withou any errors. Can anybody tell me what to look at to figure out why it failed on the prod server?
