CODEWITHSUNDEEP
sqlite
Goran
Goran

Reputation: 163

SQLITE file is encrypted or is not a database

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

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

Thanks in advance.

Upvotes: 12

Views: 40358

Answers (6)

Mark Hamstra
Mark Hamstra

Reputation: 722

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;

Upvotes: 1

ulidtko
ulidtko

Reputation: 15560

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.

Upvotes: 17

Heelara
Heelara

Reputation: 979

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.

Upvotes: 1

Goran
Goran

Reputation: 163

Ok, finally found a solution that works so posting the answer if anybody will have same trouble as I did..

First of all, use good recover software. For repairing the database I found 3 solutions that work without backup :

  1. Open corrupted database using DB Browser an Export Database to SQL. Name it however you want. Then, create new database and import database from SQL.
  2. There is software that repairs corrupted databases. Download one and use it to repair the database.

  3. Download "sqlite3" from sqlite.org and in command line navigate to folder where "sqlite3" is unzipped. Then try to dump the entire database with .dump, and use those commands to create a new database:

    sqlite3 corrupt_table_name.sqlite ".dump" | sqlite3 new.sqlite

Upvotes: 4

Rahul Verma
Rahul Verma

Reputation: 684

The issue is with sqlcipher version upgrade in my case, Whenever I update my pod it automatically upgrade the sqlcipher and the error occurred.

For a quick fix just manually add the SDK instead of Pod install. And for a proper solution use this link GitHub Solution

Upvotes: 0

CL.
CL.

Reputation: 180010

Your database did not become encrypted (this is only one of the two options in the error message).

Your data recovery tool did not recover the correct data; what you have in the file is something else.

You have to restore the database file from the backup.

Upvotes: 0

Related Questions