sqlite3.OperationalError: database is locked (SQLITE_BUSY)
Another connection holds a write lock on the SQLite file, and this one gave up waiting.
Exact message you may see
database is locked
Seen on:
SQL
Meaning
SQLite allows one writer at a time. Long transactions, open cursors, a DB browser holding the file, or many concurrent web workers cause lock contention.
Common causes
- Concurrent writers (multiple workers/threads)
- A long-running transaction or uncommitted write
- DB Browser/IDE keeping the file open
- Network filesystems (NFS/SMB) with broken locking
⚡ Quick fix
- Keep write transactions short and commit promptly
- Enable WAL mode and a busy timeout
- Close GUI tools holding the database
- Use PostgreSQL/MySQL for concurrent web workloads
Detailed fix by platform
SQL
- sql
PRAGMA journal_mode = WAL; PRAGMA busy_timeout = 5000;
How to diagnose
- Writers — How many processes write?
- Holder — Any open transaction or tool?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- 1213 MySQL ERROR 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
- Deadlock Deadlock found when trying to get lock; try restarting transaction
- Error acquiring the state lock Terraform: Error: Error acquiring the state lock — ConditionalCheckFailedException / state blob is already locked
Most viewed in SQL
Other ways to find it
Where this error sits
Origin: Data. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Did this fix work for you?
Report a correction or suggest an improvement
Last updated 13 Oct 2026