File is not a database ошибка - Не ошибается лишь тот, кто ничего не делает!

I have created a database named database.db

When I create a table in the database I get the error:Error: file is not a database

nehal@nehal-Inspiron-5559:~/Desktop/UAV$ sqlite3 database.db 
SQLite version 3.20.1 2017-08-24 16:21:36
Enter ".help" for usage hints.
sqlite> CREATE TABLE users(
   ...> password varchar(10),
   ...> email text,
   ...> name text
   ...> );
Error: file is not a database

How do I resolve the error?

asked Feb 25, 2018 at 13:44

Create database without the .db extension.

for e.g. sqlite3 users //this creates a database names users

answered Feb 25, 2018 at 16:58

user7441user7441

4012 gold badges5 silver badges11 bronze badges

The error can occur when a database was created with cipher.
So sqlite3_open succeded but any sqlite3_exec or sqlite3_prepare will be failed with this error.

answered Feb 2, 2021 at 0:00

Aikon MogwaiAikon Mogwai

4,8642 gold badges18 silver badges30 bronze badges

You can also use

.open users

it will also create the database

and to open an existing database users.db use

.open users.db

if .db is not used new database of same name will be created

answered Nov 10, 2019 at 5:45

DevanshuDevanshu

87310 silver badges22 bronze badges

Same problem with WPF and SQLiteAdministrator creating a SQLite v3 DB with Database->New->SQLite 3 DB option and «Data Source=whatever.s3db; Version=3» in the WPF code using System.Data.SQLite library.

Select Database->Migrate to SQLite3 option in SQLiteAdministrator solves the problem. Its works for me. I hope this helps someone.

answered Mar 29, 2022 at 15:10

Источник

Comments

justinclift

added
the

bug

Confirmed bugs or reports that are very likely to be bugs.

label

Mar 23, 2019

MKleusberg

added a commit
that referenced
this issue

Mar 25, 2019

When opening a plain database and trying to attach an unencrypted
database we need to explicitly specify that there is no key for the
attached database. Otherwise SQLCipher is going to use the same key as
for the main database which results in an error.

See issue #1814.

MKleusberg

added a commit
that referenced
this issue

Mar 30, 2019

When opening a plain database and trying to attach an unencrypted
database we need to explicitly specify that there is no key for the
attached database. Otherwise SQLCipher is going to use the same key as
for the main database which results in an error.

See issue #1814.

Источник

Summary: This blog is summarized about the methods to resolve SQLite encryption error. Sometimes, we face a lot of errors during the operation of the SQLite database. But the SQLite encryption error is very common and the message shows like this:
“Fixed SQLite Error – file is encrypted or is not a database”

So, if you reluctantly getting this error and looking forward to a genuine solution to fix this encryption error then, you are in the right place to resolve this error. This is the most common error SQLite users face. Now, before going for the solution let’s have a look at a brief description of the SQLite database.

Introduction to SQLite

SQLite is a lighter version of the SQL database and widely deployed database in the world of application. It is different from the other SQL databases like it does not require a separate server process. And it directly performs reads and writes operations to ordinary disk files. In a single file, a whole SQL database is included containing multiple tables, indices, triggers, and views. The codes of SQLite are in the public domain by which it is widely used in personal and professional work.

Now here I am going to mention some more features, which makes it exclusive from other database engines.

Features of SQLite Database

It does not require a separate server process, not like other SQL databases.
The SQLite has a feature to directly read and write to ordinary disk files.
This Database has ways to create, delete, execute SQL commands, and perform other common database management operations.
Mostly the SQLite source code is meant for testing and verification.
The SQLite is embedded in the end program. Its database engine is not a client-server.

Causes of SQLite File is Encrypted or is Not a Database Error

The two major reasons are responsible for the situation when the SQLite file is encrypted or is not a Database. These reasons are as follows:

Maybe the data file is not password protected.
SQLite is a sequential database which consists of a minimum of one table and one record. So error occurs when you have created a file as a new file in which it is out of the table.

