Oracle 5.0 Reference Manual page 344

myisamchk
The directory where character sets are installed. See
•
--correct-checksum
Correct the checksum information for the table.
•
--data-file-length=len
The maximum length of the data file (when re-creating data file when it is "full").
•
--extend-check
Do a repair that tries to recover every possible row from the data file. Normally, this also finds a lot of
garbage rows. Do not use this option unless you are desperate.
See also the description of this option under table checking options.
For a description of the output format, see
myisamchk".
• [323],
--force -f
Overwrite old intermediate files (files with names like tbl_name.TMD) instead of aborting.
•
--keys-used=val
For myisamchk, the option value is a bit-value that indicates which indexes to update. Each binary
bit of the option value corresponds to a table index, where the first index is bit 0. An option value of 0
disables updates to all indexes, which can be used to get faster inserts. Deactivated indexes can be
reactivated by using
• [324],
--no-symlinks
Do not follow symbolic links. Normally
option does not exist as of MySQL 4.0 because versions from 4.0 on do not remove symlinks during
repair operations.
•
--max-record-length=len
Skip rows larger than the given length if
•
--parallel-recover
Use the same technique as
This is beta-quality code. Use at your own risk!
• [324],
--quick -q
Achieve a faster repair by modifying only the index file, not the data file. You can specify this option
twice to force
myisamchk
• [324],
--recover
Do a repair that can fix almost any problem except unique keys that are not unique (which is an
extremely unlikely error with
first. You should try
--safe-recover
recovered using
--recover
remains intact.)
If you have lots of memory, you should increase the value of sort_buffer_size.
•
--safe-recover
— MyISAM Table-Maintenance Utility
[324]
[324],
-D len
[323],
-e
Section 4.6.3.5, "Obtaining Table Information with
[324],
-k val
myisamchk -r.
-l
myisamchk
[324]
myisamchk
[324],
-p
and -n, but create all the keys in parallel, using different threads.
-r
to modify the original data file in case of duplicate keys.
-r
tables). If you want to recover a table, this is the option to try
MyISAM
[324]
[324]. (In the unlikely case that
[324],
-o
324
Section 10.5, "Character Set
repairs the table that a symlink points to. This
cannot allocate memory to hold them.
only if reports that the table cannot be
myisamchk
--recover
Configuration".
[324] fails, the data file