Common Errors When Using MySQL Programs
2956
See also
Section C.5.2.9, “
MySQL server has gone away
”
.
C.5.2.12.
The table is full
If a table-full error occurs, it may be that the disk is full or that the table has reached its maximum size.
The effective maximum table size for MySQL databases is usually determined by operating system
constraints on file sizes, not by MySQL internal limits. See
Section E.7.3, “Limits on Table Size”
.
This error can occur sometimes for MySQL Cluster tables even when there appears to be more than
sufficient data memory available. See the documentation for the
DataMemory
[1559]
MySQL Cluster
data node configuration parameter, as well as
Section 17.1.2, “MySQL Cluster Nodes, Node Groups,
Replicas, and Partitions”
, for more information.
C.5.2.13.
Can't create/write to file
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
[424]
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
Section 4.2.3.3, “Using Option Files”
.
Another cause of this error can be permissions issues. Make sure that the MySQL server can write to
the
tmpdir
[502]
directory.
Check also the error code that you get with
perror
. One reason the server cannot write to a table is
that the file system is full:
shell>
perror 28
OS error code 28: No space left on device
If you get an error of the following type during startup, it indicates that the file system or directory used
for storing data files is write protected. Providing the write error is to a test file, This error is not serious
and can be safely ignored.
Can't create test file /usr/local/mysql/data/master.lower-test
C.5.2.14.
Commands out of sync
If you get
Commands out of sync; you can't run this command now
in your client code,
you are calling client functions in the wrong order.
This can happen, for example, if you are using
mysql_use_result()
and try to execute a new query
before you have called
mysql_free_result()
. It can also happen if you try to execute two queries
that return data without calling
mysql_use_result()
or
mysql_store_result()
in between.
C.5.2.15.
Ignoring user
If you get the following error, it means that when
mysqld
was started or when it reloaded the grant
tables, it found an account in the
user
table that had an invalid password.
Found wrong password for user 'some_user'@'some_host'; ignoring user
Summary of Contents for 5.0
Page 1: ...MySQL 5 0 Reference Manual ...
Page 18: ...xviii ...
Page 60: ...40 ...
Page 396: ...376 ...
Page 578: ...558 ...
Page 636: ...616 ...
Page 844: ...824 ...
Page 1234: ...1214 ...
Page 1427: ...MySQL Proxy Scripting 1407 ...
Page 1734: ...1714 ...
Page 1752: ...1732 ...
Page 1783: ...Configuring Connector ODBC 1763 ...
Page 1793: ...Connector ODBC Examples 1773 ...
Page 1839: ...Connector Net Installation 1819 2 You must choose the type of installation to perform ...
Page 2850: ...2830 ...
Page 2854: ...2834 ...
Page 2928: ...2908 ...
Page 3000: ...2980 ...
Page 3122: ...3102 ...
Page 3126: ...3106 ...
Page 3174: ...3154 ...
Page 3232: ...3212 ...
