November 28, 2017 at 10:24 am
Hi,
I got a strange problem, I am moving DBs from old test server(SQL Server 2008 R2 SP2) to new test server (SQL Server 2016 SP1-CU5), whereas no DB errors, found when I am running DBCC CHECKDB(Mydb) WITH PHYSICAL_ONLY, but after backup and restore the same DB got so many errors while running DBCC CHECKDB(mydb) WITH PHYSICAL_ONLY.
Please help me.
Thanks,
Venkata
November 28, 2017 at 11:56 am
Sounds like the backup may have been corrupted. Try restoring it to a different server. If it fails there too, that's the problem. You'll need a new backup. If it succeeds there, you may have a problem with the server.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
November 28, 2017 at 9:44 pm
mssqlchat - Tuesday, November 28, 2017 10:24 AMHi,I got a strange problem, I am moving DBs from old test server(SQL Server 2008 R2 SP2) to new test server (SQL Server 2016 SP1-CU5), whereas no DB errors, found when I am running DBCC CHECKDB(Mydb) WITH PHYSICAL_ONLY, but after backup and restore the same DB got so many errors while running DBCC CHECKDB(mydb) WITH PHYSICAL_ONLY.
Please help me.
Thanks,
Venkata
Can you post the errors?.
Regards
Durai Nagarajan
November 29, 2017 at 3:51 am
Hi Durai,
There are more than 100 errors, so I am giving few below.
Msg 8939, Level 16, State 5, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 101332025764413440 (type Unknown), page (1:15779857). Test (hdr->m_headerVersion == Page::HEADER_7_0) failed. Values are 46 and 1.
Msg 8939, Level 16, State 53, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 101332025764413440 (type Unknown), page (1:15779857). Test (PageComprInfo::FValidOffsetMapIndex (page->GetCompressionInfo ())) failed. Values are -1 and -1.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 91479429642452992 (type Unknown), page (1:949274). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 133129 and -1.
CHECKDB found 0 allocation errors and 3 consistency errors not associated with any single object.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 14779260, index ID 0, partition ID 72057594047299584, alloc unit ID 72057597021847552 (type In-row data), page (1:549835). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 133129 and -1.
Msg 8928, Level 16, State 1, Line 1
Object ID 14779260, index ID 0, partition ID 72057594047299584, alloc unit ID 72057597021847552 (type In-row data): Page (1:549835) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 14779260, index ID 0, partition ID 72057594047299584, alloc unit ID 72057597021847552 (type In-row data), page (1:5389895). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 133129 and -1.
Msg 8928, Level 16, State 1, Line 1
Object ID 14779260, index ID 0, partition ID 72057594047299584, alloc unit ID 72057597021847552 (type In-row data): Page (1:5389895) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 14779260, index ID 7, partition ID 72057610558767104, alloc unit ID 72057612685148160 (type In-row data), page (1:12310465). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 133129 and -1.
Msg 8928, Level 16, State 1, Line 1
Thanks,
Venkata
November 29, 2017 at 4:35 am
What is the db compability level
Regards
Durai Nagarajan
November 29, 2017 at 4:42 am
durai nagarajan - Wednesday, November 29, 2017 4:35 AMWhat is the db compability level
SQL Server 2016(130)
November 29, 2017 at 5:55 am
mssqlchat - Wednesday, November 29, 2017 4:42 AMdurai nagarajan - Wednesday, November 29, 2017 4:35 AMWhat is the db compability levelSQL Server 2016(130)
Can you change the compatibility level to old one and check once?
Regards
Durai Nagarajan
November 29, 2017 at 6:03 am
Grant Fritchey - Tuesday, November 28, 2017 11:56 AMSounds like the backup may have been corrupted. Try restoring it to a different server. If it fails there too, that's the problem. You'll need a new backup. If it succeeds there, you may have a problem with the server.
Thanks Guru,
Yes, running new backup and restore solved my problem. Yesterday corrupted backup file got 94 GB file size today good backup file size is 19 GB. I don't know why.
Venkata
November 29, 2017 at 6:42 am
durai nagarajan - Wednesday, November 29, 2017 5:55 AMmssqlchat - Wednesday, November 29, 2017 4:42 AMdurai nagarajan - Wednesday, November 29, 2017 4:35 AMWhat is the db compability levelSQL Server 2016(130)
Can you change the compatibility level to old one and check once?
How would the compatibility level create or remove corruption?
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
November 29, 2017 at 6:44 am
mssqlchat - Wednesday, November 29, 2017 6:03 AMGrant Fritchey - Tuesday, November 28, 2017 11:56 AMSounds like the backup may have been corrupted. Try restoring it to a different server. If it fails there too, that's the problem. You'll need a new backup. If it succeeds there, you may have a problem with the server.Thanks Guru,
Yes, running new backup and restore solved my problem. Yesterday corrupted backup file got 94 GB file size today good backup file size is 19 GB. I don't know why.
Venkata
Good to know. Thanks for sharing.
I couldn't tell you why it went wrong. Disk drive, controller, network, any of the above or in combination.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply