RESTORE DATABASE is terminating abnormally

  • Hi all,

    I need some help on below error.

    RESTORE DATABASE is terminating abnormally.

    Msg 211, Level 23, State 46, Line 2 Possible schema corruption. Run DBCC CHECKCATALOG.

    Backed up SQL server 2000 database by using stripe backup concept.

    Needs to restore in SQL server 2005.

    Able to restore the full backup with no recover option.

    I am getting the above error while restoring differential data(There are 3 files).

    All backup files are vaild.

    Following is SQL server error log.

    =============================================

    2009-03-13 05:20:12.34 spid52 External dump process return code 0x20000001.

    External dump process returned no errors.

    2009-03-13 05:20:12.34 spid52 Error: 928, Severity: 20, State: 1.

    2009-03-13 05:20:12.34 spid52 During upgrade, database raised exception 211, severity 23, state 46, address 019C60EE. Use the exception number to determine the cause.

    2009-03-13 05:20:12.34 spid52 Error: 211, Severity: 23, State: 46.

    2009-03-13 05:20:12.34 spid52 Possible schema corruption. Run DBCC CHECKCATALOG.

    =============================================

    The help would be very helpful to me.

    Thanks in advance,

  • On the SQL 2000 database, please run the following and post the full output

    DBCC CHECKDB (< Database Name > ) WITH NO_INFOMSGS, ALL_ERRORMSGS

    DBCC CHECKCATALOG (< Database Name > ) WITH NO_INFOMSGS, ALL_ERRORMSGS

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • When ran DBCC CHECKDB there was no error messages.

    But when ran DBCC CHECKCATALOG reported the following error.

    Server: Msg 2513, Level 16, State 5, Line 1

    Table error: Object ID 1412200081 (object 'DF_INTERNET_EMAILS_LAST_MOD_DATE') does not match between 'SYSOBJECTS' and 'SYSCOMMENTS'.

    Any idea, how to fix the above problem?

    Thank you so much for the assistance.

    Regards,

  • Dropped and re-created the default constraint for the table and ran the CHECKCATALOG command successfully.

    Taken the backup and restoring the db.

    Hope this will work fine.

    Thanks a lot for all the help.

    Regards,

  • Bagath (3/16/2009)


    Dropped and re-created the default constraint for the table and ran the CHECKCATALOG command successfully.

    Yup, that is the way to fix schema-related errors like that. If CheckCatalog is clean, you should be able to restore without difficulty.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • Just FYI,

    Restore database was successful after fix.

    Thank you so much once again.

    Regards,

Viewing 6 posts - 1 through 5 (of 5 total)

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