MySQL Bugs: #54966: Wrong error message with no temp table space

Bug #54966	Wrong error message with no temp table space
Submitted:	2 Jul 2010 19:05	Modified:	5 Jul 2010 8:11
Reporter:	Robin Powell	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Server: Installing	Severity:	S3 (Non-critical)
Version:	5.0.77	OS:	Linux
Assigned to:		CPU Architecture:	Any

Description:
Figured this out when /usr/bin/mysql_install_db was failing.  Was not easy.

If the directory pointed to by tmpdir does not exist, then trying to create a temp table seems to cause a 1049.

How to repeat:
If the directory pointed to by tmpdir does not exist, then:

tm50-s00079 / # cat /tmp/mrun2
use mysql;
CREATE TEMPORARY TABLE tmp_db LIKE db;
tm50-s00079 / #  cat /tmp/mrun2 | /usr/sbin/mysqld --bootstrap --basedir=/usr --datadir=/db/mysql/mysql-data --skip-innodb --skip-bdb --skip-ndbcluster --user=mysql --max_allowed_packet=8M --net_buffer_length=16K --verbose

Causes the following to be added to the logs:

ERROR: 1049  Unknown database 'mysql'
100702 12:02:51 [ERROR] Aborting

100702 12:02:51 [Note] /usr/sbin/mysqld: Shutdown complete

which is both inaccurate and unhelpful.

-Robin

Please do not submit the same bug more than once. An existing bug report already describes this very problem. Even if you feel that your issue is somewhat different, the resolution is likely
to be the same. Because of this, we hope you add your comments to the original bug instead.

Thank you for your interest in MySQL.

Duplicate of bug #52644

Sorry about that; I actually did search on "1049" and came up with nothing.

-Robin