Post reply

DBCC Error

  • October 22, 2010 at 1:17 am

    #225311

    Hi, I'm getting this error on a McAfee db ...

    is a restore required or should i go ahead with repair_allow_dataloss???

    Msg 8966, Level 16, State 2, Line 1

    Unable to read and latch page (1:379490) with latch type SH. 23(Data error (cyclic redundancy check).) failed.

    CHECKDB found 0 allocation errors and 1 consistency errors not associated with any single object.

    Msg 2533, Level 16, State 1, Line 1

    Table error: page (1:379490) allocated to object ID 738817694, index ID 1, partition ID 72057594197245952, alloc unit ID 72057594207469568 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.

    Msg 8976, Level 16, State 1, Line 1

    Table error: Object ID 738817694, index ID 1, partition ID 72057594197245952, alloc unit ID 72057594207469568 (type In-row data). Page (1:379490) was not seen in the scan although its parent (1:381963) and previous (1:379489) refer to it. Check any previous errors.

    Msg 8978, Level 16, State 1, Line 1

    Table error: Object ID 738817694, index ID 1, partition ID 72057594197245952, alloc unit ID 72057594207469568 (type In-row data). Page (1:379492) is missing a reference from previous page (1:379490). Possible chain linkage problem.

    CHECKDB found 0 allocation errors and 3 consistency errors in table 'HIP7_IPSEventParameter' (object ID 738817694).

    CHECKDB found 0 allocation errors and 4 consistency errors in database 'ePO4_SERVER'.

    repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (ePO4_SERVER).

    MCITP: Database Administrator 2005
    MCTS SQL Server 2008
    MCP SQL 2012/2014
    MCSA SQL Server 2012/2014
    MCSE Data Management and Analytics

  • October 22, 2010 at 1:42 am

    #1240744

    issue with a user table ...

    SELECT name, type_desc FROM sys.objects

    WHERE object_id IN (738817694) returned HIP7_IPSEventParameterUSER_TABLE

    MCITP: Database Administrator 2005
    MCTS SQL Server 2008
    MCP SQL 2012/2014
    MCSA SQL Server 2012/2014
    MCSE Data Management and Analytics

  • October 22, 2010 at 1:53 am

    #1240748

    If you do repair_allow_data_loss you will lose data from that table as the page is from the leaf level of the clustered index. I would recommend restoring using your backups if that will result in less data loss.

    You also need to investigate the integrity of your IO subsystem as the CRC error is caused by the IO subsystem - and it will likely happen again.

    Thanks

    Paul Randal
    CEO, SQLskills.com: Check out SQLskills online training!
    Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
    SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
    Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005

  • October 22, 2010 at 2:09 am

    #1240751

    thanks Paul 😀 will check on what backups are available and find out if they want a restore or accept the dataloss ...

    MCITP: Database Administrator 2005
    MCTS SQL Server 2008
    MCP SQL 2012/2014
    MCSA SQL Server 2012/2014
    MCSE Data Management and Analytics

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

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