An Internal Consistency Error Occurred. Contact Technical Support For Assistance
16, 20100 0 0 0 Here is one of the corruption issue that i came across on the database which was dettached after entering into suspect mode making it difficult to re-use the mdf and ldf file.Even the database backup they had was taken from SQL 7.0 instance which had corruption. This backup was taken post the database was corrupt.Below im sharing the information on all the steps that I tried and finally getting the backup work with minimal data loss. Failing to restore SQL Server database backup with internal consistency error. ERROR======5 percent restored.10 percent restored.15 percent restored.Server: Msg 3270, Level 16, State 1, Line 1An internal consistency error occurred. Contact Technical Support for assistance.Server: Msg 3013, Level 16, State 1, Line 1RESTORE DATABASE is terminating abnormally. Troubleshooting===============-- Customer had SQL 7 backup and trying to restore the database and failing to restore and giving some internal consistecny error.-- It passes all the checks (Verify Header and Filelistonly) however when trying to restore.-- CU do not have the DB anymore in production.-- They have mdf and ldf but they were dettached after the database went into suspect mode. -- Ran Restore headeronly from disk = backup file name, this came with below output. BackupName BackupType ExpirationDate Compressed Position DeviceType UserName ServerName DatabaseName DatabaseVersion DatabaseCreationDate BackupSize ---------- ------- ------------ ------- ----- ------- ----------------- --------- ----------- ---------- ----------------------- --------------- NULL 1 NULL 0 1 2
SQL Server experts to answer whatever question you can come up with. Our new SQL Server Forums are live! Come on over! We've restricted the ability to create new threads on these forums. SQL Server Forums Profile | ActiveTopics | Members | Search | ForumFAQ Register Now and get your question answered! Username: Password: Save Password Forgot your Password? All Forums General SQL Server Forums Data Corruption Issues Internal Consistency Error Reply to Topic Printer Friendly Author Topic MBeal https://blogs.msdn.microsoft.com/venkn/2010/03/16/failing-to-restore-sql-server-database-backup-with-internal-consistency-error/ Posting Yak Master 110 Posts Posted-02/13/2007: 16:43:13 I have been running log shipping for more than a year now and it has been very successful until just recently. For some reason the SQL Agent jobs that backup the database, ship it across the network to a standby server and restore it are failing. On the source server the backup http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=79103 process is running, the log shipping is running however when it tries to restore it on the destination server it fails with the following error:SQL Server Help file: Help context: 0 Error Detail Records: Error: -2147217900 (80040E14); Provider Error: 3013 (BC5) Error string: RESTORE DATABASE is terminating abnormally. Error source: Microsoft OLE DB Provider for SQL Server Help file: Help context: 0 Error: -2147217900 (80040E14); Provider Error: 3270 (CC6) Error string: An internal consistency error occurred. Contact Technical Support for assistance. Error source: Microsoft OLE DB Provider for SQL Server Help file: Help context: 0 Error: 0 (0); Provider Error: 3211 (C8B) Error string: 10 percent restored. Error source: Microsoft OLE DB Prov... Process Exit Code 1. The step failed.If I delete the database on the destination server, re-run the sql agent job that ships the backup job, and re-run the restore job on the destination server the process will succeed without error. This tells me the original backup was fine but something may have been lost during the shipping. Have you ever seen this message before? What does it
Join INTELLIGENT WORK FORUMSFOR COMPUTER PROFESSIONALS Log In Come Join Us! Are you aComputer / IT professional?Join Tek-Tips Forums! Talk With Other Members Be Notified Of ResponsesTo Your Posts Keyword Search One-Click Access To YourFavorite http://www.tek-tips.com/viewthread.cfm?qid=772831 Forums Automated SignaturesOn Your Posts Best Of All, It's Free! Join Us! *Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail. Posting Guidelines Promoting, selling, recruiting, coursework and thesis posting is forbidden.Tek-Tips Posting Policies Jobs Jobs from Indeed What: Where: jobs by Link To This Forum! Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.Just copy and paste the an internal BBCode HTML Markdown MediaWiki reStructuredText code below into your site. CA: ARCserve back-up Forum at Tek-Tips HomeForumsServer RackBack-up SystemsCA: ARCserve back-up Forum restore of SQL DB failes :-( in B9 2 thread478-772831 Forum Search FAQs Links MVPs restore of SQL DB failes :-( in B9 restore of SQL DB failes :-( in B9 Padzik (TechnicalUser) (OP) 11 Feb 04 05:45 PLEASE HELP - Brightstor9, SQL2000 serverHi, I found an internal consistency out, that I cannot restore only SQL DB, that is more than eg. 50 MB or bigger. When I want to restore any of "small" SQL DB from ANY media, it is not problem but when the DB is "big" (more than eg. 50 MB), I got these errors: (This is not a media error, all backups are finished; we tried to change the tapes)E6300 WinNT SCSI port error - we tried the advices in FAQ here, but it didn't help us. We even replaced the SCSI controller for another type!E3713 Unable to read from media. EC=controller failure or HW errorE8617 Failed to end restore. (DBname=mis EC=server:[SQL Server] szSqlState = 37000,fNativeError =3270, errMsg=[Microsoft] [ODBC SQL Server Driver] [SQL Server] An internal consistency eror occured. Contact T. Support for assistance.But when I look into the dbasql.log on the server I want to restore the db, there are these lines, from I think, the data are written OK, but is here any problem with SQL agent???? I deleted the time symbols from log to make it easier to read...Database MIS in Restore Modeget_dumpload_unit(): Got BackupId = 0 forNEW TAPE FORMAT. sqlTapeSignature = 1, nStripes = 1,nVdiStripes_Restore = 1DSABeginRestore(): OKrestore database [MIS] from virtual_device = 'DBASQL_DB_MIS_PID2936TID5808BID0TS446694312VD0' WITH RECOVERY , BLOCKSIZE=6553