An internal consistency error occurred.

Question

An internal consistency error occurred.

CooLDBA

Hall of Fame

Points: 3301
More actions
March 11, 2005 at 4:26 pm

#113475

RESTORE DATABASE is terminating abnormally. [SQLSTATE 42000] (Error 3013) An internal consistency error occurred. Contact Technical Support for assistance. [SQLSTATE 42000] (Error 3270). The step failed.
Any idea what's this?

Viewing 15 posts - 1 through 15 (of 20 total)

You must be logged in to reply to this topic. Login to reply

Rich James Default port Points: 1484 More actions · Answer 1

Are you trying to restore a backup taken from that server, and that database, or are you trying to move it from one server to another?

CooLDBA Hall of Fame Points: 3301 More actions · Answer 2

Restore a backup taken from that server and that database...

Kishore-132325 Hall of Fame Points: 3784 More actions · Answer 3

Try using :

RESTORE VERIFYONLY FROM < backup_device > [ ,...n ]

This only checks the backup to see if the backup file you have is complete.

--Kishore

Terry Denney SSC Journeyman Points: 97 More actions · Answer 4

I am having the same problem. I have a database that I received from a customer and I get the same error during a restore.

Could the backup file that I am trying to restore corrupt?

Terry

Brij Singh SSC Journeyman Points: 89 More actions · Answer 5

I have taken backup of database using windows 2000 server and now I am restoring database on windows 2003 server machine, I have also installed service pack 3a but i am getting error "sqlstate: 42000 An internal consistency error occured. resote database is terminating abnormally.

Please help

Jason Hall Hall of Fame Points: 3906 More actions · Answer 6

This is typically due to either a corrupted backup file or some bad hardware that the backup file sits on. Try and move the backup file to a different disk (local would be ideal) and restore from that location. Other than that you will most likely need to take another backup.

Vladimir Sim Ten Centuries Points: 1310 More actions · Answer 7

Hi,

I also facing the same problem of having 'internal consistency error occurred. MS SQL-DMO(ODBC Sqlstate:42000)'

Using 'RESTORE VERIFY ONLY' command show that my backup file is okay.

I am trying to restore from backup file from another Window 2003 server (standard)

to my development system (Window 2000 XP Professional, with SP2).

So, does it mean that my backup file is corrupted, any other ways for me to

01) prevent similar issue again

02) check that my future backup file is okay.

I need to prevent similar problem from happening again.

Thank you

Daylinda-241205 SSC Journeyman Points: 85 More actions · Answer 8

I got the same error msg

An internal consistency error occurred. Contact Technical Support for assistance. [SQLSTATE 42000] (Error 3270) RESTORE DATABASE is terminating abnormally. [SQLSTATE 42000] (Error 3013). The step failed.

I have searched the MS KB and this is the only article I found but was not useful for us..thought it might help.

http://support.microsoft.com/default.aspx?scid=kb;en-us;268481

Has anyone logged a PSS support for this error?

Daylinda

Höbenreich SSC Journeyman Points: 79 More actions · Answer 9

Hi,

i got a BAK File from an customer with SQL Server 2000, based on a Windows2003 Server. After a verify i`m sure, BAK File is not BAK file!

I do only have an W2K Server, also SQL and therfore i got the same error!

It looks like that the BAK File from 2003 Server is different to W2K Server.

I have no solution, the onlyst thing is, i try to find something to convert this BAK-Format!

//Martin

Vladimir Sim Ten Centuries Points: 1310 More actions · Answer 10

Hi Martin,

Sorry to heard about your BAK file problem.

01) In your case, we might have to ensure what software your customer

use to create the BAK file for you ? Is your customer using the

SQL server to create the backup file or other software ?

02) If your customer is truly using SQL Server to create it, then I afraid

your bak file is corrupted. I faced similar issue before. There don't seem

to be any reliable way to check whether the backup file created is okay unless

we get some third-party tool that have this feature.

Hope the above will help you out.

Jason Hall Hall of Fame Points: 3906 More actions · Answer 11

Quest software has a product called LiteSpeed that may be able to help with corrupted backup files. This product has a feature called Object Level Recovery that allows you to extract individual objects out of a full backup file. In the case of a corrupted backup, usually only 1% or less of the file is bad so we should be able to recover 99% of the data. If you need individual table data/schema's, stored procs, vies, UDF's, or UDT's Litespeed should be able to help you out. I've tested this out against files that could not be restored from and had very good success in extracting individual tables.

For more info:

http://www.quest.com/news/show.aspx?ContentID=2539&ContentTypeID=2

shekhar-328994 SSC Rookie Points: 31 More actions · Answer 12

This error comes because of the mismatch with the files that are there in the database and files that are there in the backup set. So use

"with Replace" option with the restore command and if you are trying to restore the database with Enterprise manager then select overright option on option tab while.

Thanks & regards

chander shekhar

SQL ORACLE One Orange Chip Points: 27807 More actions · Answer 13

Corruption of the backup file is one of possible reasons. I got the same error once restoring a database. I pinned the error was the corruption of the backup file eventually.

paul_mighty Grasshopper Points: 21 More actions · Answer 14

Are there any tool that cal be used to fix the db file