• Eirikur Eiriksson - Wednesday, July 26, 2017 9:07 AM

    joliveira 19841 - Wednesday, July 26, 2017 8:56 AM

    Eirikur Eiriksson - Wednesday, July 26, 2017 5:12 AM

    Quick thought, looks like either that the update has removed the object with the id of 1106115727 by deleting from the system tables, have you reviewed the "upgrade" script?
    😎
    Have you checked the IO subsystem's health?
    Last time I fixed an error similar to this when the client didn't have any usable backups, I did a side by side installation and then migrated to the new installation by simple detach/attach.

    Hi! Thanks for your reply!

    We don't have access to de script.
    After the error on the upgrade I performed the tests on a backup that I did before the test. The upgrade script is no the guilty :))

    The timeline was like this …

    1) Backup of database
    2) Execute the upgrade script … Aborted with error
    3) Restore the backup in a different server
    4) Execute DBCC CheckDB … Errors were found
    5) Execute DBCC CheckDB (with the option *Repair_rebuild*) … Some errors were corrected, some were not
    6) Perform the upgrade script again … It went ok
    7) Perform DBCC CheckDB again with the “upgraded†database… The check returned the list of errors that I posted before.

    So the error output you posted are the errors after the repair?
    😎

    What about the storage (IO subsystem)? Have you checked the health status there, i.e. SMART,SAN logs etc?

    Yes.
    The error output I posted is from after the repair
    At this stage I'm working with the database at a completely different system/hardware.