Início / dba / Perguntas / 87169
Accepted
Chris Woods
Asked: 2014-12-30 06:55:33 +0800 CST

Orig DB = Sem Corrupção, Backup/restauração = Corrupção?

  • 772

Estamos configurando checkdbs DBCC offline em um servidor offline para que possamos fazer nossas verificações, mas não interferir na produção.

Quando fazemos backup do banco de dados mestre e o restauramos (mesmo diretamente em um SSD local na mesma máquina de produção), obtemos 36 erros de corrupção quando DBCC CHECKDB o banco de dados restaurado (master_restore).

Mas quando eu DBCC CHECKDB o banco de dados mestre original, não recebo erros. Qualquer ideia?

Check Catalog Msg 3851, State 1: An invalid row (class=12,depid=0,depsubid=0) was found in the system table sys.syssingleobjrefs (class=12).
Check Catalog Msg 3851, State 1: An invalid row (class=13,depid=1,depsubid=0) was found in the system table sys.syssingleobjrefs (class=13).
Check Catalog Msg 3851, State 1: An invalid row (class=60,depid=1,depsubid=0) was found in the system table sys.syssingleobjrefs (class=60).
Check Catalog Msg 3851, State 1: An invalid row (class=26,depid=1,depsubid=0,indepid=3,indepsubid=0) was found in the system table sys.sysmultiobjrefs (class=26).
Check Catalog Msg 3851, State 1: An invalid row (class=13,depid=2,depsubid=0) was found in the system table sys.syssingleobjrefs (class=13).
Check Catalog Msg 3851, State 1: An invalid row (class=60,depid=2,depsubid=0) was found in the system table sys.syssingleobjrefs (class=60).
Check Catalog Msg 3851, State 1: An invalid row (class=60,depid=3,depsubid=0) was found in the system table sys.syssingleobjrefs (class=60).
Check Catalog Msg 3851, State 1: An invalid row (class=60,depid=4,depsubid=0) was found in the system table sys.syssingleobjrefs (class=60).
Check Catalog Msg 3851, State 1: An invalid row (class=60,depid=5,depsubid=0) was found in the system table sys.syssingleobjrefs (class=60).
Check Catalog Msg 3851, State 1: An invalid row (class=26,depid=261,depsubid=0,indepid=3,indepsubid=0) was found in the system table sys.sysmultiobjrefs (class=26).
Check Catalog Msg 3851, State 1: An invalid row (class=26,depid=262,depsubid=0,indepid=3,indepsubid=0) was found in the system table sys.sysmultiobjrefs (class=26).
Check Catalog Msg 3851, State 1: An invalid row (class=26,depid=263,depsubid=0,indepid=3,indepsubid=0) was found in the system table sys.sysmultiobjrefs (class=26).
Check Catalog Msg 3851, State 1: An invalid row (class=26,depid=264,depsubid=0,indepid=3,indepsubid=0) was found in the system table sys.sysmultiobjrefs (class=26).
Check Catalog Msg 3851, State 1: An invalid row (class=26,depid=266,depsubid=0,indepid=3,indepsubid=0) was found in the system table sys.sysmultiobjrefs (class=26).
Check Catalog Msg 3851, State 1: An invalid row (class=26,depid=268,depsubid=0,indepid=3,indepsubid=0) was found in the system table sys.sysmultiobjrefs (class=26).
Check Catalog Msg 3851, State 1: An invalid row (class=26,depid=269,depsubid=0,indepid=9,indepsubid=0) was found in the system table sys.sysmultiobjrefs (class=26).
Check Catalog Msg 3851, State 1: An invalid row (class=26,depid=269,depsubid=0,indepid=10,indepsubid=0) was found in the system table sys.sysmultiobjrefs (class=26).
Check Catalog Msg 3851, State 1: An invalid row (class=26,depid=273,depsubid=0,indepid=3,indepsubid=0) was found in the system table sys.sysmultiobjrefs (class=26).
Check Catalog Msg 3851, State 1: An invalid row (class=26,depid=274,depsubid=0,indepid=3,indepsubid=0) was found in the system table sys.sysmultiobjrefs (class=26).
Check Catalog Msg 3851, State 1: An invalid row (class=26,depid=277,depsubid=0,indepid=3,indepsubid=0) was found in the system table sys.sysmultiobjrefs (class=26).
Check Catalog Msg 3851, State 1: An invalid row (class=26,depid=278,depsubid=0,indepid=3,indepsubid=0) was found in the system table sys.sysmultiobjrefs (class=26).
Check Catalog Msg 3851, State 1: An invalid row (class=26,depid=279,depsubid=0,indepid=3,indepsubid=0) was found in the system table sys.sysmultiobjrefs (class=26).
Check Catalog Msg 3851, State 1: An invalid row (class=26,depid=280,depsubid=0,indepid=3,indepsubid=0) was found in the system table sys.sysmultiobjrefs (class=26).
Check Catalog Msg 3851, State 1: An invalid row (class=26,depid=283,depsubid=0,indepid=3,indepsubid=0) was found in the system table sys.sysmultiobjrefs (class=26).
Check Catalog Msg 3851, State 1: An invalid row (class=76,depid=65536,depsubid=101) was found in the system table sys.syssingleobjrefs (class=76).
Check Catalog Msg 3851, State 1: An invalid row (class=76,depid=65536,depsubid=103) was found in the system table sys.syssingleobjrefs (class=76).
Check Catalog Msg 3851, State 1: An invalid row (class=76,depid=65536,depsubid=104) was found in the system table sys.syssingleobjrefs (class=76).
Check Catalog Msg 3851, State 1: An invalid row (class=76,depid=65536,depsubid=105) was found in the system table sys.syssingleobjrefs (class=76).
Check Catalog Msg 3851, State 1: An invalid row (class=76,depid=65536,depsubid=107) was found in the system table sys.syssingleobjrefs (class=76).
Check Catalog Msg 3851, State 1: An invalid row (class=76,depid=65537,depsubid=101) was found in the system table sys.syssingleobjrefs (class=76).
Check Catalog Msg 3851, State 1: An invalid row (class=76,depid=65537,depsubid=103) was found in the system table sys.syssingleobjrefs (class=76).
Check Catalog Msg 3851, State 1: An invalid row (class=76,depid=65537,depsubid=107) was found in the system table sys.syssingleobjrefs (class=76).
CHECKDB found 0 allocation errors and 32 consistency errors not associated with any single object.
Page (1:10) in database ID 13 is allocated in the SGAM (1:3) and PFS (1:1), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED   0_PCT_FULL'.
CHECKDB found 1 allocation errors and 0 consistency errors in table '(Object ID 99)' (object ID 99).
CHECKDB found 1 allocation errors and 32 consistency errors in database 'master_restore'
sql-server restore

1 respostas

  1. Best Answer

    O banco de dados mestre é um caso especial. Você notará que a corrupção está na página 10, que é a página de configuração. Isso está aparecendo como corrompido porque faltam dados quando restaurado como um banco de dados do usuário, em vez de um banco de dados mestre para uma instância.

    Paul Randal escreveu um post sobre isso http://sqlmag.com/blog/my-master-database-really-corrupt

    • 2

relate perguntas