RE: InnoDB problem.

: Re: InnoDB problem. 2013/7/23 Rick James mailto:rja...@yahoo-inc.com>> Did you change innodb_log_file_size? innodb_log_file_size error always appears in the logs...he only posted a few lines of his log...but I guess (or I want to believe) he's gone through the whole log before s

Re: InnoDB problem.

; > -Original Message- > > From: Johan De Meersman [mailto:vegiv...@tuxera.be] > > Sent: Tuesday, July 23, 2013 9:57 AM > > To: Luis H. Forchesatto; mysql list > > Subject: Re: InnoDB problem. > > > > Eek. > > > > No immediate clue here, bu

RE: InnoDB problem.

Did you change innodb_log_file_size? > -Original Message- > From: Johan De Meersman [mailto:vegiv...@tuxera.be] > Sent: Tuesday, July 23, 2013 9:57 AM > To: Luis H. Forchesatto; mysql list > Subject: Re: InnoDB problem. > > Eek. > > No immediate clue here,

Re: InnoDB problem.

ssage - > From: "Luis H. Forchesatto" > To: "Johan De Meersman" > Sent: Tuesday, 23 July, 2013 6:34:47 PM > Subject: Re: InnoDB problem. > The error log: > 130723 10:04:23 [ERROR] Plugin 'InnoDB' init function returned error. > 130723 10:04:23 [E

Re: InnoDB problem.

What's the MySQL error log have to say? - Original Message - > From: "Luis H. Forchesatto" > To: "Johan De Meersman" > Sent: Tuesday, 23 July, 2013 3:39:55 PM > Subject: Re: InnoDB problem. > Yep, I do backup of /home/mysql/ib* files too :D &g

Re: InnoDB problem.

- Original Message - > From: "Luis H. Forchesatto" > Subject: InnoDB problem. > > Permission and owner of the table files (.frm files) are ok, since it > recognizes MyISAM tables (they have the same permission). Oops. You should always read the fine manual. You took file-level backups,

Re: InnoDB: Problem with innobackup

James, page number 22357 is corrupt. InnoDB Hot Backup notices these checksum errors, and refuses to do the backup. Sometimes it happens that an unused (i.e., freed) page in an ibdata file becomes corrupt. Then it would be nice to have some tool to reset the checksums on that page, so that mysql

Re: InnoDB: Problem with innobackup

James, We've had this issue twice (every 4 months) - running on 4.0.20 - due to an old kernel (we just upgraded the kernel after the last issue). Do you have a replicated (slave) database? We shut down the master and then the slave (a few minutes after the master to let all changes propigate),

Re: innodb problem

Matteo, - Original Message - From: <[EMAIL PROTECTED]> Newsgroups: mailing.database.myodbc Sent: Friday, February 04, 2005 3:51 PM Subject: innodb problem Hello, my name's Matteo, probably my question is basic but I'm new with mysql. I've an application that write some milion of row in m

Re: innodb problem

Hello. Use the max attribute. See: http://dev.mysql.com/doc/mysql/en/innodb-configuration.html If you want to decrease the size of your tablespace, see: http://dev.mysql.com/doc/mysql/en/adding-and-removing.html [EMAIL PROTECTED] wrote: > Hello, my name's Matteo, probably my questi

Re: InnoDB problem, yet performance increased!?

You can determine table type with SHOW CREATE TABLE table_name or SHOW TABLE STATUS LIKE 'table_name'; From the manual , "If a storage engine is specified that is not available, MySQL uses MyISAM instead." That applies to ALTER as well as

Re: InnoDB problem, yet performance increased!?

In article <[EMAIL PROTECTED]>, James Green <[EMAIL PROTECTED]> writes: > Unfortunately when we repeated on the live server, whilst we got a > 200% performance boost (estimate) again, we failed to notice that > innodb is in DISABLED state, and yet alter table returned ok. It's one of the ugliest

re: InnoDB Problem

On Tuesday 18 March 2003 02:26, Custódio de Matos Lima wrote: > Im having some troubles when creating the foreign key > constraints in a InnoDB database. The problem is, i > can create the InnoDB table, but im having a little > difficult to make the connections with other tables. > > The error th

Re: innodb problem

Massimo, Tuesday, July 16, 2002, 1:02:15 PM, you wrote: MP> I am a new user of mysql MP> I installed 3.23.51 on my nt MP> this is my my.ini files. MP> [mysqld] MP> innodb_data_home_dir = MP> innodb_data_file_path = ibdata1:30M:autoextend MP> default-table-type=innodb MP> [WinMySQLAdmin] MP> S

RE: innodb problem (with JDBC/transactions)

Hi, We are currently facing the same problem (Deadlock found when trying to get lock; Try restarting transaction) in our production environnement. We are using InnoDB tables (mysqk 3.23.48-max) with Jboss 2.4.4 and JDBC driver mm.mysql-2.0.11-bin.jar / RedHat 7.1. Could you please tell me how to f

RE: innodb problem (with JDBC/transactions)

all COMMIT to release the locks. > JDBC Driver: mm.mysql-2.0.6.1.jar > MySQL: mysql-max-3.23.42-win > >Thanks, > >Erik Regards, Heikki http://www.innodb.com >-Original Message- >From: Heikki Tuuri [mailto:[EMAIL PROTECTED]] >Sent: Friday, October 19, 2

RE: innodb problem (with JDBC/transactions)

e. PLEASE HELP! JDBC Driver: mm.mysql-2.0.6.1.jar MySQL: mysql-max-3.23.42-win Thanks, Erik -Original Message- From: Heikki Tuuri [mailto:[EMAIL PROTECTED]] Sent: Friday, October 19, 2001 3:11 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: innodb problem (

Re: innodb problem (with JDBC/transactions)

Erik, run the MySQL server mysqld from a command prompt and do with the mysql client: mysql>create table innodb_lock_monitor(a int) type = innodb; (assuming you run a recent version). Then mysqld will print lock information to the standard output and you see what is happening. Regards, Heikk

RE: innodb problem (with JDBC/transactions)

--- Original Message - From: "Heikki Tuuri" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, October 10, 2001 7:34 PM Subject: Re: innodb problem > Hi! > > >Thanks for your help, but starting the innodb_lock_monitor with > > > >mysql&g

RE: InnoDB problem

al Message- From: Heikki Tuuri [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 16, 2001 11:24 AM To: Jamie Krasnoo; [EMAIL PROTECTED] Subject: RE: InnoDB problem Jamie, really strange. Now I start to suspect the file system. InnoDB should create and write a file of size 2000 MB like you sp

RE: InnoDB problem

Jamie, really strange. Now I start to suspect the file system. InnoDB should create and write a file of size 2000 MB like you specified in my.cnf. InnoDB does the initial file write in 1 MB chunks using pwrite, calling fsync in between. When you restart MySQL, InnoDB checks if the data file is