MySQL Bugs: #14123: Create table attempt causes error 1050, when no table actually exists.

Bug #14123	Create table attempt causes error 1050, when no table actually exists.
Submitted:	18 Oct 2005 17:53	Modified:	21 Nov 2005 14:06
Reporter:	Jason Williams	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S2 (Serious)
Version:	4.1.14	OS:	Solaris (Solaris 10 AMD64)
Assigned to:		CPU Architecture:	Any

Description:
Happens under MySQL Max 4.1.14 Solaris 10 AMD64 pre-built binaries.

When running supersmack or any manual CREATE TABLE, and error 1050 is thrown saying that table already exists. However, the database in question has no files in it and has the correct filesystem permissions. This behavior happens regardless of database. A DROP TABLE reports the table does not exist yet.

Re-installing MySQL Max and recreating the data dir doesn't fix the issue.

How to repeat:
Install MySQL Max 4.1.14 Solaris 10 AMD64 from the pre-built Solaris pkg.

Install super-smack.

Run: super-smack /usr/share/smacks/update-select.smack 10 10000

Try any "CREATE TABLE" query.

Suggested fix:
Install MySQL Standard 4.1.14 Solaris 10 AMD64 pre-build binaries. Doesn't seem to suffer the same problem.

Thank you for a problem report. I have no root access to Solaris 10 boxes right now, so, please, send the detailed log of all the actions you had performed. The simplest one that demonstrates the problem with package.

Can it be so that you have no space at the file system used by the package (df -k results will help to decide)? May be, it is a problem of permissions?

Solaris package and .tar.gz are built from exactly the same sources, so it can be either a packaging problem or some problem in your installation actions.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".