Troubleshooting - Oracle 5.0 Reference Manual

•
appr. key
• pages: The approximate number of leaf pages in the index.
leaf
• pages: The approximate total number of pages in the index.
size
• FIELDS: The names of the fields in the index. For a clustered index that was generated
automatically, the field list begins with the internal
DB_ROLL_PTR
the primary key. For a secondary index, the final fields are those from the primary key that are not
part of the secondary index.
The end of the table section lists the
appears whether the table is a referencing or referenced table.
14.2.12.3.
InnoDB
The following general guidelines apply to troubleshooting
• When an operation fails or you suspect a bug, you should look at the MySQL server error log (see
Section 5.2.1, "The Error
• Issues relating to the
table files), inability to open
errors. For information about these sorts of problems and errors, see

"Troubleshooting

• When troubleshooting, it is usually best to run the MySQL server from the command prompt, rather
than through
console, and so have a better grasp of what is going on. On Windows, start
console
• Use the
ENGINE INNODB STATUS
your server appears to be hung, you should use the standard Monitor to print information about
the internal state of InnoDB. If the problem is with locks, use the Lock Monitor. If the problem is in
creation of tables or other data dictionary operations, use the Table Monitor to print the contents of
the
InnoDB
• If you suspect that a table is corrupt, run
14.2.12.4. Troubleshooting
A specific issue with tables is that the MySQL server keeps data dictionary information in
it stores in the database directories, whereas
dictionary inside the tablespace files. If you move
middle of a data dictionary operation, the locations of the
the locations recorded in the
A symptom of an out-of-sync data dictionary is that a
you should look in the server's error log. If the log says that the table already exists inside the
internal data dictionary, you have an orphaned table inside the
corresponding
InnoDB: Error: table test/parent already exists in InnoDB internal
InnoDB: data dictionary. Have you deleted the .frm file
InnoDB: and not used DROP TABLE? Have you used DROP DATABASE
InnoDB: for InnoDB tables in MySQL version <= 3.23.43?
InnoDB: See the Restrictions section of the InnoDB manual.
InnoDB: You can drop the orphaned table inside InnoDB by
InnoDB: creating an InnoDB table with the same name in another
InnoDB: database and moving the .frm file to the current database.
InnoDB: Then MySQL thinks the table exists, and DROP TABLE will
InnoDB: succeed.
Performance Tuning and Troubleshooting
InnoDB
vals: The approximate index cardinality.
are always added internally to the clustered index, following the fields that comprise
General Troubleshooting
Log").
data dictionary include failed
InnoDB
.InnoDB
Data Dictionary
InnoDB
or as a Windows service. You can then see what
mysqld_safe
[404] option to direct the output to the console window.
Monitors to obtain information about a problem (see
InnoDB
and the
internal data dictionary. To see tablespace information use the Tablespace Monitor.
InnoDB
InnoDB
file. The error message looks like this:
.frm
DB_ROW_ID
definitions that apply to the table. This information
FOREIGN KEY
files, and
system cannot find the path specified
Operations".
Monitors"). If the problem is performance-related, or
InnoDB
CHECK TABLE
Data Dictionary Operations
also stores the information into its own data
InnoDB
files around, or if the server crashes in the
.frm
internal data dictionary.
CREATE TABLE
1296
(row ID) field.
DB_TRX_ID
problems:
InnoDB
statements (orphaned
CREATE TABLE
Section 14.2.12.4,
mysqld
Section 14.2.12.2,
on that table.
files may end up out of synchrony with
.frm
statement fails. If this occurs,
tablespace files that has no
InnoDB
and
prints to the
mysqld
with the
--
"SHOW
files
.frm
InnoDB