SQL3 File Repair

[MasterT]

Hi guys,

I have a recovery case. Customer is interested in a database file which is a backup of a software data.

I recovered the file, all sectors read ok. I tried to open file with different software online and offline but all say that "database disk image is malformed". So file is corrupt.

Any of you have knowledge about how can i repair the file so the customer can use it to import data back into his software?

If you had this case before and had success with any commercial tool let me know.

Thank you.

[einstein9]

can you post the file header here? and how big is the file?

[MasterT]

Here it is:

Attachments

[MasterT]

I tried with command lines:

sqlite3 broken.db ".dump" | sqlite3 new.db - gives error

sqlite3 broken.db ".recover" | sqlite3 new.db - works without error but generated file is not recognized by the application.

[einstein9]

SQL lite header looks OK, most probably can be fixed ,,, some of the contents (records) will be lost
process is manually performed..

most probably due to bad sectors..

How big is the Original DB file? and the backup file you recovered?

[MasterT]

Broken file has 6,41 MB (6.726.656 bytes)
Recovered file has 6,64 MB (6.971.392 bytes)

The problem was solved after all. Recovered file looks ok. I don't know however, how can i check what records are missing.

Initially data could not import because an additional configuration file was necessary next to the db.

[einstein9]

In my opinion here (depends on the bads location) the Diff. in size "Makes a big Diff" <<---- Not little to ignore
just image how much data (records) you can have in 200k, some DBs are compressed some are not (depends on the designer and how Pro. is the programmer)

after all, we can go through the guesses and continue list possibilities

To cut it short (if you are interested) such a repair case for us here costs 300-500$ (will quote after looking @the DB file with some more info. required about the App. used)

PM if this works with you here

and all the best

[MasterT]

Recovered file has bigger size because there are some 00 00 inserts in a few places.

Also there are some changes in the header also.

Untitled.png (11.47 KiB) Viewed 29893 times

Original recovered file from the customer drive had no bad sector at the time of reading it. I can guess there was a bad sector in the past that got relocated, but original data was not read totally right, or maybe some other kind of corruption.

Thank you for the quote einstein9. In case needed I know who can help.

[einstein9]

All the best :>