Otdfbt

Is it a problem that pull requests are approved without any comments

How to decline physical affection from a child whose parents are pressuring them?

How is it possible that Gollum speaks Westron?

Did Darth Vader wear the same suit for 20+ years?

How to make thick Asian sauces?

Short story written from alien perspective with this line: "It's too bright to look at, so they don't"

How do I write "Show, Don't Tell" as an Asperger?

Why does the Schrödinger equation work so well for the Hydrogen atom despite the relativistic boundary at the nucleus?

What do we gain with higher order logics?

Fair use: Instructor sharing notes from textbooks

Whats the next step after commercial fusion reactors?

OOP demonstration in C++17 using a Pokémon

Sharing one invocation list between multiple events on the same object in C#

Accidentally renamed tar.gz file to a non tar.gz file, will my file be messed up

Will TSA allow me to carry a Continuous Positive Airway Pressure (CPAP)/sleep apnea device?

My coworkers think I had a long honeymoon. Actually I was diagnosed with cancer. How do I talk about it?

What are the words for people who cause trouble believing they know better?

Implement Homestuck's Catenative Doomsday Dice Cascader

C SIGINT signal in Linux

What can plausibly explain many of my very long and low-tech bridges?

Function to extract float from different price patterns

Importance sampling estimation of power function

How would you say “AKA/as in”?

Why don’t airliners have temporary liveries?

Why does Mysql or Mysqldump say Error 1049 no database found?

ERROR when restoring MySQL data dumpgetting syntax error while importing database backups in mysqlSQL Error (1064) when importing data from SQL fileI deleted my database MySQL by mistakeGetting Error “Unknown MySQL server host” during importing the sql file?Recover mysql database - mysql/mysqldump gives “table <database>.<tablename> doesn't exist (1146)”With WebMatrix, How do I Connect to a MySQL Database on a Colleague's Machine?MySQL lost connection error on mysqldumpMySQL database import silently failing?Keep getting “MySQL has gone away” and “Error while sending QUERY packet”

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;

1

I exported the SQL database for my WordPress before rebuilding my Debian 8 VPS because I wasn't able to fix some error messages I've been getting. I did the following.

$ mysql -u root -p wordpressDB < /var/www/html/example.com/backups/backup.sql

The output message I get is

ERROR 1049 (42000): Unknown database 'wordpressDB'

I also tried doing this.

MySQL -u wordpress -p wordpressDB < backup.sql

But when I put in the password, it said it was invalid. I opened up the SQL file in notepad, and the database name does exist.
I exported this file using mysqldump, and I tried importing using MySQL and mysqldump, but both times it was unsuccessful.

linux mysql debian wordpress

share|improve this question

asked Feb 14 '18 at 10:01

HeavenlyHarmonyHeavenlyHarmony

10614

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  " I opened up the SQL file in notepad, and the database name does exist." - The problem is not in the SQL file, the error comes from the MySQL server and there the database 'wordpressDB' does not exist (yet)... Depending on how the backup was created backup.sql may already include the CREATE DATABASE statements and you can use mysql -u root -p < /var/www/html/example.com/backups/backup.sql without selecting a database on the commandline
  
  – HBruijn
  Feb 14 '18 at 10:11
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I tried that, and got ERROR 1046 (3D000) at line 22: No database selected
  
  – HeavenlyHarmony
  Feb 14 '18 at 10:14
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Then you may need to create the database first...
  
  – HBruijn
  Feb 14 '18 at 10:16
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Strange, it worked. The guide at linode.com/docs/websites/hosting-a-website Misrepresented this information, making me think all I had to do was just import the database without actually having to create the database first.
  
  – HeavenlyHarmony
  Feb 14 '18 at 10:24
  

  
  
  
  

add a comment | 

1

I exported the SQL database for my WordPress before rebuilding my Debian 8 VPS because I wasn't able to fix some error messages I've been getting. I did the following.

$ mysql -u root -p wordpressDB < /var/www/html/example.com/backups/backup.sql

The output message I get is

ERROR 1049 (42000): Unknown database 'wordpressDB'

