SpirirHost Support Centre: MySQL Reference Manual p.235

<< previous page -- table of contents -- next page >>

Chapter_1

Chapter_2

Chapter_3

Chapter_4

Chapter_5

Return to Table of Contents

Table of Contents
1. General Information
2. MySQL Installation
3. Tutorial Introduction
4. Database Administration
5. MySQL Optimisation
6. MySQL Language Reference
7. MySQL Table Types
8. MySQL APIs
9. Extending MySQL

Chapter 4: Database Administration 235 but you shouldn't use this option if the mysqld server is using the table and you are running mysqld with --skip-external-locking. -T or --read-only Don't mark table as checked. This is useful if you use myisamchk to check a table that is in use by some other application that doesn't use locking (like mysqld --skip-external-locking). 4.4.6.4 Repair Options for myisamchk The following options are used if you start myisamchk with -r or -o: -D # or --data-file-length=# Max length of datale (when re-creating datale when it's 'full'). -e or --extend-check Try to recover every possible row from the datale. Normally this will also nd a lot of garbage rows. Don't use this option if you are not totally desperate. -f or --force Overwrite old temporary les (table_name.TMD) instead of aborting. -k # or keys-used=# If you are using ISAM, tells the ISAM table handler to update only the rst # indexes. If you are using MyISAM, tells which keys to use, where each binary bit stands for one key (rst key is bit 0). This can be used to get faster inserts! Deactivated indexes can be reactivated by using myisamchk -r. keys. -l or --no-symlinks Do not follow symbolic links. Normally myisamchk repairs the table a symlink points at. This option doesn't exist in MySQL 4.0, as MySQL 4.0 will not remove symlinks during repair. -r or --recover Can x almost anything except unique keys that aren't unique (which is an extremely unlikely error with ISAM/MyISAM tables). If you want to recover a table, this is the option to try rst. Only if myisamchk reports that the table can't be recovered by -r, you should then try -o. (Note that in the unlikely case that -r fails, the datale is still intact.) If you have lots of memory, you should increase the size of sort_buffer_size! -o or --safe-recover Uses an old recovery method (reads through all rows in order and updates all index trees based on the found rows); this is an order of magnitude slower than -r, but can handle a couple of very unlikely cases that -r cannot handle. This recovery method also uses much less disk space than -r. Normally one should always rst repair with -r, and only if this fails use -o. If you have lots of memory, you should increase the size of key_buffer_size! -n or --sort-recover Force myisamchk to use sorting to resolve the keys even if the temporary les should be very big.

MySQL Reference Manual

Home
Hosting Plans \| Domain Registration \| About Us \| Contact Us \| Site Map Terms of Use \| Privacy Policy \| Guarantees Merchant Accounts

SpiritHost - web hosting for spiritual and education sites SpiritHit.com - Religious and Spiritual Portal Copyright © 2002 Dyntex Group, Inc. All Rights Reserved

Return to Table of Contents	Back to top

Web Hosting: Manuals & FAQ's

1. Unix-Based Web Hosting
2. Unix Dedicated Servers
3. Windows Dedicated Servers
4. CuteFTP User’s Guide
5. CuteHTML User’s Guide
6. WS_FTP Pro User's Guide
7. Miva Order User's Guide
8. Miva Merchant User's Guide