Troubleshooting this SQLite Encryption Error Manually

Install the SQLite3 Database:
>> sudo apt-get update
>> sudo apt-get install sqlite3 libsqlite3-dev
Under the install documentation there is an error there when determining database file in etc/turnserver.conf:
userdb=/etc/turnuserdb.conf
should be changed to:
userdb=/var/lib/turn/turndb
PS:
In case of need of the main parts of turnuserdb.conf:
# you can listen ports 80 and 443 instead of 3478/5349
listening-port=3478
alt-listening-port=0tls-listening-port=5349
alt-tls-listening-port=0listening-ip=YourPublicIPv4
relay-ip=YourPublicIPv4
external-ip=YourPublicIPv4# realm=yourdomain.com
# server-name=yourdomain.com# lt-cred-mech
# userdb=/etc/turnuserdb.conf OAuth
user=youruser: your password# use real-valid certificate/privatekey files
# cert=/etc/ssl/certificate.pem
# pkey=/etc/ssl/private.keyno-stdout-log

Automated Method

As we all can see the manual way is very complex and need deep knowledge to perform these steps. Hence, It is advisable to try a third-party tool like SysInfoTools SQLite Repair software to get rid of these complex errors in very easy steps. The software is inbuilt with a result-oriented algorithm that performs SQLite database recovery perfectly.

Conclusion

In the above section, we have discussed the manual and automated approaches to resolve SQLite encryption error. The manual method needs technical knowledge and is not suitable for a novice user, whereas using a third-party tool makes it easier and output-driven way. Anyway, you can choose any method which is suitable for you and if are having any suggestions for us please mention them in our comment section.

Источник

Know why you get SQLITE File is encrypted or is not a database message

In this technical blog, we first introduce you to a SQLite sample database. Then, we will give you the links to download the sample database and its diagram. At the end you will know how to connect to the sample database using the sqlite3 tool.

SQLite is a popular choice as embedded database software for local/client storage in application software such as web browsers.
SQLite is also said to be a unique in-process library that is a self-contained, zero-configuration, server less, transactional SQL database engine. The code for SQLite is in the public domain and is thus free for use for any purpose, commercial or private.

Additionally, it do not possess a separate server process unlike most other SQL databases. SQLite also have the ability to read and write directly to ordinary disk files. SQLiteDatabase has methods to create, delete, execute SQL commands, and perform other common database management tasks. Most of the SQLite source code is devoted purely to testing and verification SQLite is not a client–server database engine. Rather, it is embedded into the end program.

Recently lots of user are getting message that SQLITE File is encrypted or is not a database. what is this?

This problem arises because of two things.

Either the data file is not password protected and (2)it is a sequalize database that contains at least one table and one record.

The error happens because you create a file as a new file and then out of the table. This method is completely valid but it creates a database as version two.

To resolve the issue follow the below mentioned tips.

1) Install SQLite3:
>> sudo apt-get update
>> sudo apt-get install sqlite3 libsqlite3-dev

2) In the install documentation you will find an error there when defining database file in etc/turnserver.conf:
userdb=/etc/turnuserdb.conf
should be changed to:
userdb=/var/lib/turn/turndb
PS:
Here are some important parts of turnuserdb.conf in case you need:
# you can listen ports 80 and 443 instead of 3478/5349
listening-port=3478
alt-listening-port=0

tls-listening-port=5349
alt-tls-listening-port=0

listening-ip=YourPublicIPv4
relay-ip=YourPublicIPv4
external-ip=YourPublicIPv4

# realm=yourdomain.com
# server-name=yourdomain.com

# lt-cred-mech
# userdb=/etc/turnuserdb.conf

oauth
user=youruser:yourpassword

# use real-valid certificate/privatekey files
# cert=/etc/ssl/certificate.pem
# pkey=/etc/ssl/private.key

no-stdout-log
Consider using your YourPublicIPv4 (x.x.x.x) and youruser:yourpassword.

