sql error log multiples errors

  • daniel 73468

    SSC Enthusiast

    Points: 174

    Hi,

    Thursday the 2nd, we replace a disk on our RAID6. Unfortunately, when we powered on the server, we got errors. The back-up would fail.

    We were able to restore & take a back-up on Michelangelo_Data database in SQL, but as for VPP_2006SBO_Data_MICHELANGELO_DATA.mdf, we restored VPP from a succesfull back-up but still cannot back-up the database anymore… 

    dbcc CHECKDB WITH NO_INFOMSGS, ALL_ERRORMSGS

    gives me 

    Msg 8939, Level 16, State 98, Line 2
    Table error: Object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 281474980642816 (type In-row data), page (1:759). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 133129 and -4.
    Msg 8928, Level 16, State 1, Line 2
    Object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 281474980642816 (type In-row data): Page (1:759) could not be processed. See other errors for details.
    Msg 8976, Level 16, State 1, Line 2
    Table error: Object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 281474980642816 (type In-row data). Page (1:759) was not seen in the scan although its parent (1:43) and previous (1:758) refer to it. Check any previous errors.
    Msg 8978, Level 16, State 1, Line 2
    Table error: Object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 281474980642816 (type In-row data). Page (1:777) is missing a reference from previous page (1:759). Possible chain linkage problem.
    CHECKDB found 0 allocation errors and 4 consistency errors in table 'sys.sysobjvalues' (object ID 60).
    CHECKDB found 0 allocation errors and 4 consistency errors in database 'VPP_2006SBO_MICHELANGELO_DATA'.
    repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (VPP_2006SBO_MICHELANGELO_DATA).
    Msg 824, Level 24, State 2, Line 2
    SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x18f080db; actual: 0xcdc9497a). It occurred during a read of page (1:759) in database ID 18 at offset 0x000000005ee000 in file 'E:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Data\VPP_2006SBO_Data_MICHELANGELO_DATA.mdf:MSSQL_DBCC18'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
    Msg 824, Level 24, State 2, Line 2
    SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x18f080db; actual: 0xcdc9497a). It occurred during a read of page (1:759) in database ID 18 at offset 0x000000005ee000 in file 'E:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Data\VPP_2006SBO_Data_MICHELANGELO_DATA.mdf:MSSQL_DBCC18'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
    Msg 824, Level 24, State 2, Line 2
    SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x18f080db; actual: 0xcdc9497a). It occurred during a read of page (1:759) in database ID 18 at offset 0x000000005ee000 in file 'E:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Data\VPP_2006SBO_Data_MICHELANGELO_DATA.mdf:MSSQL_DBCC18'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
    Msg 824, Level 24, State 2, Line 2
    SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x18f080db; actual: 0xcdc9497a). It occurred during a read of page (1:759) in database ID 18 at offset 0x000000005ee000 in file 'E:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Data\VPP_2006SBO_Data_MICHELANGELO_DATA.mdf:MSSQL_DBCC18'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
    Msg 824, Level 24, State 2, Line 2
    SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x18f080db; actual: 0xcdc9497a). It occurred during a read of page (1:759) in database ID 18 at offset 0x000000005ee000 in file 'E:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Data\VPP_2006SBO_Data_MICHELANGELO_DATA.mdf:MSSQL_DBCC18'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.

    What should I do from there ? Thanks.
    Daniel

  • Sue_H

    SSC Guru

    Points: 89727

    daniel 73468 - Monday, March 13, 2017 1:37 PM

    Hi,

    Thursday the 2nd, we replace a disk on our RAID6. Unfortunately, when we powered on the server, we got errors. The back-up would fail.

    We were able to restore & take a back-up on Michelangelo_Data database in SQL, but as for VPP_2006SBO_Data_MICHELANGELO_DATA.mdf, we restored VPP from a succesfull back-up but still cannot back-up the database anymore… 

    If the errors are from the restored database, then it looks like the database was corrupt when the backup ran. I'd look for some older backups and see if those have corruption as well. And keep going back until you find one that isn't corrupt.

    Sue

  • Steve Jones - SSC Editor

    SSC Guru

    Points: 714105

    Sue_H - Tuesday, March 14, 2017 2:32 PM

    If the errors are from the restored database, then it looks like the database was corrupt when the backup ran. I'd look for some older backups and see if those have corruption as well. And keep going back until you find one that isn't corrupt.

    Sue

    Agree with Sue here.

Viewing 3 posts - 1 through 3 (of 3 total)

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