locked
DBCC CheckDB RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I am brand new to database Engine forum. I have been searching all along for a solution. I need your help with the following. I did a DBCC check DB for my Database and this is what I got. Can someone tell me what it means ?

    Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (1:72772). The PageId in the page header = (0:0).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (1:72773). The PageId in the page header = (0:0).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (1:72776). The PageId in the page header = (0:0).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (1:72784). The PageId in the page header = (0:0).
CHECKDB found 0 allocation errors and 11 consistency errors not associated with any single object.
DBCC results for 'sysobjects'.
There are 676 rows in 13 pages for object 'sysobjects'.
DBCC results for 'sysindexes'.
There are 344 rows in 16 pages for object 'sysindexes'.
DBCC results for 'syscolumns'.
There are 2251 rows in 37 pages for object 'syscolumns'.
DBCC results for 'systypes'.
There are 26 rows in 1 pages for object 'systypes'.
DBCC results for 'syscomments'.
There are 469 rows in 58 pages for object 'syscomments'.
DBCC results for 'sysfiles1'.
There are 2 rows in 1 pages for object 'sysfiles1'.
DBCC results for 'syspermissions'.
There are 19 rows in 1 pages for object 'syspermissions'.
DBCC results for 'sysusers'.
There are 18 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 548 rows in 3 pages for object 'sysdepends'.
DBCC results for 'sysreferences'.
There are 89 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 'Application_Checkbooks'.
There are 108 rows in 1 pages for object 'Application_Checkbooks'.
DBCC results for 'Application_Component'.
There are 32 rows in 1 pages for object 'Application_Component'.
DBCC results for 'Application_Forms'.
There are 185 rows in 1 pages for object 'Application_Forms'.
DBCC results for 'Application_Instance'.
There are 110 rows in 1 pages for object 'Application_Instance'.
DBCC results for 'Application_Scripts'.
There are 11 rows in 1 pages for object 'Application_Scripts'.
DBCC results for 'Application_Types'.
There are 2 rows in 1 pages for object 'Application_Types'.
DBCC results for 'Applications'.
There are 14 rows in 1 pages for object 'Applications'.
DBCC results for 'Attribute_Types'.
There are 3 rows in 1 pages for object 'Attribute_Types'.
DBCC results for 'Check_Registry_Report'.
There are 0 rows in 0 pages for object 'Check_Registry_Report'.
DBCC results for 'Checkbook_Accounts'.
There are 2 rows in 1 pages for object 'Checkbook_Accounts'.
DBCC results for 'Checkbook_Instance'.
There are 79 rows in 2 pages for object 'Checkbook_Instance'.
DBCC results for 'Checkbook_Resources'.
There are 216 rows in 1 pages for object 'Checkbook_Resources'.
DBCC results for 'Checkbooks'.
There are 9 rows in 1 pages for object 'Checkbooks'.
DBCC results for 'Conditional_Types'.
There are 4 rows in 1 pages for object 'Conditional_Types'.
DBCC results for 'Conditionals'.
There are 206 rows in 1 pages for object 'Conditionals'.
DBCC results for 'Event_Log'.
There are 1694 rows in 27 pages for object 'Event_Log'.
DBCC results for 'Feature_Access_Control_list'.
There are 420 rows in 1 pages for object 'Feature_Access_Control_list'.
DBCC results for 'Feature_Group_Features'.
There are 72 rows in 1 pages for object 'Feature_Group_Features'.
DBCC results for 'Feature_Groups'.
There are 3 rows in 1 pages for object 'Feature_Groups'.
DBCC results for 'Features'.
There are 70 rows in 1 pages for object 'Features'.
DBCC results for 'Field_Attribute_Types'.
There are 122 rows in 1 pages for object 'Field_Attribute_Types'.
DBCC results for 'Field_Attributes'.
There are 66 rows in 1 pages for object 'Field_Attributes'.
DBCC results for 'Field_Definition'.
There are 572 rows in 5 pages for object 'Field_Definition'.
DBCC results for 'Field_Types'.
There are 4 rows in 1 pages for object 'Field_Types'.
DBCC results for 'Fonts'.
There are 63 rows in 1 pages for object 'Fonts'.
DBCC results for 'Form_Field_Types'.
There are 7 rows in 1 pages for object 'Form_Field_Types'.
DBCC results for 'Form_Instance'.
There are 5 rows in 1 pages for object 'Form_Instance'.
DBCC results for 'Form_Types'.
There are 4 rows in 1 pages for object 'Form_Types'.
DBCC results for 'Forms'.
There are 4 rows in 1 pages for object 'Forms'.
DBCC results for 'FrmGfx_Field'.
There are 1586 rows in 27 pages for object 'FrmGfx_Field'.
DBCC results for 'Group_Users'.
There are 0 rows in 0 pages for object 'Group_Users'.
DBCC results for 'Groups'.
There are 0 rows in 0 pages for object 'Groups'.
DBCC results for 'History'.
There are 2771 rows in 47 pages for object 'History'.
DBCC results for 'History_Action_Link'.
There are 0 rows in 0 pages for object 'History_Action_Link'.
DBCC results for 'History_Actions'.
There are 7 rows in 1 pages for object 'History_Actions'.
DBCC results for 'History_Link'.
There are 277274 rows in 1033 pages for object 'History_Link'.
DBCC results for 'History_Record_Types'.
There are 3 rows in 1 pages for object 'History_Record_Types'.
DBCC results for 'INI_Entry'.
There are 27 rows in 1 pages for object 'INI_Entry'.
DBCC results for 'INI_Values'.
There are 285 rows in 6 pages for object 'INI_Values'.
DBCC results for 'Job_Types'.
There are 7 rows in 1 pages for object 'Job_Types'.
DBCC results for 'Justification_Types'.
There are 3 rows in 1 pages for object 'Justification_Types'.
DBCC results for 'Machines'.
There are 0 rows in 0 pages for object 'Machines'.
DBCC results for 'Paper_Orientation'.
There are 4 rows in 1 pages for object 'Paper_Orientation'.
DBCC results for 'Postal_Addresses'.
There are 58 rows in 1 pages for object 'Postal_Addresses'.
DBCC results for 'Printer_Access'.
There are 0 rows in 0 pages for object 'Printer_Access'.
DBCC results for 'Printer_Engine_Map'.
There are 0 rows in 0 pages for object 'Printer_Engine_Map'.
DBCC results for 'Printer_Engines'.
There are 1 rows in 1 pages for object 'Printer_Engines'.
DBCC results for 'Printer_Group_Link'.
There are 0 rows in 0 pages for object 'Printer_Group_Link'.
DBCC results for 'Printer_Groups'.
There are 0 rows in 0 pages for object 'Printer_Groups'.
DBCC results for 'Printer_Locales'.
There are 1 rows in 1 pages for object 'Printer_Locales'.
DBCC results for 'Printer_Types'.
There are 4 rows in 1 pages for object 'Printer_Types'.
DBCC results for 'Printers'.
There are 2 rows in 1 pages for object 'Printers'.
DBCC results for 'Record_Fields'.
There are 572 rows in 2 pages for object 'Record_Fields'.
DBCC results for 'Record_Layout'.
There are 3 rows in 1 pages for object 'Record_Layout'.
DBCC results for 'Report_Fields'.
There are 0 rows in 0 pages for object 'Report_Fields'.
DBCC results for 'Report_Launch_Type_Categories'.
There are 5 rows in 1 pages for object 'Report_Launch_Type_Categories'.
DBCC results for 'Report_Launch_Types'.
There are 8 rows in 1 pages for object 'Report_Launch_Types'.
DBCC results for 'Report_Recipient_Access'.
There are 0 rows in 0 pages for object 'Report_Recipient_Access'.
DBCC results for 'Report_Types'.
There are 15 rows in 1 pages for object 'Report_Types'.
DBCC results for 'Report_View_Access_Control_List'.
There are 1 rows in 1 pages for object 'Report_View_Access_Control_List'.
DBCC results for 'Report_View_Fields'.
There are 0 rows in 0 pages for object 'Report_View_Fields'.
DBCC results for 'Report_Views'.
There are 1 rows in 1 pages for object 'Report_Views'.
DBCC results for 'Reports'.
There are 29 rows in 1 pages for object 'Reports'.
DBCC results for 'Resource_Instance'.
There are 121 rows in 1 pages for object 'Resource_Instance'.
DBCC results for 'Resource_Security_Device'.
There are 0 rows in 0 pages for object 'Resource_Security_Device'.
DBCC results for 'Resource_Types'.
There are 8 rows in 1 pages for object 'Resource_Types'.
DBCC results for 'Resources'.
There are 114 rows in 2 pages for object 'Resources'.
DBCC results for 'Script_Groups'.
There are 0 rows in 0 pages for object 'Script_Groups'.
DBCC results for 'Script_Instance'.
There are 0 rows in 0 pages for object 'Script_Instance'.
DBCC results for 'Script_Parameters'.
There are 18 rows in 1 pages for object 'Script_Parameters'.
DBCC results for 'Scripts'.
There are 11 rows in 1 pages for object 'Scripts'.
DBCC results for 'Security_Device'.
There are 1 rows in 1 pages for object 'Security_Device'.
DBCC results for 'Security_Device_Type'.
There are 3 rows in 1 pages for object 'Security_Device_Type'.
DBCC results for 'Secure32Application.0000000002_0000'.
There are 89362 rows in 1261 pages for object 'Secure32Application.0000000002_0000'.
DBCC results for 'Security_Identifier'.
There are 30 rows in 1 pages for object 'Security_Identifier'.
DBCC results for 'Source_File_Types'.
There are 3 rows in 1 pages for object 'Source_File_Types'.
DBCC results for 'Secure32Application.0000000002_0001'.
There are 89362 rows in 11369 pages for object 'Secure32Application.0000000002_0001'.
DBCC results for 'Source_Proc_Table'.
There are 0 rows in 0 pages for object 'Source_Proc_Table'.
DBCC results for 'Tray_Types'.
There are 4 rows in 1 pages for object 'Tray_Types'.
DBCC results for 'Secure32Application.0000000002_0002'.
There are 89362 rows in 3713 pages for object 'Secure32Application.0000000002_0002'.
DBCC results for 'UID_Manager'.
There are 3 rows in 1 pages for object 'UID_Manager'.
DBCC results for 'Users'.
There are 6 rows in 1 pages for object 'Users'.
DBCC results for 'Secure32Application.0000000003_0000'.
Msg 8928, Level 16, State 1, Line 1
Object ID 1543676547, index ID 0: Page (1:72776) could not be processed. See other errors for details.
There are 187906 rows in 2648 pages for object 'Secure32Application.0000000003_0000'.
CHECKDB found 0 allocation errors and 1 consistency errors in table 'Secure32Application.0000000003_0000' (object ID 1543676547).
DBCC results for 'Watch_Configurations'.
There are 6 rows in 1 pages for object 'Watch_Configurations'.
DBCC results for 'Watch_Script_Link'.
There are 6 rows in 1 pages for object 'Watch_Script_Link'.
DBCC results for 'Secure32Application.0000000003_0001'.
Msg 8928, Level 16, State 1, Line 1
Object ID 1575676661, index ID 0: Page (1:72768) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 1575676661, index ID 0: Page (1:72769) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 1575676661, index ID 0: Page (1:72770) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 1575676661, index ID 0: Page (1:72771) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 1575676661, index ID 0: Page (1:72772) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 1575676661, index ID 0: Page (1:72773) could not be processed. See other errors for details.
There are 187906 rows in 23331 pages for object 'Secure32Application.0000000003_0001'.
CHECKDB found 0 allocation errors and 6 consistency errors in table 'Secure32Application.0000000003_0001' (object ID 1575676661).
DBCC results for 'Watch_Types'.
There are 3 rows in 1 pages for object 'Watch_Types'.
DBCC results for 'ACHBankInfo'.
There are 0 rows in 0 pages for object 'ACHBankInfo'.
DBCC results for 'Secure32Application.0000000003_0002'.
Msg 8928, Level 16, State 1, Line 1
Object ID 1607676775, index ID 0: Page (1:72760) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 1607676775, index ID 0: Page (1:72761) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 1607676775, index ID 0: Page (1:72762) could not be processed. See other errors for details.
There are 187906 rows in 7876 pages for object 'Secure32Application.0000000003_0002'.
CHECKDB found 0 allocation errors and 3 consistency errors in table 'Secure32Application.0000000003_0002' (object ID 1607676775).
DBCC results for 'ACHCommScripts'.
There are 0 rows in 0 pages for object 'ACHCommScripts'.
DBCC results for 'ACHCompany'.
There are 0 rows in 0 pages for object 'ACHCompany'.
DBCC results for 'ACHIndividual'.
There are 0 rows in 0 pages for object 'ACHIndividual'.
DBCC results for 'ACHHeader'.
There are 0 rows in 0 pages for object 'ACHHeader'.
DBCC results for 'ACHHolidays'.
There are 0 rows in 0 pages for object 'ACHHolidays'.
DBCC results for 'ACHAddenda'.
There are 0 rows in 0 pages for object 'ACHAddenda'.
DBCC results for 'PosPayCommScripts'.
There are 0 rows in 0 pages for object 'PosPayCommScripts'.
DBCC results for 'AdvisementLogs'.
There are 0 rows in 0 pages for object 'AdvisementLogs'.
DBCC results for 'Reconciliation'.
Msg 8928, Level 16, State 1, Line 1
Object ID 1742629251, index ID 0: Page (1:72784) could not be processed. See other errors for details.
There are 286902 rows in 4422 pages for object 'Reconciliation'.
CHECKDB found 0 allocation errors and 1 consistency errors in table 'Reconciliation' (object ID 1742629251).
DBCC results for 'Reconciliation_Types'.
There are 6 rows in 1 pages for object 'Reconciliation_Types'.
CHECKDB found 0 allocation errors and 22 consistency errors in database 'secure32dbomegaprotein'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (secure32dbomegaprotein ).
DBCC execution completed. If DBCC printed error messages, contact your system administrator.

    The reason I did the CheckDB I viewed the error log see below for log and after googling this topic I was told by this thread.

    http://en.allexperts.com/q/MS-SQL-Server-1801/O-error-bad-page.htm

    2013-06-05 11:21:01.16 server    Microsoft SQL Server  2000 - 8.00.760 (Intel X86) 
	Dec 17 2002 14:22:05 
	Copyright (c) 1988-2003 Microsoft Corporation
	Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 3)

