| Bug #17612 | AIX5.2 64Bit InnoDb storage engine gets disabled | ||
|---|---|---|---|
| Submitted: | 21 Feb 2006 13:09 | Modified: | 10 Dec 2007 13:06 |
| Reporter: | Matthias Leich | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Compiling | Severity: | S1 (Critical) |
| Version: | 5.1 | OS: | IBM AIX (aix 5.2, 64 bit only) |
| Assigned to: | CPU Architecture: | Any | |
[11 Apr 2006 15:15]
Magnus Blåudd
This happens quite frequently in Pushbuild for mysql-5.1-new https://intranet.mysql.com/~knielsen/pb/mysql-5.1-new/ Look at my two pushes "Tue Apr 11 11:48:41 2006 msvensson" and "Tue Apr 11 15:09:23 2006 msvensson". The first one have only 2 failing test case and the second has 7 and all the innodb test have been skipped.
[2 Jun 2006 11:10]
Joerg Bruehe
Re-occurs in 5.1.11-beta.
[27 Jul 2006 15:09]
Heikki Tuuri
Hi! Is this still a problem? Looking at innodb_flush_method code in mysqld.cc I could not see anything special about how this char* option is declared there. --Heikki
[6 Sep 2006 10:05]
Heikki Tuuri
Changing the category to Compiling.
[4 Dec 2007 10:17]
Valeriy Kravchuk
Please, try to check with a newer version, 5.1.22, and inform about the results.
[6 Dec 2007 19:05]
Matthias Leich
Sorry, I cannot give feedback because I am not running and observing builds on AIX. The problem happens randomly during these builds and will than be reported by build team members. But I can offer to write a test (if doable) which fails if the phenomenon SHOW VARIABLES; Variable_name Value ..... innodb_flush_method <not reasonable value like ^A> happens.
[10 Dec 2007 13:06]
Susanne Ebrecht
I'll close this, because I can't reproduce the issues with 5.1.21
mysql> SHOW VARIABLES;
....
| innodb_flush_log_at_trx_commit | 1
| innodb_flush_method |
| innodb_force_recovery | 0
....
mysql> show storage engines\G
*************************** 1. row ***************************
Engine: InnoDB
Support: YES
Comment: Supports transactions, row-level locking, and foreign keys
Transactions: YES
XA: YES
Savepoints: YES
...
InnoDB isn't disable in that version.
No errors are logged.
For testing I used mysql-5.1.21-beta-aix5.2-powerpc-64bit.tar.gz
Thank you for your bug report. This issue has already been fixed in the latest released version of that product, which you can download at
http://www.mysql.com/downloads/
Description: The release was build with InnoDB enabled. SHOW VARIABLES; Variable_name Value auto_increment_increment 1 ..... innodb_flush_method ^A The "^A" looks very suspicious. Test on x86 32 Bit Linux gives there an empty string. .... show storage engines; Engine Support Comment Transactions XA Savepoints MEMORY YES Hash based, stored in memory, useful for temporary tables NO NO NO ..... InnoDB DISABLED Supports transactions, row-level locking, and foreign keys YES YES YES Test on x86 32 Bit Linux gives here 'YES' instead of disabled. InnoDB YES Supports transactions, row-level locking, and foreign keys ...... Further tests on AIX 5.2 64 Bit show that all tables which have to be created with InnoDB as storage engine get MyISAM instead + Warning which tells that this replacement was done. Other test containing "--source include/have-innodb.inc" get skipped. Content of var/log/master.err: CURRENT_TEST: ml001 060221 16:06:19 [Warning] /home/mysqldev/aix52-64bit/test/mysql-5.1.8-beta-aix5.2-powerpc-64bit/bin/mysqld: unknown variable 'loose-binlog-show-x id=0' 060221 16:06:19 [Warning] /home/mysqldev/aix52-64bit/test/mysql-5.1.8-beta-aix5.2-powerpc-64bit/bin/mysqld: unknown variable 'loose-binlog-show-x id=0' InnoDB: Unrecognized value ^A�for innodb_flush_method ............ MySQL release is: SELECT VERSION(); VERSION() 5.1.8-beta-log How to repeat: Please execute the statements above.