Documentation Home
MySQL 5.6 Reference Manual
Related Documentation Download this Manual
PDF (US Ltr) - 31.1Mb
PDF (A4) - 31.1Mb
PDF (RPM) - 30.3Mb
EPUB - 7.7Mb
HTML Download (TGZ) - 7.5Mb
HTML Download (Zip) - 7.6Mb
HTML Download (RPM) - 6.5Mb
Eclipse Doc Plugin (TGZ) - 8.3Mb
Eclipse Doc Plugin (Zip) - 10.1Mb
Man Pages (TGZ) - 182.4Kb
Man Pages (Zip) - 293.8Kb
Info (Gzip) - 2.9Mb
Info (Zip) - 2.9Mb
Excerpts from this Manual

MySQL 5.6 Reference Manual  /  The InnoDB Storage Engine  /  InnoDB Configuration
User Comments
  Posted by Brian Krispinsky on April 14, 2005
I've found quite a few people having issues initializing MySQL 4.0.x with InnoDB support under Suse 9.x Pro. Server startup will fail with a message like:

unknown variable 'innodb_data_home_dir=/var/lib/mysql'

If this happens, make sure you've installed the mySQL-Max package (after installing the base mySQL server). Then invoke the server like:

$ /usr/sbin/mysqld-max

You should then see your InnoDB tables initialize.
  Posted by Jose Pablo Ezequiel Fernandez Silva on July 12, 2005
InnoDB on Gentoo is not enabled unless you specify the "innodb" USE flag. Knowing this may save you from having to do an extra compilation.
  Posted by Jaime Montoya on January 8, 2006
Hola, la forma de activar las tablas innodb en mysql 3.23.54 me funciono de esta forma usando Red Hat Linux 9:

Primero me fui a /etc/my.cnf, y agregue algunas lineas que me faltaban en ese archivo de modo que al final quedara de esta manera:

# skip_innodb
set-variable = innodb_buffer_pool_size=80M
set-variable = innodb_additional_mem_pool_size=2M
set-variable = innodb_log_file_size=20M
set-variable = innodb_log_buffer_size=8M



Espero que les sirva y si tienen preguntas me escriben a, adios.
  Posted by Toby Thain on April 9, 2006
Per Jose's comment on Gentoo above - on my Gentoo system, the USE flags depend on the version of MySQL you are installing:

mysql-3.23.58-r1 : 'innodb' flag enables InnoDB support
mysql-4.0.25-r2 through mysql-5.0.19 include InnoDB support by default. After 5.1 this was again made dependent on flag 'innodb'.

If installing 4.1.3 or later you can use the 'extraengine' flag to enable ARCHIVE, CSV (4.1.4+), BLACKHOLE (4.1.11+) and FEDERATED (5.0.3+). (Also see 'berkdb', 'cluster' and 'geometry' flags.)
  Posted by Jon Evans on December 11, 2006
Another thing to watch for with Gentoo is the way it configures the max file size to 128M:

[extract from /etc/mysql/my.cnf]
# you may wish to change this size to be more suitable for your system
# the max is there to avoid run-away growth on your machine
innodb_data_file_path = ibdata1:10M:autoextend:max:128M

If you start getting "Table 'foo' is full" errors, check your config file.
  Posted by David Toth on December 11, 2006
This is kind of a got ya and either isn't in the documentation or is as clear as mud. When you want to change the location of the innodb data files you have to set both the innodb_data_home_dir and innodb_data_file_path variables. So in my case, I was trying to move the data file location to /History/mysql. So I tried adding to my.cnf


Upon starting mysql, I got an error unable to open database. When I looked in syslog, the innodb_data_file_path looked like this

I added to the my.cnf


and modified innodb_data_file_path to


and mysql started up using the correct file paths. Remember to change the permissions on the /History/mysql directory to chown mysql:mysql mysql. All is well and I was also able to change the log file locations as well.
  Posted by Charly Molter on July 18, 2013
From this part of the doc:
# Set key_buffer to 5 - 50% of your RAM depending on how much
# you use MyISAM tables, but keep key_buffer_size + InnoDB
# buffer pool size < 80% of your RAM
It is not really clear but 'key_buffer_size' is a MyISAM parameter so the sentence above means that the more you use MyISAM table the higher key_buffer_size should be.

It wasn't really clear to me at the beginning.

Sign Up Login You must be logged in to post a comment.