2013-06-05 11:21:01.16 server    Copyright (C) 1988-2002 Microsoft Corporation.
2013-06-05 11:21:01.16 server    All rights reserved.
2013-06-05 11:21:01.16 server    Server Process ID is 1736.
2013-06-05 11:21:01.16 server    Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\Mssql\Data\MSSQL\LOG\ERRORLOG'.
2013-06-05 11:21:01.16 server    SQL Server is starting at priority class 'normal'(2 CPUs detected).
2013-06-05 11:21:01.92 server    SQL Server configured for thread mode processing.
2013-06-05 11:21:01.92 server    Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
2013-06-05 11:21:02.00 spid2     Starting up database 'master'.
2013-06-05 11:21:02.17 server    Using 'SSNETLIB.DLL' version '8.0.766'.
2013-06-05 11:21:02.17 spid5     Starting up database 'model'.
2013-06-05 11:21:02.22 spid2     Server name is 'SN-FBPKCH1'.
2013-06-05 11:21:02.22 spid2     Skipping startup of clean database id 4
2013-06-05 11:21:02.22 spid2     Skipping startup of clean database id 6
2013-06-05 11:21:02.22 spid2     Starting up database 'secure32dbomegaprotein'.
2013-06-05 11:21:02.71 spid5     Clearing tempdb database.
2013-06-05 11:21:03.05 spid5     Starting up database 'tempdb'.
2013-06-05 11:21:03.21 spid2     Recovery complete.
2013-06-05 11:21:03.21 spid2     SQL global counter collection task is created.
2013-06-05 11:21:03.53 server    SQL server listening on 192.168.100.78: 1433.
2013-06-05 11:21:03.53 server    SQL server listening on 127.0.0.1: 1433.
2013-06-05 11:21:03.60 server    SQL server listening on TCP, Shared Memory, Named Pipes.
2013-06-05 11:21:03.60 server    SQL Server is ready for client connections
2013-06-05 11:21:04.44 spid51    Starting up database 'msdb'.
2013-06-05 11:21:05.19 spid51    Using 'xpsqlbot.dll' version '2000.80.760' to execute extended stored procedure 'xp_qv'.
2013-06-05 11:21:36.68 spid53    Starting up database 'secure32dbomegaprotein'.
2013-06-05 11:21:50.37 spid53    Error: 823, Severity: 24, State: 2
2013-06-05 11:21:50.37 spid53    I/O error (bad page ID) detected during read at offset 0x00000023890000 in file 'C:\Program Files\Microsoft SQL Server\Mssql\Data\MSSQL\Data\\[secure32dbomegaprotein]_DATA.MDF'..
2013-06-05 11:22:43.78 spid53    Starting up database 'secure32dbomegaprotein'.
2013-06-05 11:22:43.90 spid53    Starting up database 'secure32dbomegaprotein'.
2013-06-05 11:26:07.88 spid55    Using 'xpstar.dll' version '2000.80.760' to execute extended stored procedure 'xp_instance_regread'.
2013-06-05 11:27:07.30 spid55    Starting up database 'secure32dbomegaprotein2'.
2013-06-05 11:29:09.13 spid55    Error: 823, Severity: 24, State: 2
2013-06-05 11:29:09.13 spid55    I/O error (bad page ID) detected during read at offset 0x00000023890000 in file 'C:\Program Files\Microsoft SQL Server\Mssql\Data\MSSQL\Data\\[secure32dbomegaprotein]_DATA.MDF'..
2013-06-05 11:45:01.13 spid53    DBCC TRACEON 2562, server process ID (SPID) 53.
2013-06-05 11:45:07.66 spid53    DBCC TRACEON 2549, server process ID (SPID) 53.
2013-06-05 11:46:09.92 spid53    DBCC CHECKDB (secure32dbomegaprotein) executed by OMEGA\fmohiuddin found 22 errors and repaired 0 errors.
2013-06-05 11:56:37.26 spid58    Starting up database 'secure32dbomegaprotein2'.
2013-06-05 11:58:01.98 spid55    Starting up database 'secure32dbomegaprotein2'.
2013-06-05 11:58:19.94 spid55    Starting up database 'secure32dbomegaprotein2'.
2013-06-05 11:58:54.50 spid57    Error: 823, Severity: 24, State: 2
2013-06-05 11:58:54.50 spid57    I/O error (bad page ID) detected during read at offset 0x00000023890000 in file 'C:\Program Files\Microsoft SQL Server\Mssql\Data\MSSQL\Data\\[secure32dbomegaprotein]_DATA.MDF'..
2013-06-05 12:06:11.24 spid55    Error: 823, Severity: 24, State: 2
2013-06-05 12:06:11.24 spid55    I/O error (bad page ID) detected during read at offset 0x00000023890000 in file 'C:\Program Files\Microsoft SQL Server\Mssql\Data\MSSQL\Data\\[secure32dbomegaprotein]_DATA.MDF'..

    Can someone please guide me thru?

    FM

    Wednesday, June 5, 2013 5:17 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    No valid backup? That's bad.

    You could do the following: Run a backup and restore this backup as a new (test) database; then run a DBCC CheckDB with one of the "Repair" options on this new test database to see if it could be fixed by SQL Server. Test very carefully & completely if the problem is fixed and the database is in a well state.

    If this test was successful you could perform the same on your productive database, of course during an "offline" time while no one uses the database.

    And please: Take care about your backups, this is really very important.

    Olaf Helper

    Blog Xing

    • Proposed as answer by Saurabh Sinha DBA Friday, June 7, 2013 3:21 AM
    • Marked as answer by Fanny Liu Tuesday, June 11, 2013 7:37 AM
    Wednesday, June 5, 2013 5:45 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Farhan Your DBCC checkdb has all Index ID=0(heap) showing as cannot read so I assume no clustered index (data) is damaged 

    I would suggest you try

    Use database_name
    GO

    ALTER DATABASE database_name SET SINGLE_USER
    GO

    DBCC CHECKDB('database_name', REPAIR_REBUILD)
    GO

    to return to multi-user mode:
    ALTER <database-name> SET MULTI_USER

    After that run DBCC checkdb again to check if error is fixed

    For finding out the root cause, you would have to check if there were any storage sub-system related errors recently noticed on the server by reviewing the system/application event logs. Also, find out if the drivers and firmware on the box needs any updates. Another thing that can be checked is if your drives have read/write caching enabled.

     backup can be taken but i think it will be difficult for u to restore corrupt database on other server so DBCC checkdb Repair_rebuild

    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

    • Proposed as answer by Saurabh Sinha DBA Friday, June 7, 2013 3:21 AM
    • Marked as answer by Fanny Liu Tuesday, June 11, 2013 7:37 AM
    Wednesday, June 5, 2013 6:06 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello Farhan,

    In short words: Your database is damaged/corrupt. See DBCC CHECKDB (Transact-SQL) => Understanding DBCC Error Messages.

    Have you checked when this error occurred the first time? I hope you have several backups of the database, so that you may can restore the database from the last valid point?

    Olaf Helper

    Blog Xing

    Wednesday, June 5, 2013 5:23 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    >>CHECKDB found 0 allocation errors and 22 consistency errors in database 'secure32dbomegaprotein'.repair_allow_data_loss is the minimum repair level for the errors found by 
    DBCC execution completed  ..................this means there is corruption in ur database. restoring from latest backup will be the best option....Restore Full bkp witn norecovery den  latest diff backup (if ur takin) in win no recovery den tnn backups...I think                                                                                                                           
     I/O error (bad page ID) detected during read at offset 0x00000023890000 in file 'C:\Program Files\Microsoft SQL Server\Mssql\Data\MSSQL\Data\\[secure32dbomegaprotein]_DATA.MDF'..
