Re: Repairing packed MyISAM tables with no index file (.MYI)

this /usr/local/mysql/bin/myisamchk -rq (table name) troubleticket.* This might help you. Kayra Otaner wrote: Hello, I have been using myisampack to pack old MyISAM tables to archive huge amounts of data. To save more space I decided to get rid of index (.MYI) files based

Repairing packed MyISAM tables with no index file (.MYI)

. Any idea on what is going on? Did I hit to a bug? Thanks. Kayra Otaner -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: Unbelieveable with 4 Gbytes - MySQL 5 only 350 concurrent mysql connection... on Linux Redhat 9

be the reason why you're seeing can't create new thread. Kayra Otaner On Fri, 2006-02-24 at 20:51 +0700, Ady Wicaksono wrote: I have MySQL 5 installed on My Machine, But it could handle only max about 350 concurrent mysql connection Unbelieveable, i have 4 Gbytes, but on the next 351

Index merge optimization with joined tables?

L table has 9 million rows Explain plan only shows ref eq_ref type optimization is being used. M table has 2 key fields used in the joins and only one is used. Tables are InnoDB, total size of the tables is around 9G. I'm using MySQL max 5.0.16 Any suggestions? Thank you Kayra Otaner

Re: Optimization suggestions when only using Innodb

Please see my comments below : On Thu, 2005-12-01 at 14:06 -0600, Ross Anderson wrote: I have read the suggestions for optimization for innodb however I'm curious if anyone can help me understand which buffers are common (thus used by innodb action) and which are specific to myiasm. The

Re: MySQL Replicaiton

that you have entered your password correctly to /etc/my.cnf file. You can chance your replication user's password by typing change master to master_user = 'repl', master_password = 'PASSWORD' After all these steps type 'start slave' on slave server to see if it is working. Kayra Otaner

Re: Optimizing Mysql for large tables

suggestions can be : 1 - Add indexes to your tables and use that indexes when you're selecting rows. 2 - increase key_buffer_size to 32 or 64 or even more depending on your server memory 3- Add memory to your server if you have less then 256 Mb and willing to have fast db performance. Kayra Otaner

MySQL 4.0.13 Memory Problem on heavy load

tables? Should I increase key_buffer_size to 32Mb or more? Key_buffer_size doesn't look like a problem since key efficiency looks 100% most of the time. Thank you for your time Kayra Otaner - This mail sent through IMP: http

Re: DIFFERENTIAL BACKUPS

of lines. Last step compresses diff file using bzip2 and securely transfer to a designated backup server. #!/bin/bash # Copyright (C) 2002-2003 Kayra Otaner [EMAIL PROTECTED] # This software may be freely redistributed under the terms of the GNU # public license. # # MySQL differential backup script

MySQL 4.0.13 Memory problem under heavy load

key_buffer_size to 256Mb or more? Key_buffer_size doesn't look like a problem since key efficiency looks 100% most of the time. Thank you for your time Kayra Otaner -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http