[solved] OTRS4 and MySQL 5.5: problem with innodb_log_file_size when MyISAM used

Moderator: crythias

Locked
ASY
Znuny newbie
Posts: 8
Joined: 23 Nov 2012, 10:54
Znuny Version: 3.1.10
Real Name: Sergey
Location: Russia, Samara

[solved] OTRS4 and MySQL 5.5: problem with innodb_log_file_size when MyISAM used

Post by ASY »

Hello.

I attempted to install OTRS 4.0.7 with MySQL/MyISAM, but I got error when check database:

Error: Please set the value for innodb_log_file_size on your database to at least 256 MB (current: 0 MB, recommended: 512 MB). For more information, please have a look at http://dev.mysql.com/doc/refman/5.6/en/ ... ation.html.

Is MyISAM not supported now or is it a bug ?
Last edited by ASY on 25 Apr 2015, 19:03, edited 1 time in total.
Giulio Soleni
Znuny wizard
Posts: 392
Joined: 30 Dec 2010, 14:35
Znuny Version: 6.0.x and 5.0.x
Real Name: Giulio Soleni
Company: IKS srl

Re: OTRS4 and MySQL 5.5: problem with innodb_log_file_size when MyISAM used

Post by Giulio Soleni »

Hi,
from OTRS 3.3 onwards new tables created in the MySQL UPGRADING process will be created with the default table storage engine set in your MySQL server. In MySQL 5.5 the new default type is InnoDB.

As specified in the upgrading instruction at § 6.1 You have two options: you can change the default storage engine of MySQL back to MyISAM so that new tables will have the same engine as the existing tables, or change the existing tables to use InnoDB as storage engine.

In my humble opinion, changing to InnoDB is the best option.

There's a script you may use to perform the migration: bin/otrs.MySQLInnoDBSwitch.pl

You may also take a look to this thread in the forum for some details on db migration.
OTRS 6.0.x on CentOS 7.x with MariaDB 10.2.x database connected to an Active Directory for Agents and Customers.
ITSM and FAQ modules installed.
ASY
Znuny newbie
Posts: 8
Joined: 23 Nov 2012, 10:54
Znuny Version: 3.1.10
Real Name: Sergey
Location: Russia, Samara

Re: OTRS4 and MySQL 5.5: problem with innodb_log_file_size when MyISAM used

Post by ASY »

Giulio Soleni wrote:from OTRS 3.3 onwards new tables created in the MySQL UPGRADING process will be created with the default table storage engine set in your MySQL server. In MySQL 5.5 the new default type is InnoDB.
I known and I use "default-storage-engine=MYISAM" in my.cnf:

Code: Select all

mysql> show variables like 'storage_engine';
+----------------+--------+
| Variable_name  | Value  |
+----------------+--------+
| storage_engine | MyISAM |
+----------------+--------+
Giulio Soleni wrote: You may also take a look to this thread in the forum for some details on db migration.
This is new installation. As for InnoDB I thik what it requires greater care in work. MyISAM allows less caution in work...
ASY
Znuny newbie
Posts: 8
Joined: 23 Nov 2012, 10:54
Znuny Version: 3.1.10
Real Name: Sergey
Location: Russia, Samara

Re: OTRS4 and MySQL 5.5: problem with innodb_log_file_size when MyISAM used

Post by ASY »

I installed OTRS4 with InnoDB now. But I'm not sure what this is a good idea for me.

http://bugs.otrs.org/show_bug.cgi?id=11208

The patch for MyISAM was attached to this bug.
Locked