Re: problem open a innodb table

Dont you have mysql dump file for those table? It is best way to restore InnoDB tables. 2011/1/7 Elim PDT > I messed up the ibdata1,ib_logfile1,0 files and encounter the problems of > openning innodb tables even after I copied the back-up files of few months > ago. I don't have many innodb tabl

problem open a innodb table

I messed up the ibdata1,ib_logfile1,0 files and encounter the problems of openning innodb tables even after I copied the back-up files of few months ago. I don't have many innodb tables and so this not causing too much trouble. I don't know what to do for restoring those tables, and not even kno

Re: cleaning up general_log table?

Hi Ronaldo, After some digging I did find a way! USE mysql; CREATE TABLE gn2 LIKE general_log; RENAME TABLE general_log TO oldLogs, gn2 TO general_log; the rename is atomic, so it is quick, there is no need to stop the server. After that, oldLogs is very easy to mess up with thanks, Jacek

RE: cleaning up general_log table?

Since that table is a MyISAM table, you must do the following: 01. In mysql, CREATE DATABASE IF NOT EXISTS mystuff; 02. service mysql stop 03. cd /var/lib/mysql/mysql 04. mv general_log.* ../mystuff 05. comment out general log from my.cnf 06. service mysql start 07. In mysql, DELETE FROM mystuff.g

cleaning up general_log table?

Hello, Is there a way to purge parts of general log table without interrupting the server? Ideally, we would like to transfer older logs (say copy all entries from 2010 into a separate location, and then run: DELETE FROM mysql.general_log WHERE event_time<'2011-01-01' However this yields an err

Efficient Blobbing?

I am dealing with blobs up to - I estimate - about 100 kilo bytes in size. Storage engine: InnoDB Frontend: PHP Some questions: * I've read somewhere that it's not good to update blobs, because it leads to reallocation, thus fragmentation, thus bad performance. Is that true? Any reference

Efficient Blobbing?

I am dealing with blobs up to - I estimate - about 100 kilo bytes in size. Storage engine: InnoDB Frontend: PHP Some questions: * I've read somewhere that it's not good to update blobs, because it leads to reallocation, thus fragmentation, thus bad performance. Is that true? Any reference o

Efficient Blobbing?

I am dealing with blobs up to - I estimate - about 100 kilo bytes in size. Storage engine: InnoDB Frontend: PHP Some questions: * I've read somewhere that it's not good to update blobs, because it leads to reallocation, thus fragmentation, thus bad performance. Is that true? Any reference on

Re: MySQL raw files to .SQL

Hmm, no I had not. Does this mean that there is no native way to do it? (that would be my preference.) Sent from my iPad On Jan 1, 2011, at 12:27 PM, Wagner Bianchi wrote: > Did a tried MaatKit? MaatKit let you control over the number of threads > dedicated to extract a MySQL backup. > > Best

Re: Stored procedure

HI All Thank you for the responses. I have been going through the documentation the whole of today thus far and it seems to be easy enough. I am still however confused on how to achieve the following though , and this might be due to a lack of experience or I might just not

Re: mysql 5.5 optimize changes?

As per usual, I seem to have found the answer after asking for help... It seems our team did not cleanly remove the old centos packaged versions, or perhaps there is a bug in the removal scripts. As such, an incorrect mysqlcheck binary was running and that somehow caused the problems.

mysql 5.5 optimize changes?

Hello. Our team has upgraded a few of our mysql servers from 5.0.77 on centos to 5.5.8. Since then mysqlcheck -Ao has been failing with permissions errors: mysqlcheck: Got error: 1142: SELECT,INSERT command denied to user 'root'@'localhost' for table 'XXX' when executing 'OPTIMIZE TABLE ...