ERROR 1049 (42000): Unknown database
ERROR 1049 (42000): Unknown database 'mydatabasename'Short answer
Error 1049 means the server has no database with that exact name. List the databases first. Then either create it, correct the name (names are case-sensitive on Linux), or create the database before you load a dump that has no CREATE DATABASE statement.
Fix it fast
1Find out which cause you have
Connect without naming a database and list what the server really has. Compare the names letter by letter.
mysql -u root -p -e "SHOW DATABASES;"2Match what you see, then jump to its fix
What does the error look like?
ERROR 1049 (42000): Unknown database 'mydatabasename'Unknown database 'mydatabasename'
Cause 1 of 3
The database was never created on this server
1Check
You may be on a fresh server, a new container, or a different server from the one you created it on.
mysql -u root -p -e "SELECT @@hostname, @@port; SHOW DATABASES;"2Fix
Create it. Choose the character set on purpose.
CREATE DATABASE IF NOT EXISTS mydatabasename
CHARACTER SET utf8mb4;3Verify
Connect to it by name.
mysql -u root -p mydatabasename -e "SELECT DATABASE();"Confirmed by dev.mysql.com
Cause 2 of 3
The name differs in letter case
1Check
Databases are folders in the data directory, so case matters on Linux and most Unix systems but not on Windows. lower_case_table_names is 0 on Unix, 1 on Windows and 2 on macOS by default. A project that worked on Windows can fail on Linux.
mysql -u root -p -e "SHOW VARIABLES LIKE 'lower_case_table_names'; SHOW DATABASES;"2Fix
Use the exact name in the connection string and in statements. Pick one convention, preferably all lowercase.
mysql -u root -p MyDatabase3Verify
The client connects without error.
mysql -u root -p MyDatabase -e "SELECT DATABASE();"Confirmed by dev.mysql.com
Cause 3 of 3
A dump was loaded into a database that does not exist yet
1Check
mysqldump writes CREATE DATABASE only when --databases or --all-databases is used. A dump of a single database does not contain it.
grep -c -i "CREATE DATABASE" dump.sql2Fix
Create the database first, then load the dump into it.
mysql -u root -p -e "CREATE DATABASE IF NOT EXISTS mydatabasename"
mysql -u root -p mydatabasename < dump.sql3Verify
Count the tables that arrived.
mysql -u root -p mydatabasename -e "SHOW TABLES;"Confirmed by dev.mysql.com
How do I stop it coming back?
- Use lowercase database names so one config works on Windows, macOS and Linux.
- Take dumps with --databases when the restore target may be empty.
- Keep the database name in one environment variable instead of retyping it.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
- TaxiDexMy own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.
- QistLockA NestJS and React SaaS driving an Android Device Owner agent that locks financed phones when payments lapse.
- ShopGoAn e-commerce aggregator with a Python scraping engine behind its catalog, past 10K Google Play downloads.
Related fixes
Databases
Installing the Airflow MySQL provider fails on pkg-config or mysqlclient
Building the mysqlclient wheel fails during the install
The Airflow MySQL provider depends on mysqlclient, which pip compiles against the MySQL C client library.
2 causes, each with a fixDatabases
A query on Aurora MySQL dies with 'table /rdsdbdata/tmp/#sql... is full'
ERROR 1114 (HY000): The table '/rdsdbdata/tmp/#sqlfd_1586_2' is full
In Aurora MySQL 3, internal temporary tables share one pool, and when that pool and the memory-mapped overflow file are used up, a reader instance ends the query with error 1114.
3 causes, each with a fixDatabases
Azure Database for MySQL refuses a connection that does not use SSL
ERROR 3159 (HY000): Connections using insecure transport are prohibited while --require_secure_transport=ON.
Azure Database for MySQL Flexible Server requires encrypted connections by default (require_secure_transport = ON, TLS 1.2).
4 causes, each with a fixDatabases
Compiling a C or C++ program that includes mysql.h fails
undefined reference to `mysql_init'
The compiler only finds mysql.h when the MySQL client development files are installed and their folder is on the include path.
3 causes, each with a fixDatabases
DBeaver fails to resolve Maven dependencies when downloading a database driver
A driver library does not download automatically
DBeaver downloads driver jars from a Maven repository.
3 causes, each with a fixDatabases
DBeaver cannot verify the MySQL server certificate
unable to find valid certification path to requested target
DBeaver's MySQL driver is checking the server certificate and Java does not trust the CA that signed it.
2 causes, each with a fix