Provisioning sanitized data with SQL Clone and Data Masker. Watch now.

Error Big update in a partitioned table in a Clone Database

DannyDanny Posts: 2 New member
Hello, 

we have create a clone database in a local server and we have tried to do a big update (SSMS) (to test Sql Clone because we just bought it) in a partitioned table and we have this error:

"Msg 824, Level 24, State 2, Line 1
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0xfff0aec3; actual: 0xa20ecd8a). It occurred during a read of page (3:15414) in database ID 23 at offset 0x0000000786c000 in file 'D:\Base Datos\Datos\clones\it_clone_00010002_pbk\VhdMount\Data\IT_Registros_ANTIGUOS.ndf'.  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."

Details:
  • Clone image is hosted in a NAS
  • SQL Server version: 2012 (11.0.5343.0)
  • Database image size: 7.23 gb
  • Database clone size: 725 mb

Answers

  • TheSQLGuruTheSQLGuru Posts: 78 Silver 2
    The obvious question is have you verified that the production database is in fact not corrupted?

    Did you try recreating the clone?

    Do you get the same error if you do the same operation from a different client?
    Kevin G. Boles
    SQL Server MVP 2007-2012
    Indicium Resources, Inc.
  • DannyDanny Posts: 2 New member
    Yes, the backup file is not corrupted.
    We have restored the backup file in SQL Server and work correctly.
    Int he test we use the same backup file to create a SQL Clone image and later create a clone using that image. The error is in the database create using SQL clone image. Thanks!
Sign In or Register to comment.