November 5, 2015 at 2:30 am
We are migrating SQL Server 2005 database to SQL Server 2012 on VM Server.
The VM Server OS is Windows 2012 R2.
We copied the .bak files to the new VM Server and perform a DB restore.
Disk drive info are as follows:
DriveTotal SizeDrive Purpose
D 50 GBSQL binaries
E 1.3 TBSQL data files/system databases
F 400 GBSQL log files
G 1.2 TBSQL DB backups/ SQL temp data files
VM Server Info
•64 bit
•VM ESX
•OS – Windows 2012 R2
We are able to restore the databases successfully. After wards, we perform our post DB restoration checklist:
•Change DB compatibility level to 110
•run DBCC UPDATEUSAGE
•Update statistics on all tables with full scan
•execute DBCC CHECKDB to check data integrity
•Refresh All views
PROBLEM:
After 5 days since we restore the DB, we suddenly encounter the error Error: 824, Severity: 24, State: 2.
2015-11-02 16:56:07.17 spid62 Error: 3183, Severity: 16, State: 1.
2015-11-02 16:56:07.17 spid62 RESTORE detected an error on page (115:7929965) in database "UENPOAS1" as read from the backup set.
2015-11-02 18:18:34.87 spid61 Error: 824, Severity: 24, State: 2.
2015-11-02 18:18:34.87 spid61 SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:189; actual 1:498). It occurred during a read of page (1:189) in database ID 1 at offset 0x0000000017a000 in file 'E:\Program Files\Microsoft SQL Server\MSSQL11.I02\MSSQL\DATA\master.mdf'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
2015-11-02 18:18:36.46 spid61 Error: 824, Severity: 24, State: 2.
2015-11-02 18:18:36.46 spid61 SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:189; actual 1:498). It occurred during a read of page (1:189) in database ID 1 at offset 0x0000000017a000 in file 'E:\Program Files\Microsoft SQL Server\MSSQL11.I02\MSSQL\DATA\master.mdf'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
2015-11-02 18:18:38.01 spid61 Error: 824, Severity: 24, State: 2.
2015-11-02 18:18:38.01 spid61 SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:189; actual 1:498). It occurred during a read of page (1:189) in database ID 1 at offset 0x0000000017a000 in file 'E:\Program Files\Microsoft SQL Server\MSSQL11.I02\MSSQL\DATA\master.mdf'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
We run the DBCC CHECKDB on the DB and found out that some of them are corrupted (4 out of 7 DB restored suddenly became corrupted)
WHAT COULD BE THE ISSUE?
We told the VM Server admin that this could be a storage issue based on the kb.
https://support.microsoft.com/en-us/kb/2015756.
But they said that they have configured the VM properly and found no issues from storage perspective (but no logs have been showed yet). In other words, VM server admins are pushing this issue to DBA and claims that it could be SQL installation issue. But it cannot be due to SQL installation because the 824 error message usually indicates that there is a problem with underlying storage system or the hardware or a driver that is in the path of the I/O request.
We have uninstalled and re-installed SQL Server 3 times and still get the same error every time.
November 5, 2015 at 4:54 am
Hi
Had a similar problem which was caused by inconstant timings with replication at SAN level.
November 5, 2015 at 8:27 am
Hi Daniel Hughes,
Have you resolved the problem? What did you do?
Thanks
Best Regards,
November 6, 2015 at 9:45 am
Have you guys resolved the problem yet.
November 7, 2015 at 9:25 pm
Hi
No. We haven't. Have you encountered this problem as well?
Best Regards,
October 9, 2017 at 2:33 am
We are planning to do the same upgrade. Has anybody rectified this so we can plan any recommendation in advance?
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply