SQLITE file is encrypted or is not a database

user_5537045 0
Viewed 32673

I have a huge problem... I am developing desktop app with SQLite but during copy/paste process I lost a power and process was terminated so base was lost. However, I found a way to recover it but base is encrypted. When I try to open connection using conn.Open(); I get this error. If I try to open it with DB Browser for SQLite it asks me a SQLCipher encryption password so it seams to me that data is lost..

Is there any default password ? Why did this happen and how to prevent it from happening again ? What can I do ?

Thanks in advance.

sqlite
6 Answers

Also check that SQLite version you're "connecting" with aligns with the DB file version.

For example, here's a DB file written by SQLite version 3+:

$ file foobar.db 
foobar.db: SQLite 3.x database, last written using SQLite version 3027002

And here I also have 2 versions of sqlite:

$ sqlite -version
2.8.17
$ sqlite3 -version
3.27.2 2019-02-25 16:06:06 bd49a8271d650fa89e446b42e513b595a717b9212c91dd384aab871fc1d0alt1

Obviously in hindsight, opening foobar.db with sqlite version 2 will fail, yielding the same error message:

$ sqlite foobar.db 
Unable to open database "foobar.db": file is encrypted or is not a database

But all is good with the correct version:

$ sqlite3 foobar.db
SQLite version 3.27.2 2019-02-25 16:06:06
Enter ".help" for usage hints.
sqlite> 
sqlite> .databases 
main: /tmp/foobar.db
sqlite>

The error message is a catch-all, simply meaning that the file format was not recognized.

user_5311790

I had the same error when I was trying to access a db dump in another system compared to compared to where it was obtained. When I tried to open on a dev machine, it threw the reported error in this thread:

$ sqlite3 db_dump.sqlite .tables
Error: file is encrypted or is not a database

This turned out to be due to the differences in the sqlite version between those systems. This dev system version was 3.6.20.

The version on the production system was 3.8.9. Once I had the sqlite3 upgraded to same version, I was able to access all its data. I am just showing below the tables are displayed as expected:

# sqlite3 -version
3.8.9
# sqlite3 db_dump.sqlite .tables
capture               diskio                transport     
consumer              filters               processes

This error is rather misleading to begin with, though.

user_28861580

If you've interacted with the database at some point while specifying journal_mode = WAL, and then later try to use the database from a client that does not support WAL (< v3.7.0), this error can also come up.

As noted in the SQLite documentation under Backwards Compatibility, to resolve that without having to recreate the database, explicitly set the journal mode to DELETE:

PRAGMA journal_mode=DELETE;
user_12773450
Related