2013-06-05 12:06:11.24spid55  ...this error shows there is some corruption in ur DB file

    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers


    Wednesday, June 5, 2013 5:24 PM
  • Question
    Sign in to vote
    1
    Sign in to vote
    Some further articles regarding Checkdb and issue solving: http://www.sqlskills.com/blogs/paul/category/checkdb-from-every-angle/

    Olaf Helper

    Blog Xing

    Wednesday, June 5, 2013 5:29 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Olaf,

    This Started Today and I believe we don`t have a restore point available to do from the last valid point.

    Its Sql 2000 version, only reason we have this is to do Check printing with a 3rd party vendor app called Secure32.

    Not sure what to do 

    FM

    Wednesday, June 5, 2013 5:32 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    No valid backup? That's bad.

    You could do the following: Run a backup and restore this backup as a new (test) database; then run a DBCC CheckDB with one of the "Repair" options on this new test database to see if it could be fixed by SQL Server. Test very carefully & completely if the problem is fixed and the database is in a well state.

    If this test was successful you could perform the same on your productive database, of course during an "offline" time while no one uses the database.

    And please: Take care about your backups, this is really very important.

    Olaf Helper

    Blog Xing

    • Proposed as answer by Saurabh Sinha DBA Friday, June 7, 2013 3:21 AM
    • Marked as answer by Fanny Liu Tuesday, June 11, 2013 7:37 AM
    Wednesday, June 5, 2013 5:45 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Farhan Your DBCC checkdb has all Index ID=0(heap) showing as cannot read so I assume no clustered index (data) is damaged 

    I would suggest you try

    Use database_name
    GO

    ALTER DATABASE database_name SET SINGLE_USER
    GO

    DBCC CHECKDB('database_name', REPAIR_REBUILD)
    GO

    to return to multi-user mode:
    ALTER <database-name> SET MULTI_USER

    After that run DBCC checkdb again to check if error is fixed

    For finding out the root cause, you would have to check if there were any storage sub-system related errors recently noticed on the server by reviewing the system/application event logs. Also, find out if the drivers and firmware on the box needs any updates. Another thing that can be checked is if your drives have read/write caching enabled.

     backup can be taken but i think it will be difficult for u to restore corrupt database on other server so DBCC checkdb Repair_rebuild

    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

    • Proposed as answer by Saurabh Sinha DBA Friday, June 7, 2013 3:21 AM
    • Marked as answer by Fanny Liu Tuesday, June 11, 2013 7:37 AM
    Wednesday, June 5, 2013 6:06 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi Olaf, Let me try that and will come back to the thread to report the outcome.

    FM

    Wednesday, June 5, 2013 6:12 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I agree with Shanky, but please: First on a restored test database. And backup your productive database, before you perform any repair action.

    Olaf Helper

    Blog Xing

    Wednesday, June 5, 2013 6:13 PM