I also tried doing this.

MySQL -u wordpress -p wordpressDB < backup.sql

But when I put in the password, it said it was invalid. I opened up the SQL file in notepad, and the database name does exist.
I exported this file using mysqldump, and I tried importing using MySQL and mysqldump, but both times it was unsuccessful.

linux mysql debian wordpress

share|improve this question

asked Feb 14 '18 at 10:01

HeavenlyHarmonyHeavenlyHarmony

10614

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  " I opened up the SQL file in notepad, and the database name does exist." - The problem is not in the SQL file, the error comes from the MySQL server and there the database 'wordpressDB' does not exist (yet)... Depending on how the backup was created backup.sql may already include the CREATE DATABASE statements and you can use mysql -u root -p < /var/www/html/example.com/backups/backup.sql without selecting a database on the commandline
  
  – HBruijn
  Feb 14 '18 at 10:11
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I tried that, and got ERROR 1046 (3D000) at line 22: No database selected
  
  – HeavenlyHarmony
  Feb 14 '18 at 10:14
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Then you may need to create the database first...
  
  – HBruijn
  Feb 14 '18 at 10:16
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Strange, it worked. The guide at linode.com/docs/websites/hosting-a-website Misrepresented this information, making me think all I had to do was just import the database without actually having to create the database first.
  
  – HeavenlyHarmony
  Feb 14 '18 at 10:24
  

  
  
  
  

add a comment | 

I exported the SQL database for my WordPress before rebuilding my Debian 8 VPS because I wasn't able to fix some error messages I've been getting. I did the following.

$ mysql -u root -p wordpressDB < /var/www/html/example.com/backups/backup.sql

The output message I get is

ERROR 1049 (42000): Unknown database 'wordpressDB'

I also tried doing this.

MySQL -u wordpress -p wordpressDB < backup.sql

But when I put in the password, it said it was invalid. I opened up the SQL file in notepad, and the database name does exist.
I exported this file using mysqldump, and I tried importing using MySQL and mysqldump, but both times it was unsuccessful.

linux mysql debian wordpress

share|improve this question

asked Feb 14 '18 at 10:01

HeavenlyHarmonyHeavenlyHarmony

10614

$ mysql -u root -p wordpressDB < /var/www/html/example.com/backups/backup.sql

ERROR 1049 (42000): Unknown database 'wordpressDB'

MySQL -u wordpress -p wordpressDB < backup.sql

share|improve this question

asked Feb 14 '18 at 10:01

HeavenlyHarmonyHeavenlyHarmony

10614

share|improve this question

asked Feb 14 '18 at 10:01

HeavenlyHarmonyHeavenlyHarmony

10614

asked Feb 14 '18 at 10:01

HeavenlyHarmonyHeavenlyHarmony

10614

asked Feb 14 '18 at 10:01

HeavenlyHarmonyHeavenlyHarmony

10614

1 Answer
1

active

oldest

votes

0

Based on your comments below your question, it sounds like you probably omitted the --databases option when you used mysqldump to backup the database.

If you backup the databases by doing mysqldump <database-name>, then the backup does not re-create the database for you. When you restore from that backup, you need to create the database that you want to import into and then import into that database, which may or may not be the same name as the database you exported from earlier.

If you do not want to be required to do this, then, when creating your backup, you export like this: mysqldump --databases <database-name>. Doing that, the backup will have the command to re-create the database when it is imported back into MySQL.

There are also other differences between those two usages. If you use the first version, then any symbols after the database name are considered table names to include in the backup. As in: mysqldump MyDatabase Table1 Table2 Table3 to backup tables 1, 2, and 3, but no others.

In the second variation, all symbols after the initial database name are also treated as additional database names, so you can get multiple databases. mysqldump --databases HRDatabase WebsiteDatabase DevTestDatabase That should export all three databases.

But back to the main point: next time you use mysqldump, if you specify the --databases option then you will not need to manually create the database and use it before importing, as that would then be taken care of for you.

share|improve this answer

answered Aug 17 '18 at 18:31

