June 22, 2017 at 7:45 pm
Hi,
Below error raised when apply dacpac in sql server16 database
Publishing to database 'SHIPMATETEST' on server '103.231.40.95'.
Initializing deployment (Start)
Initializing deployment (Failed)
*** An error occurred during deployment plan generation. Deployment cannot continue.
Failed to import target model SHIPMATETEST. Detailed message Unable to reconnect
to database: SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0xf3ffe274; actual: 0xf3fff274). It occurred during a read of page (1:10593) in database ID 8 at offset 0x000000052c2000 in file 'D:\WEBDB\LM_SHIPMATETEST8.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.
Pls help
Regards
Binu
June 23, 2017 at 1:53 am
Can you please run the following on the destination database and post the full output?
DBCC CHECKDB WITH NO_INFOMSGS
Do you have any backups of that SHIPMATETEST, or it it an empty database that can be trashed and recreated?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 23, 2017 at 8:31 am
Below message when run DBCC CHECKDB WITH NO_INFOMSGS
Msg 211, Level 23, State 255, Line 3
Corruption in database ID 43, object ID 60 possibly due to schema or catalog inconsistency. Run DBCC CHECKCATALOG.
I tried DBCC CHECKCATALOG
then again above error raised
Error in one of client database with data.
June 26, 2017 at 9:05 am
Hi All,
Any solution for below issue
Detailed message Unable to reconnect
to database: SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0xf3ffe274; actual: 0xf3fff274). It occurred during a read of page (1:10593) in database ID 8 at offset 0x000000052c2000 in file 'D:\WEBDB\LM_SHIPMATETEST8.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.
Regards
Binu
June 26, 2017 at 2:11 pm
GilaMonster - Friday, June 23, 2017 1:53 AMDo you have any backups of that SHIPMATETEST, or it it an empty database that can be trashed and recreated?
???
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply