- B.1.2 Common Errors When Using MySQL Programs
- B.1.2.1 Access denied
- B.1.2.2 Can't connect to [local] MySQL server
- B.1.2.3 Client does not support authentication protocol
- B.1.2.4 Password Fails When Entered Interactively
- B.1.2.5 Host 'host_name' is blocked
- B.1.2.6 Too many connections
- B.1.2.7 Out of memory
- B.1.2.8 MySQL server has gone away
- B.1.2.9 Packet too large
- B.1.2.10 Communication Errors and Aborted Connections
- B.1.2.11 The table is full
- B.1.2.12 Can't create/write to file
- B.1.2.13 Commands out of sync
- B.1.2.14 Ignoring user
- B.1.2.15 Table 'tbl_name' doesn't exist
- B.1.2.16 Can't initialize character set
- B.1.2.17 'File' Not Found and Similar Errors
If you get an error of the following type for some queries, it means that MySQL cannot create a temporary file for the result set in the temporary directory:
Can't create/write to file '\\sqla3fe_0.ism'.
The preceding error is a typical message for Windows; the Unix message is similar.
One fix is to start mysqld with the
--tmpdir option or to add the option to the
[mysqld] section of your option file. For
example, to specify a directory of
C:\temp, use these lines:
[mysqld] tmpdir=C:/temp
The C:\temp directory must exist and have
sufficient space for the MySQL server to write to. See
項3.3.2. 「オプションファイルの使用」.
Another cause of this error can be permissions issues. Make
sure that the MySQL server can write to the
tmpdir directory.
Check also the error code that you get with perror. One reason the server cannot write to a table is that the filesystem is full:
shell> perror 28
Error code 28: No space left on device
