Oracle 5.0 Reference Manual page 38

information is really top secret and you do not want to show it even to us, go ahead and provide an
example using other names, but please regard this as the last choice.
• Include all the options given to the relevant programs, if possible. For example, indicate the
options that you use when you start the
any MySQL client programs. The options to programs such as
script, are often key to resolving problems and are very relevant. It is never a bad idea
configure
to include them. If your problem involves a program written in a language such as Perl or PHP,
please include the language processor's version number, as well as the version for any modules
that the program uses. For example, if you have a Perl script that uses the
modules, include the version numbers for Perl, DBI, and DBD::mysql.
• If your question is related to the privilege system, please include the output of mysqlaccess,
the output of
mysqladmin
When you test your privileges, you should first run mysqlaccess. After this, execute
and try to connect with the program that gives you trouble.
reload version
found in the directory under your MySQL installation directory.
bin
• If you have a patch for a bug, do include it. But do not assume that the patch is all we need, or that
we can use it, if you do not provide some necessary information such as test cases showing the bug
that your patch fixes. We might find problems with your patch or we might not understand it at all. If
so, we cannot use it.
If we cannot verify the exact purpose of the patch, we will not use it. Test cases help us here. Show
that the patch handles all the situations that may occur. If we find a borderline case (even a rare one)
where the patch will not work, it may be useless.
• Guesses about what the bug is, why it occurs, or what it depends on are usually wrong. Even the
MySQL team cannot guess such things without first using a debugger to determine the real cause of
a bug.
• Indicate in your bug report that you have checked the reference manual and mail archive so that
others know you have tried to solve the problem yourself.
• If your data appears corrupt or you get errors when you access a particular table, first check your
tables with TABLE. If that statement reports any errors:
CHECK
• The crash recovery mechanism handles cleanup when the server is restarted after being
InnoDB
killed, so in typical operation there is no need to "repair" tables. If you encounter an error with
tables, restart the server and see whether the problem persists, or whether the error
InnoDB
affected only cached data in memory. If data is corrupted on disk, consider restarting with the
innodb_force_recovery
• For non-transactional tables, try to repair them with
Chapter 5, MySQL Server
If you are running Windows, please verify the value of
the
SHOW VARIABLES LIKE 'lower_case_table_names'
the server handles lettercase of database and table names. Its effect for a given value should be as
described in Section 9.2.2, "Identifier Case
• If you often get corrupted tables, you should try to find out when and why this happens. In this case,
the error log in the MySQL data directory may contain some information about what happened. (This
is the file with the
.err
relevant information from this file in your bug report. Normally
if nothing killed it in the middle of an update. If you can find the cause of
easier for us to provide you with a fix for the problem. See
Causing a Problem".
• If possible, download and install the most recent version of MySQL Server and check whether it
solves your problem. All versions of the MySQL software thoroughly tested and should work without
How to Report Bugs or Problems
mysqld
reload, and all the error messages you get when trying to connect.
[1243] option enabled so that you can dump the affected tables.
Administration.
Sensitivity".
suffix in the name.) See
18
server, as well as the options that you use to run
mysqld
REPAIR TABLE
lower_case_table_names
statement. This variable affects how
Section 5.2.1, "The Error
should never crash a table
mysqld
Section C.5.1, "How to Determine What Is
and mysql, and to the
and
DBI DBD::mysql
mysqladmin
mysqlaccess
or with myisamchk. See
[466] using
Log". Please include any
dying, it is much
mysqld
can be