Posted on 10-19-2016 12:51 PM
This was mentioned in the presentation as it moves from a table lock to row lock process.
Wondering if any have done this and what steps you took to complete.
We have found references:
http://www.ryadel.com/en/mysql-convert-all-tables-of-one-or-more-databases-to-myisam-or-innodb/
Posted on 09-26-2018 10:51 AM
@kerouak I filed a bug for this... basically it's assuming you are starting and stopping your Linux services with systemctl however that's not always the case, you might find that your Linux distro is using service instead
So try restarting your database this way...
Make sure your Tomcat instance(s) have stopped first:
sudo service jamf.tomcat8 stop
Now restart the databse:
sudo service mysql restart
Now start up Tomcat:
sudo service jamf.tomcat8 start
YMMV
Posted on 10-04-2018 08:06 PM
@brunerd did that actually work for you as far as conversion? I had the same issue, and after restarting mysqld and checking most of the tables were still myisam...
Posted on 10-05-2018 06:08 AM
@chris.kemp The current version of the jamf-pro tool fails to complete the InnoDB conversion on RHEL systems, so you have to do a manual conversion. Contact your TAM/Jamf Buddy/Customer Success Specialist/Whatever they're called today for the procedure.
Posted on 10-10-2018 02:35 AM
@Hugonaut Thanks for the very useful article I think it missed only in your process the reimport of the dump
MYSQL PATH HERE -u root -p PASSWORDHERE < jamfsoftware_innodb.sql
Best and many thanks
Benoit
Posted on 10-10-2018 05:35 AM
Thank you @bdelamarche for correcting the post! I updated my post..its only the most crucial part of the conversion haha. & You're welcome. Glad to help