Post reply

Chain linkage mismatch.

  • June 18, 2004 at 11:24 am

    #102071

    I'm getting repeated errors refering to a Chain linkage mismatch. Also I seeing repeated logon failures to that database.  Can anyone shed some light as to what is occuring and what the best course of action might be.

    Thanks

     

  • June 18, 2004 at 11:44 am

    #511091

    Can you give more details ? Do you mean you are getting errors with cross database ownership ?

  • June 18, 2004 at 12:30 pm

    #511102

    i'm getting Error: 8908, Severity: 22, State: 6 in my MOM database.  I have not had any hardware failures that know of.  I don't think this has anything to do with cross database ownership.

  • June 22, 2004 at 5:58 am

    #511388

    Hi Gary,

    This is the information given in BOL

    Error 8908

      Topic last updated -- January 2004

    Severity Level 16
    Message Text

    Table error: Database Id DB_ID, object Id O_ID, index Id I_ID. Chain linkage mismatch. P_ID1->next = P_ID2, but P_ID2->prev = P_ID3.

    Explanation

    The first phase of a DBCC CHECKDB is to do primitive checks on the data pages of critical system tables. If any errors are found, they cannot be repaired, so the DBCC CHECKDB terminates immediately.

    This error means that the next page pointer of page P_ID1 points to page P_ID2, but the prev page pointer of page P_ID2 points to page P_ID3—not back to page P_ID1 as it should.

    Action

    HARDWARE FAILURE

    Run hardware diagnostics and correct any problems. Also examine the Microsoft® Windows NT® system and application logs and the SQL Server™ error log to see if the error occurred as the result of hardware failure. Fix any hardware related problems.

    If you have persistent data corruption problems, try to swap out different hardware components to isolate the problem. Check to ensure that your system does not have write caching enabled on the disk controller. If you suspect this to be the problem, contact your hardware vendor.

    Finally, you might find it beneficial to switch to a completely new hardware system, including reformatting the disk drives and reinstalling the operating system.

    RESTORE FROM BACKUP

    If the problem is not hardware related and a known clean backup is available, restore the database from the backup. 

    DBCC CHECKDB

    If no clean backup is available, execute DBCC CHECKDB without a repair clause to determine the extent of the corruption. DBCC CHECKDB will recommend a repair clause to use. Then, execute DBCC CHECKDB with the appropriate repair clause to repair the corruption.

    Caution  If you are unsure what effect DBCC CHECKDB with a repair clause has on your data, contact your primary support provider before executing this statement.

    This error cannot be repaired automatically.

    Hope it might be helpful...


    Lucky

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

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