myisamchk.
At https://dev.mysql.com/doc/refman/5.1/en/myisam-optimization.html I read this:
To coalesce fragmented rows and eliminate wasted space that results
from deleting or updating rows, run myisamchk in recovery mode:
shell> myisamchk -r tbl_name
You can optimize a table in the same
- Original Message -
> From: "Hank"
>
> I'm trying to rebuild an index after disabling all keys using
> myisamchk and adding all 144 million records, so there is no current index on
> the
> table.
Ahhh... I didn't realise that.
> But in ord
>
> > Exactly - I can't create an index on the table until I remove the
> > duplicate records.
>
> I was under the impression you were seeing this during a myisamchk run -
> which indicates you should *already* have a key on that field. Or am I
> interpreting that
- Original Message -
> From: "Hank"
>
> Exactly - I can't create an index on the table until I remove the
> duplicate records.
I was under the impression you were seeing this during a myisamchk run - which
indicates you should *already* have a key on that
On Mon, Sep 19, 2011 at 7:19 AM, Johan De Meersman wrote:
> - Original Message -
> > From: "Hank"
> >
> > While running a -rq on a large table, I got the following error:
> >
> > myisamchk: warning: Duplicate key for record at 54381140 agains
- Original Message -
> From: "Hank"
>
> While running a -rq on a large table, I got the following error:
>
> myisamchk: warning: Duplicate key for record at 54381140 against
> record at 54380810
>
> How do I find which records are duplicated (wit
While running a -rq on a large table, I got the following error:
myisamchk: warning: Duplicate key for record at 54381140 against
record at 54380810
How do I find which records are duplicated (without doing the typical
self-join or "having cnt(*)>1" query)? This table has 144
Hello All,
I have a new install of CentOS 5.5. 64bit running MySQL 5.5. This box
has 8GB of memory and is running nothing else other than mysql.
Shortly, I will be copying over a 80GB database from a Mysql 4.1.x server,
and need to repair/upgrade most of the tables. I'm using myisamc
I'm looking to optimize the myisamchk settings for some table rebuilds
I need to do.
I'm running CentOS 5 and MySQL 5.1 in a VMWare VM with 4 vCPUs and 4GB
of memory.
All the examples I can find online look like they are several years
old, and just copied from someone else's c
On Tue, 16 Jun 2009, Thomas Spahni wrote:
Hi
I have MySQL 5.0.64 compiled from source. When I run myisamchk on any
table I get the following warnings:
Warning: option 'key_buffer_size': unsigned value 18446744073709551615
adjusted to 4294963200
Warning: option 'read_buffer_
On Wed, 17 Jun 2009, Johan De Meersman wrote:
Aren't those options defined in megabytes ?
On Tue, Jun 16, 2009 at 4:59 PM, Thomas Spahni wrote:
Hi
I have MySQL 5.0.64 compiled from source. When I run myisamchk
on any
table I get the following warnings:
Wa
Hi
I have MySQL 5.0.64 compiled from source. When I run myisamchk on any
table I get the following warnings:
Warning: option 'key_buffer_size': unsigned value 18446744073709551615
adjusted to 4294963200
Warning: option 'read_buffer_size': unsigned value 1844674407370
atabase.
4. Generate all index keys: myisamchk --sort_buffer_size=2700M
--key_buffer_size=2700M -r --tmpdir=/tmpdir --quick /ut_netflow_4.MYI
5. flush privileges: FLUSH TABLE ut_netflow_4
6. restart server.
Everything up to step 3 goes great. Step 4 and 5 on the other hand do
not seem to work. After r
index keys: myisamchk --sort_buffer_size=2700M
--key_buffer_size=2700M -r --tmpdir=/tmpdir --quick /ut_netflow_4.MYI
5. flush privileges: FLUSH TABLE ut_netflow_4
6. restart server.
Everything up to step 3 goes great. Step 4 and 5 on the other hand do
not seem to work. After running the command at st
Had a minor crisis this morning. One of my database tables had become
corrupted.
As I've done quite a few times, I shut down the db, ran myisamchk -r and it
seemed to repair the table.
Shortly afterwards it corrupted again - seemed a little strange, but decided
I'd give it another
I wrote:
> My problem isn't quite the same as the original poster's, but I
suspect the solution may be the same. However, I'm having trouble
> running the myisamchk command.
I'm using the Unix Terminal in Mac OS X, with MySQL 5.0.19, and it
won't let me ge
Hello,
Is it possible to tell myisamchk where the intermediate files (.TMD) must be
created.
Because my database are big and these not enough space in his directory.
I try with --tmpdir but this doesn't work.
I use myisamchk ver 2.7 and mysql 4.1.11
thank's
Nuno
--
MyS
> At 14:02 +0300 1/6/06, Remo Tex wrote:
>>If you change the character set when running MySQL, you must run
>>myisamchk -r -q --set-collation=collation_name on all MyISAM tables.
>
> Hi
>
> My problem isn't quite the same as the original poster's, but I
&
At 18:34 +0100 4/6/06, Chris Sansom wrote:
I'm stumped! How exactly do I go about this?
It's OK - I sorted it out. Turns out I needed to use upper case for
the .MYI. Doh!
--
Cheers... Chris
Highway 57 Web Development -- http://highway57.co.uk/
Old professors never die; they just lose their
At 14:02 +0300 1/6/06, Remo Tex wrote:
If you change the character set when running MySQL, you must run
myisamchk -r -q --set-collation=collation_name on all MyISAM tables.
Hi
My problem isn't quite the same as the original poster's, but I
suspect the solution may be the same. Ho
Hank <[EMAIL PROTECTED]> writes:
>How do I find which record is duplicated (without doing the typical
>self-join query)? This table has 70 million rows, so that's not
>really feasible.
select col, count(1) cnt from tab group by col having cnt > 1;
This will print out all duplicated col rows.
While running a -rq on a large table, I got the following error:
myisamchk: warning: Duplicate key for record at 54381140 against
record at 54380810
How do I find which record is duplicated (without doing the typical
self-join query)? This table has 70 million rows, so that's not
r
Hello.
Check if the speed of recovering changes if you run myisamchk with
-n option among other parameters to force using sort recovery. However,
it requires a lot of disk space. See:
http://dev.mysql.com/doc/mysql/en/myisamchk-repair-options.html
I guess it might help because this
used to run myisamchk to fix and
optimize this table (myisamchk -r, -S, -a). All of a sudden, this process
has become slower to the point that I have given up. It used to take 3
hours to repair/optimize each table. Now we are running myisamchk for the
last 12 hours and it has completed only 1/3 of
Hello.
There're some good descriptions at:
http://dev.mysql.com/doc/mysql/en/crash-recovery.html
http://dev.mysql.com/doc/mysql/en/myisampack.html
[EMAIL PROTECTED] wrote:
> Hello everyone,
> When running these utilities does the MySQL daemon have to be "down"?
> There's no activ
Hello everyone,
When running these utilities does the MySQL daemon have to be "down"?
There's no activity against the database other than an occasional query.
George
__
Switch to Netscape Internet Service.
As low as $9.95 a month
Hello.
Have you stopped MySQL server before executing myisamchk?
sirisha gnvg <[EMAIL PROTECTED]> wrote:
> [-- text/plain, encoding 8bit, charset: iso-8859-1, 21 lines --]
>
> hello everybody,
>
> I used myisamchk /path/to/datadir/mysql/*.* to find memory
hello everybody,
I used myisamchk /path/to/datadir/mysql/*.* to find memory already in
use and free memory available for all tables in 'mysql' database.where mysql in
above path refers to mysql database.
I got two types of errors for all tables in that directory.
We have a database running Invision Power Board. The table containing the
posts (>3.000.000 rows) keeps on crashing from time to time, and the index
gets corrupt. We stop mysql, and run "myisamchk -r tablename", which
behaves strangely. First it uses 3-5 minutes fixing the inde
ey changed the syntax
mysql 4.1.7 running on windows 2000 server, dual 2.8 xeon with 1 gig of ram
I do not have any myisamchk options specified in the my.ini
I let it run for 2 weeks, and I killed it the data file is good, it sat
for 2 weeks indexing, at least as far as I can tell
is this normal fo
; wrote:
> Gleb Paharenko wrote:
>
>>Hello.
>>
>>
>>
>>There is a variable sort_buffer, which you can set with -O sort_buffer=xxxM
>>or in my.cnf.
>>
>>
>>
>>
>>>myisamchk -o -p -f --sort_key_blocks=512M - -key
Gleb Paharenko wrote:
Hello.
There is a variable sort_buffer, which you can set with -O sort_buffer=xxxM or
in my.cnf.
myisamchk -o -p -f --sort_key_blocks=512M - -key_cache_block_size=512M
it's no longer -O sort_buffer=xxxM
it's now --sort_key_blocks
and I set it to 512M an
it's been running a week
> and who knows how long that'll take
>
> myisamchk -o -p -f --sort_key_blocks=512M - -key_cache_block_size=512M
> --read_buffer_size=8M 321st_stat
> - parallel recovering (with sort) MyISAM-table '321st_stat'
> Data records: 0
Are these critical errors? It keeps on going, saying it's fixing records
I tried doing a check table on the main server, it's been running a week
and who knows how long that'll take
myisamchk -o -p -f --sort_key_blocks=512M - -key_cache_block_size=512M
--read_buffer_siz
by "mysqladmin ping".
According to all documentation that I found and the source code, mysqlcheck in
opposide to myisamchk does not deal with the tables files itself which could
be suspicious (e.g. with skip-locking) but just issue a "CHECK TABLE xyz FAST"
command to the server
all documentation that I found and the source code, mysqlcheck in
opposide to myisamchk does not deal with the tables files itself which could
be suspicious (e.g. with skip-locking) but just issue a "CHECK TABLE xyz FAST"
command to the server which should be safe regardless who else d
Hanno Fietz <[EMAIL PROTECTED]> wrote:
> Jul 2 03:10:28 t56 kernel: hda: dma_intr: status=0x51 { DriveReadySeekComplete
> Error }
> Jul 2 03:10:28 t56 kernel: hda: dma_intr: error=0x40 { UncorrectableError },
> LBAsect=429367, sector=316864
> Jul 2 03:10:28 t56 kernel: end_request: I/O error,
ty.
I would put my money on the drive.
40G is tiny these days, and cheap.
Hanno Fietz wrote:
Yes, I was suspecting that as well, but: Why do I get these messages
whenever I run myisamchk and (almost) never at any other time? Is
myisamchk using the hd more extensively than e. g. MySQL itself? Can
Yes, I was suspecting that as well, but: Why do I get these messages
whenever I run myisamchk and (almost) never at any other time? Is
myisamchk using the hd more extensively than e. g. MySQL itself? Can the
rather large demand for temporary disk space account for that?
Thanks,
Hanno
some administrative tables and one large data
table (now ~ 30 M rows, ~ 1GB index file and ~ 800 MB data file) that
we insert new rows into on a per-minute basis. Read / Write ratio
probably is around 1 : 2 or 1 : 3. To achieve good performance despite
the size of the table, we run "myisamc
e and ~ 800 MB data file) that we
insert new rows into on a per-minute basis. Read / Write ratio probably
is around 1 : 2 or 1 : 3. To achieve good performance despite the size
of the table, we run "myisamchk -r" and "myisamchk -R 1" every night as
a part of the backup routine.
Hello *
my Problem (resolved for newer mysql Versions):
A MyIsam Table is packed with myisampack
A subsequent myisamchk -r or -o with index reordering erroneously
marks wrong indices in the packed table for 4.0.15
(unpacking reconstructs the original table)
This seems to be a known issue
Hi.
I'm having this problem on 4.1.2, when I run myisamchk -o on my table I
get a bunch of these lines:
Duplicate key 3 for record at 56134200 against new record at 244828223
then it segfaults.
key 3 is a fulltext. I tried the same thing on the same data with 4.0.14
and it worked fi
On 04.06.2004 21:09 (+0200), Mark Maggelet wrote:
Hi.
I'm having this problem on 4.1.2, when I run myisamchk -o on my table I
get a bunch of these lines:
[...]
Would you please not reply to a mail to create a new thread? This
message will be displayed somewhere deep inside another thread an
Hi.
I'm having this problem on 4.1.2, when I run myisamchk -o on my table I
get a bunch of these lines:
Duplicate key 3 for record at 56134200 against new record at 244828223
then it segfaults.
key 3 is a fulltext. I tried the same thing on the same data with 4.0.14
and it worked fi
The problem is the data file is about 25GB. The index file generally
turns out to be at least half the size(~15GB)Unfortunately, I don't
have 40GB free space on the machine. That's why the NFS server came
into picture.
I managed to start the table rebuild from a linux box running
MySQL4.0.12. S
Rishi Pande wrote:
Hello,
I have been having trouble with rebuilding a database from backup.
The backup consists of the MYD and frm files only. Therefore, I need
to rebuild the myi file. I am using MySQL4.0.14 on Mac OS X. I use the
myisamchk command to rebuild the database, in the
Hello,
I have been having trouble with rebuilding a database from backup.
The backup consists of the MYD and frm files only. Therefore, I need
to rebuild the myi file. I am using MySQL4.0.14 on Mac OS X. I use the
myisamchk command to rebuild the database, in the following way
shell>/path
> You know, this might sound strange, but does the performance drop off at
> all if you lose the indices? A table scan of rows 8 bytes wide is going
> to be pretty damn quick. Plus there's a lot less maintenance to do
> without
> indices and no risk of them getting corrupted.
A full table scan is
On 8 Feb 2004, at 20:28, Mark Hazen wrote:
My tables are just 2 INT columns. I have unique indexes on them going
both
ways.
Sounds like you're sorted.
You know, this might sound strange, but does the performance drop off at
all if you lose the indices? A table scan of rows 8 bytes wide is goin
> What's the nature of your query?
>
> If it's using an integer index and that's what your searching on, then
> having
> it physically sorted is a Good Thing. If you're table-scanning your
> main table, you're toast anyway. Finding ways of making that faster is
> the
> way to go, maybe partitioning
index or a data file with no
deleted rows in it?
I don't mind running either OPTIMIZE TABLE (which apparently rebuilds
everything and sorts it) or just the myisamchk to sort the index. Does
anyone know which one might get me more mileage?
What's the nature of your query?
If it's u
In reference to my earlier message, I think I've figured out that the
equivalent command for OPTIMIZE TABLE is:
myisamchk -r --sort-index --analyze
That isn't documented anywhere... and in fact, the French language version
says something conflicting (I don't speak French but
Hi all!
Running 4.0.17.
I hope this isn't a stupid question, but it appears that OPTIMIZE TABLE is
NOT equivalent to:
myisamchk --quick --check-only-changed --sort-index --analyze
Maybe I'm missing something, but OPTIMIZE TABLE rebuilds both the data file
and the index file (I see a T
? This runs for a VERY long time.
The table I loaded is marked as broken - do I need to start over or can I fix it? The
recommendation from myisamchk (use the -f to fix the table) resulted in the same Error
22.
Unless I have missed something (likely ), this seems like a pretty major bug - is
MySQL
Hello,
I am following the advice of the manual when bulk loading a large table by turning off
index builds before LOAD DATA INFILE. The load ends normally (73 GB). The mysamchk
build of the indices fails:
myisamchk: warning: Can't change size of indexfile, error: 22
myisamchk: error: 2
Hello,
I am following the advice of the manual when bulk loading a large table by turning off
index builds before LOAD DATA INFILE. The load ends normally (73 GB). The mysamchk
build of the indices fails:
myisamchk: warning: Can't change size of indexfile, error: 22
myisamchk: error: 2
On Thu, Nov 06, 2003 at 08:33:55AM -0800, Henry Hank wrote:
>
> Very simple question:
>
> Can I use myisamchk version 2.6 (from mysql 4.0.15) to fix/repair a table from
> mysql version 3.23.41 (which includes myisamchk version 1.49)??
It should be safe, yes.
--
Jeremy D. Zawo
Very simple question:
Can I use myisamchk version 2.6 (from mysql 4.0.15) to fix/repair a table from
mysql version 3.23.41 (which includes myisamchk version 1.49)??
The reason is that I have more disk space and processing power on a machine
with 4.0.15 installed, but I'd like to rebuild
n. At MySQL
AB, we run a cron job to check all our important tables once a week, using a line like
this in a `crontab' file:
35 0 * * 0 /path/to/myisamchk --fast --silent /path/to/datadir/*/*.MYI
This prints out information about crashed tables so we can examine and repair them
when neede
Hi!
On Aug 21, Luc Foisy wrote:
> Thank you Paul.
> whew! So just checking will not do anything to the database, in an case?
yes, but ONLY if you run myisamchk with --read-only flag.
> I am not really caring if it returns the "# users still connected/ or
> table not closed rig
r warnings telling my that tables are corrupted...
Well, the thing is, if you don't tell the server to flush changes, I believe
there may be partially flushed changes that can cause myisamchk to get
confused and believe that there is corruption. I don't recall that I have
ever seen this in pra
corrupted...
-Original Message-
From: Paul DuBois [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 21, 2003 3:08 PM
To: Luc Foisy; MYSQL-List (E-mail)
Subject: RE: myisamchk question (important)
I should qualify my answer, to indicate something that may not apply
to the situation you have in
I should qualify my answer, to indicate something that may not apply
to the situation you have in mind.
If you're using myisamchk only to *check* tables, it operates in read-only
fashion. The problems occur if you're using it to repair tables, because
then if you have both myisamc
At 14:37 -0400 8/21/03, Luc Foisy wrote:
If you read http://www.mysql.com/doc/en/Maintenance_regimen.html
they say something interesting that would contracdict other places
in the documentation
They actually recomend running myisamchk on a running instance of
mysqld. The method on that page (a
Luc Foisy unknowingly asked us:
Would anything happen to the database if I ran "myisamchk --silent /usr/data/mysql/*/*.MYI" when I havent run "FLUSH TABLES" first?
As it states in the documentation:
If mysqld is running, you must force a sync/close of all tables with FLUSH TA
If you read http://www.mysql.com/doc/en/Maintenance_regimen.html they say something
interesting that would contracdict other places in the documentation
They actually recomend running myisamchk on a running instance of mysqld. The method
on that page (a method they use themselves) would not even
At 9:54 -0400 8/19/03, Luc Foisy wrote:
Would anything happen to the database if I ran "myisamchk --silent
/usr/data/mysql/*/*.MYI" when I havent run "FLUSH TABLES" first?
Yes, you may have unflushed changes still in the server's buffers.
Running myisamchk in that cas
Would anything happen to the database if I ran "myisamchk --silent
/usr/data/mysql/*/*.MYI" when I havent run "FLUSH TABLES" first?
As it states in the documentation:
If mysqld is running, you must force a sync/close of all tables with FLUSH TABLES and
ensure that no one
If mysqld is running, you must force a sync/close of all tables with FLUSH TABLES and
ensure that no one is using the tables while you are running myisamchk. In MySQL
Version 3.23 the easiest way to avoid this problem is to use CHECK TABLE instead of
myisamchk to check tables.
If i didnt do
Yes, I think you're right on that. Any idea what the cause might be or what
I can do to find out? I do have a core file, but I'm at a loss as to what to
do with it...
Original Message Follows
From: Sergei Golubchik <[EMAIL PROTECTED]>
Subject: Re: myisamchk Illegal Instr
Hi!
On Aug 07, Paul Mahon wrote:
>
> % bin/myisamchk -t ~/tmp -e BROKE/EventsBROKE
> Checking MyISAM file: BROKE/EventsBROKE
> Data records: 101333504 Deleted blocks: 86920613
> bin/myisamchk: warning: Table is marked as crashed and last repair failed
> - check file-size
&g
Hello, I recently managed to corrupt a table pretty badly. I read the
sections in the documentation about recovering after a crash. None of the
methods worked. All give output similar to the following:
% bin/myisamchk -t ~/tmp -f -o BROKE/EventsBROKE
- recovering (with keycache) MyISAM-table
y badly. I read the
> sections in the documentation about recovering after a crash. None of the
> methods worked. All give output similar to the following:
> % bin/myisamchk -t ~/tmp -f -o BROKE/EventsBROKE
> - recovering (with keycache) MyISAM-table 'BROKE/EventsBROKE.MYI'
&
"Paul Mahon" <[EMAIL PROTECTED]> wrote:
> Hello, I recently managed to corrupt a table pretty badly. I read the
> sections in the documentation about recovering after a crash. None of the
> methods worked. All give output similar to the following:
> % bin/my
Thnks a lot
Patrizio
-Messaggio originale-
Da: Egor Egorov [mailto:[EMAIL PROTECTED]
Inviato: lunedì 21 luglio 2003 14.02
A: [EMAIL PROTECTED]
Oggetto: Re: myisamchk -R
"PaT!" <[EMAIL PROTECTED]> wrote:
>
> I need a hint how to use myisamchk
>
> I use t
"PaT!" <[EMAIL PROTECTED]> wrote:
>
> I need a hint how to use myisamchk
>
> I use this syntax in a shell but it doesn't work
>
> myisamchk -R=ID \mysql\data\db\mytable.myi
>
> ID is the index name I want to use to sort the table
>
>
Hi,
I need a hint how to use myisamchk
I use this syntax in a shell but it doesn't work
myisamchk -R=ID \mysql\data\db\mytable.myi
ID is the index name I want to use to sort the table
I'm using mysql 4.0.13 on Win 2K server
Thanks for help
Patrizio
I am using mysql 3.23.54 and am trying to repair the index, using
myisamchk -o tablename.MY and am getting the following error:
- recovering (with keycache) MyISAM-table 'msg.MYI'
Data records: 498802
myisamchk: Error writing file 'msg.TMD' (Errcode: 28)
myisamchk: error
and am trying to repair the index, using
> myisamchk -o tablename.MY and am getting the following error:
>
> - recovering (with keycache) MyISAM-table 'msg.MYI'
> Data records: 498802
> myisamchk: Error writing file 'msg.TMD' (Errcode: 28)
> myisamchk: error: 2
automatically?
However, if I'm willing to run myisamchk from the command line, will that
still happen?
best regards,
Jens-Petter Salvesen
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
Mark,
> Is the only reason for this the fact that I have mysql running? Are
> mysqlcheck and myisamchk doing the exact same thing. Or are
> there scenarios in which one reports errors and the other doesn't.
mysqlcheck and myisamchk are doing the same things _basically_.
mysqlchec
Hi,
I have a question about using myisamchk and mysqlchk.
I am running myisamchk -s on a certain table and get this error:
/usr/local/mysql/bin/myisamchk: MyISAM file /usr/local/mysql/var/db1/my_table.MYI
/usr/local/mysql/bin/myisamchk: warning: 1 clients is using or hasn't closed the
Hi,
Some time ago i've read that we shouldn't use myisamchk while the mysql
server was running. Now, i don't find where in the manual says something
about it.
I think you should do a "FLUSH TABLES" and ensure that no one touches
the tables (including mysqld) before usi
Since the http://lists.mysql.com/ archives site is down, I'll have to
ask this question without the benifit of the archives...
I have a (very large) Perl script that has a bad tendency to cause the
following warning from myisamchk:
myisamchk: MyISAM file /var/lib/mysql//table_nam
On Monday 23 December 2002 03:05, Ray Kiddy wrote:
> I had used MySQL's myisampack utility to pack my tables, which makes
> them read-only, but now I want them to be write-able again.
>
> I have used "myisamchk --recover --unpack" (tried -ru as well) and the
> tabl
I had used MySQL's myisampack utility to pack my tables, which makes
them read-only, but now I want them to be write-able again.
I have used "myisamchk --recover --unpack" (tried -ru as well) and the
table is still read-only.
What is the actual incantation one must use here? I
charitha,
Wednesday, November 27, 2002, 7:40:07 AM, you wrote:
c> In mysql tables if i want to exclude some tables to do myisamchk how can i
c> do that.
c> As if i use myisamchk *.MYI it is taking too much time to check all the
c> tables. For that i can exclude some previous
Hello all,
In mysql tables if i want to exclude some tables to do myisamchk how can i
do that.
As if i use myisamchk *.MYI it is taking too much time to check all the
tables. For that i can exclude some previous days dynamic tables and i
can execute this
How to do that???
Thanx in advance
MySQL (which may also change the>>
>sort order), you must run myisamchk -r -q on all tables. Otherwise, your
>> indexes may not be ordered correctly.
>>
>>I have a MySQL server with databases that need to begin supporting
>>japanese characters. Per
arsets= list-of-charset | complex
| all options to configure, and the character set configuration files listed
in `SHAREDIR/charsets/Index'. See section 2.3.3 Typical configure Options.
If you change the character set when running MySQL (which may also
change the
sort order), you must run m
l options to configure, and the character set configuration files listed
> in `SHAREDIR/charsets/Index'. See section 2.3.3 Typical configure Options.
>
> If you change the character set when running MySQL (which may also change the
> sort order), you must run myisamchk -r -q on all table
Hello all;
Is myisamchk known to have problems in tables with lots of rows?
I've a table with a simple, single, 32 bit integer as a key. I have about
200 million rows in it. I can run myisamchk -o -e names three times in a
row and receive this message each time:
Duplicate key 1 for reco
I got an error while executing myisamchk -rq on compressed table. Here's the
output:
[root@db prod_rel5_1_0]# myisampack buyer
Compressing buyer.MYD: (3687550 records)
- Calculating statistics
- Compressing file
62.69%
Remember to run myisamchk -rq on compressed tables
[root@db prod_rel
DO NOT run myisamchk while the server is running.
lorenzo.kh wrote:
>Hi,
>I am using mysql 4.0.0-aplha on win 2000 professional.
>I install mysql in c:\mysql.
>I write a script ( customerscript.txt) and i save this script in
>c:\mysql\bin.
>The contents of customerscript.txt I
\bin>mysql < customerscript.txt
And later on I try to check the table using the command below.
And I get the error and warning.
C:\mysql\bin>myisamchk ../data/test/customer
Checking MyISAM file: ../data/test/customer
Data records: 1 Deleted blocks: 0
myisamchk: warning: 1 c
I understand all of the reasons given by Alexander.
Yet I think that in 99% of cases, it would be best for myisamchk to do as
Mark suggest, and not run when a MySQL server is active.
Safety would be the default.
There could be a special option (--no-safety) for myisamchk to override that
check
t-in precaution. I can
> understand possible objections to myisasmchk globally locking tables out of
> the blue (it might disrupt what some clients are doing), but if myisamchk
> cannot run on a live table, it should not run on a live table. As simple as
> that.
Hi,
It is not that simple.
You can
Wednesday, May 22, 2002, 9:23:02 AM, louie wrote:
lm> Hi, i was thingking about locking the tables first so no connection
lm> could write so i can do myisamchk. Is this process safe?
lm> Procedures:
lm> 1. lockdb
lm> 2. run myisamchk -r or -o
lm> 3. unlock db
lm> Btw,
louie,
Wednesday, May 22, 2002, 9:23:02 AM, you wrote:
lm> Hi, i was thingking about locking the tables first so no connection
lm> could write so i can do myisamchk. Is this process safe?
lm> Procedures:
lm> 1. lockdb
lm> 2. run myisamchk -r or -o
lm> 3. unlock db
lm> B
1 - 100 of 194 matches
Mail list logo
