- 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 order to create the index, mysql has to do a fu
>
> > 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 wrong?
>
>
I'm trying to rebuild a
- 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 field. Or am I interpreting
t
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 against
> > record at 54380810
> >
> > How do I f
- 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 (without doing the typical
> self-join o
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 million rows,
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
really fea
e indices fails:
>myisamchk: warning: Can't change size of indexfile, error: 22
>myisamchk: error: 22 for record at pos 121201294124
>myISAM-table 'mytable' is not fixed because of errors
>This process works successfully on "small" tables (37 GB) on another 2003 mach
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
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
or hasn't closed the table
> DRR> properly
> DRR> myisamchk: error: Found key at page 2472960 that points to record
> DRR> outside datafile
> DRR> myisamchk: error: Keypointers and record positions doesn't match
> DRR> MyISAM-table '/var/lib/mysql/radius/ra
Do-Risika,
Monday, April 29, 2002, 7:54:51 AM, you wrote:
DRR> Can someone tell me what this error mean ?
DRR> myisamchk: MyISAM file /var/lib/mysql/radius/radacct.MYI
DRR> myisamchk: warning: 1 clients is using or hasn't closed the table
DRR> properly
DRR> myisamchk: erro
Hi all,
Can someone tell me what this error mean ?
myisamchk: MyISAM file /var/lib/mysql/radius/radacct.MYI
myisamchk: warning: 1 clients is using or hasn't closed the table
properly
myisamchk: error: Found key at page 2472960 that points to record
outside datafile
myisamchk:
Hi:
I am running a simple INSERT query in perl code and am getting the
following error from myisamchk:
myisamchk: warning: 1 clients is using or hasn't closed the table
properly
Note that no such warning occurs when I issue a SELECT query.
I can clean up the warning by issuing a "check table",
Hi.
I hope I've solved problem with mysql.
I've contacted with my motherboard vendor (Asus) and technical support suggest
me to upgrade bios. It is standard answer IMHO :), I haven't believed it can
help. But it helped. Now everything looks OK.
I'm sorry that I couse confusion.
Best regards.
On Thu, Nov 15, 2001 at 10:13:34AM +0200, Michael Widenius wrote:
> There could also be a bug in the checksum handling in MyISAM.
>
> I did fix something with checksum handling in 3.23.43; Could you
> please try 3.23.44 and see if this helps.
>
I've escalated problem to linux-kernel becouse my
Hi!
> "Sinisa" == Sinisa Milivojevic <[EMAIL PROTECTED]> writes:
Sinisa> Grzegorz Paszka writes:
>> On Mon, Nov 12, 2001 at 07:21:07PM +0200, Sinisa Milivojevic wrote:
>> Another is as I wrote above. New database with content from
>> data source is also broken. I know that is sounds strang
Grzegorz Paszka writes:
> On Mon, Nov 12, 2001 at 07:21:07PM +0200, Sinisa Milivojevic wrote:
>
> Before I wrote to this list I read manual. Especially chapter 4.4 .
>
> I've done what You suggested but it didn't help. (Stage 3: Difficult repair).
> That's one problem.
>
> Another is as I wrot
On Mon, Nov 12, 2001 at 07:21:07PM +0200, Sinisa Milivojevic wrote:
> Grzegorz Paszka writes:
> >
> > Yes, I say more, that I created new database and filled it by perl script from
>data source and I have the same situation. I think that is the best way of rebuild
>index file :)
>
> See in our
Grzegorz Paszka writes:
>
> Yes, I say more, that I created new database and filled it by perl script from data
>source and I have the same situation. I think that is the best way of rebuild index
>file :)
>
> So what I should do in this case ?
>
> --
> Grzegorz
>
See in our manual what to
s index: 2
> > Key: 2: Keyblocks used: 65% Packed: 60% Max levels: 7
> > Total:Keyblocks used: 69% Packed: 56%
> >
> > - check record links
> > myisamchk: error: Checksum for key: 2 doesn't match checksum for records
> >
> > Record blocks:
eferences index: 1
> Key: 1: Keyblocks used: 98% Packed:0% Max levels: 4
> - check data record references index: 2
> Key: 2: Keyblocks used: 65% Packed: 60% Max levels: 7
> Total:Keyblocks used: 69% Packed: 56%
>
> - check record links
> myisamchk: e
Hello All,
When repairing a MySql table, I keep getting following error:
'mydatabase.MYD' doesn't have a correct index definition
What exactly does this mean or what needs to be done to correct it?
Mike(mickalo)Blezien
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Thunder Rain Internet Publishing
P
Hi !
I got a power failure on my database machine and now I cant start it
since I got a error 22 when I start it.
How do I fix this? And what does error 22 mean?
I looked at http://www.mysql.com/doc/R/e/Repair.html but nothing there
seems to fix it.
//eric
27 matches
Mail list logo