Conclusion: Further if the problem still persist then do use the SQLite Database protection software by Aryson SQLite Recovery. In today’s time this software is much in demand because of its requirement and effective solution. The software resolve all the issue easily by clicking on few option.

Источник

Following the indications found here: Sqlite Error: file is not a database I double-checked that the path does not contain .db extension:

export const getInfopiecesDbpath = () {
  const isEnvDevelopment = process.env.NODE_ENV === 'development'

  const infopiecesDbpath = isEnvDevelopment
    ? path.join(app.getAppPath(), "src", "data", "infopieces")
    : path.join(app.getAppPath(), ".webpack", "data", "infopieces")
  return infopiecesDbpath
}

const createInfopiecesTable: any = `
  CREATE TABLE IF NOT EXISTS infopieces (
    id INTEGER PRIMARY KEY AUTOINCREMENT,
    infotext TEXT NOT NULL
  );`

const createInfopiecesIndex = `PRAGMA INDEX_LIST(infopieces);`
 
export function initializeInfopiecesDB(db: Database) {
  db.prepare(createInfopiecesTable).run()
  db.prepare(createInfopiecesIndex).get()
}

const insertIP = `
    INSERT INTO infopiecesDb (id, infotext)
    VALUES (ip.id, ip.infotext)
  `

export const insertInfopiece = (ip: IInfopiece) => {
  infopiecesDb.prepare(insertIP).run(ip)
}

let infopiecesDbpath = getInfopiecesDbpath()
let infopiecesDb = require('better-sqlite3-multiple-ciphers')(infopiecesDbpath, { verbose: console.log })
infopiecesDb.pragma("key='secret-key'")

initializeInfopiecesDB(infopiecesDb)

in main :

let infopiecesDbpath = getInfopiecesDbpath()
let infopiecesDb = require('better-sqlite3-multiple-ciphers')(infopiecesDbpath, { verbose: console.log })
infopiecesDb.pragma("key='secret-key'")
initializeInfopiecesDB(infopiecesDb)


ipcMain.handle ("insert-infopiece-intodb", (IpcMainEvent, message) => {
  console.log("ipcMain.hanlde-insert-infopiece-intodb-message: ", message.ip_01)
  insertInfopiece(message.ip_01)
})

I get this error:

Error occurred in handler for 'insert-infopiece-intodb': SqliteError: file is not a database
    at Database.prepare (/home/raphy/Playground/.webpack/main/index.js:652:21)
    at insertInfopiece (/home/raphy/Playground/.webpack/main/index.js:1773:18)
    at /home/raphy/Playground/.webpack/main/index.js:1943:32
    at node:electron/js2c/browser_init:193:579
    at EventEmitter.<anonymous> (node:electron/js2c/browser_init:161:10433)
    at EventEmitter.emit (node:events:390:28) {
  code: 'SQLITE_NOTADB'
}

Other info:

"@types/better-sqlite3": "^7.5.0",
"better-sqlite3": "^7.5.3",
"better-sqlite3-multiple-ciphers": "^7.5.2",
"electron": "17"
 node:  v16.15.0

What am I missing and / or doing wrongly?

Update 1)

If I put in main :

const infopiecesDb = require(‘better-sqlite3-multiple-ciphers’)(«../data/infopieces.sqlite», {timeout: 5000})
infopiecesDb.exec(`CREATE TABLE IF NOT EXISTS infopieces (
id INTEGER PRIMARY KEY AUTOINCREMENT,
infotext TEXT NOT NULL,
doctype VARCHAR(255),
dateStamp DATETIME NOT NULL,
shelfLife DATETIME NOT NULL,
source VARCHAR(255) NOT NULL,
lineage TEXT,
reliability INTEGER,
person VARCHAR(255),
company VARCHAR(255),
privacy INTEGER NOT NULL,
authorization TEXT,
tag VARCHAR(255)
);’)

infopiecesDb.pragma("key='secret-key'")

I get SqliteError: unable to open database file error

Источник