LoduwijkLoduwijk

2601312

add a comment | 

Your Answer

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f897178%2fwhy-does-mysql-or-mysqldump-say-error-1049-no-database-found%23new-answer', 'question_page');

);

Post as a guest

Name

Email

Required, but never shown

0

Based on your comments below your question, it sounds like you probably omitted the --databases option when you used mysqldump to backup the database.

If you backup the databases by doing mysqldump <database-name>, then the backup does not re-create the database for you. When you restore from that backup, you need to create the database that you want to import into and then import into that database, which may or may not be the same name as the database you exported from earlier.

If you do not want to be required to do this, then, when creating your backup, you export like this: mysqldump --databases <database-name>. Doing that, the backup will have the command to re-create the database when it is imported back into MySQL.

There are also other differences between those two usages. If you use the first version, then any symbols after the database name are considered table names to include in the backup. As in: mysqldump MyDatabase Table1 Table2 Table3 to backup tables 1, 2, and 3, but no others.

In the second variation, all symbols after the initial database name are also treated as additional database names, so you can get multiple databases. mysqldump --databases HRDatabase WebsiteDatabase DevTestDatabase That should export all three databases.

But back to the main point: next time you use mysqldump, if you specify the --databases option then you will not need to manually create the database and use it before importing, as that would then be taken care of for you.

share|improve this answer

answered Aug 17 '18 at 18:31

LoduwijkLoduwijk

2601312

add a comment | 

0

Based on your comments below your question, it sounds like you probably omitted the --databases option when you used mysqldump to backup the database.

If you backup the databases by doing mysqldump <database-name>, then the backup does not re-create the database for you. When you restore from that backup, you need to create the database that you want to import into and then import into that database, which may or may not be the same name as the database you exported from earlier.

If you do not want to be required to do this, then, when creating your backup, you export like this: mysqldump --databases <database-name>. Doing that, the backup will have the command to re-create the database when it is imported back into MySQL.

There are also other differences between those two usages. If you use the first version, then any symbols after the database name are considered table names to include in the backup. As in: mysqldump MyDatabase Table1 Table2 Table3 to backup tables 1, 2, and 3, but no others.

In the second variation, all symbols after the initial database name are also treated as additional database names, so you can get multiple databases. mysqldump --databases HRDatabase WebsiteDatabase DevTestDatabase That should export all three databases.

But back to the main point: next time you use mysqldump, if you specify the --databases option then you will not need to manually create the database and use it before importing, as that would then be taken care of for you.

share|improve this answer

answered Aug 17 '18 at 18:31

LoduwijkLoduwijk

2601312

add a comment | 

Based on your comments below your question, it sounds like you probably omitted the --databases option when you used mysqldump to backup the database.

If you backup the databases by doing mysqldump <database-name>, then the backup does not re-create the database for you. When you restore from that backup, you need to create the database that you want to import into and then import into that database, which may or may not be the same name as the database you exported from earlier.

If you do not want to be required to do this, then, when creating your backup, you export like this: mysqldump --databases <database-name>. Doing that, the backup will have the command to re-create the database when it is imported back into MySQL.

There are also other differences between those two usages. If you use the first version, then any symbols after the database name are considered table names to include in the backup. As in: mysqldump MyDatabase Table1 Table2 Table3 to backup tables 1, 2, and 3, but no others.

In the second variation, all symbols after the initial database name are also treated as additional database names, so you can get multiple databases. mysqldump --databases HRDatabase WebsiteDatabase DevTestDatabase That should export all three databases.

But back to the main point: next time you use mysqldump, if you specify the --databases option then you will not need to manually create the database and use it before importing, as that would then be taken care of for you.

share|improve this answer

answered Aug 17 '18 at 18:31

LoduwijkLoduwijk

2601312

share|improve this answer

answered Aug 17 '18 at 18:31

LoduwijkLoduwijk

2601312

answered Aug 17 '18 at 18:31

LoduwijkLoduwijk

2601312

answered Aug 17 '18 at 18:31

LoduwijkLoduwijk

2601312