nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Do we have to convert MySQL from MYISAM to InnoDB

Thomas Zöger_vsg3kp

We have our current version of confluence 6.2.1 upgraded to 6.3.3 and now we get an error

"MyISAM is configured as the default storage engine in your database, wh..."

Problem there is, this system runs on a managed hosting server with no chance to change to innodb db environments. All tables are already innodb.

Question: is there a way to disable this innodb needed check?

otherwise we can not run confluence anymore.

kindly regards

Accepted answers

All comments

Nic Brough -Adaptavist-

No. You must be using Innodb tables.

However, this is just a warning that your defaults are not suitable. If your tables really are all Innodb for the confluence database, you can simply ignore it.

Thomas Zöger_vsg3kp

No it's not only a warning. after the startup was finished with running, the browser shows the following page:

Bildschirmfoto 2017-09-01 um 07.27.39.png

logfile contains:

..,803 ERROR [localhost-startStop-1] [atlassian.confluence.setup.BootstrapApplicationStartupListener] checkConfigurationOnStartup MyISAM is configured as the default storage engine in your database, which may result in data integrity issues. Please see http://confluence.atlassian.com/x/voTcDQ for more information.

Nic Brough -Adaptavist-

Ah, right. It is theoretically possible to run a set of databases differently, so it can be possible to set up one database with Innodb as the default and leave the *global* default as MyIsam, which gives you this as a warning. It's rare to do this, I'm only familiar with the global flag.

However in your case, it's set incorrectly for your database, not just globally.

Your hosting provider needs to change the default to InnoDB for this database, or you will need to find a new host.

Thomas Zöger_vsg3kp

No, our hosting partner could not change our db environments for other reasons too. That is our problem we need to fix. It was running with 6.2.1 and 6.3.3 makes this problems. how to let confluence ignore this check?