Status of bugs

2003-12-15 Thread Jim Gallagher
Hello,

Last month I posted here a question (with no responses) about a problem I am having 
with myisamchk ("myisamchk Error 22 WinServer 2003 Large table").  My problem seems to 
be identical to that described here:

http://bugs.mysql.com/bug.php?id=779

However, that bug was for the 3.x version of MySQL and I am experiencing the problem 
with 4.x.  The bug has been marked as closed, with the comment that the fix has been 
incorporated in the code.   Is there any way short of paying $1500 to find out what 
the status of this bug is in version 4?  I'm not exactly asking for charity - my 
company has bought 4 licenses.  I know that the source code is available for me to fix 
it myself, but I'm not a database programmer, or even a C programmer, so that isn't a 
reasonable option.  I don't have any kind of C development environment set up.

-Jim Gallagher



--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



Re: myisamchk Error 22 WinServer 2003 Large table

2003-11-20 Thread Jim Gallagher
Hello,

Further searching for this problem reveals that it was reported as a bug:

http://bugs.mysql.com/bug.php?id=779

but for Version 3.  Does this mean that the fix was not implemented in Version 4?

What is the workaround for this?  Do I have to load the table while creating the 
indices?  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 just not the right RDB to be using for tables this size?

-Jim Gallagher





>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: 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 machine.

>What am I doing wrong?  I'm new to MySQL, and am just finding my way.  The command 
>I'm issuing is:

>myisamchk -O sort_buffer_size=512M -O key_buffer_size=768M -O read_buffer_size=512M 
>-O write_buffer_size=512M -rq d:\mysql\data\mydb\mytable

>I have 4GB of memory on the machine.

>I searched for this problem with Google and found several others with the same 
>problem, but didn't find a solution.

>Thanks,

>Jim Gallagher



--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



myisamchk Error 22 WinServer 2003 Large table

2003-11-19 Thread Jim Gallagher
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: 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 machine.

What am I doing wrong?  I'm new to MySQL, and am just finding my way.  The command I'm 
issuing is:

myisamchk -O sort_buffer_size=512M -O key_buffer_size=768M -O read_buffer_size=512M -O 
write_buffer_size=512M -rq d:\mysql\data\mydb\mytable

I have 4GB of memory on the machine.

I searched for this problem with Google and found several others with the same 
problem, but didn't find a solution.

Thanks,

Jim Gallagher



--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



myisamchk Error 22 WinServer 2003 Large table

2003-11-17 Thread Jim Gallagher
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: 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 machine.

What am I doing wrong?  I'm new to MySQL, and am just finding my way.  The command I'm 
issuing is:

myisamchk -O sort_buffer_size=512M -O key_buffer_size=768M -O read_buffer_size=512M -O 
write_buffer_size=512M -rq d:\mysql\data\mydb\mytable

I have 4GB of memory on the machine.

I searched for this problem with Google and found several others with the same 
problem, but didn't find a solution.

Thanks,

Jim Gallagher



--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]