Tweet
The table configdb_sequence of ConfigDB schema still has no defined ENGINE in its create statement. So for that table the configured default ENGINE of MySQL will be used. Normally this is MyISAM which is not good of a table generating unique identifier.
Now the create statement comes with a definition for the ENGINE of that table. This can not be changed automatically for existing installations because update tasks for the ConfigDB are not implemented yet.
The administrator has to change that by hand. Connect to your MySQL database with the following command:
mysql -h <master-db-host> -u <db-login> -p<db-password> configdb
The values to replace are configured e.g. in /opt/open-xchange/etc/groupware/configdb.properties if you do not remember them.
When connected to MySQL ConfigDB Scheme execute the following SQL statement to correct the definition of table configdb_sequence:
ALTER TABLE configdb_sequence ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;
Now the create statement comes with a definition for the ENGINE of that table. This can not be changed automatically for existing installations because update tasks for the ConfigDB are not implemented yet.
The administrator has to change that by hand. Connect to your MySQL database with the following command:
mysql -h <master-db-host> -u <db-login> -p<db-password> configdb
The values to replace are configured e.g. in /opt/open-xchange/etc/groupware/configdb.properties if you do not remember them.
When connected to MySQL ConfigDB Scheme execute the following SQL statement to correct the definition of table configdb_sequence:
ALTER TABLE configdb_sequence ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;