Nader Jafari 5 Years Ago Data migration was a great tool in liferay 6 and removing this feature was wrong. I think this help us by migrating core tables that was the largest part of data and then we can migrate my custom porlets tables manualy. Although I remember that data migration was based on models, which could have migrated all the portlets. Please sign in to reply. Reply as... Cancel David H Nebinger Nader Jafari 5 Years Ago Well, unfortunately most users expected a perfect solution rather than as a basic starting point. It caused more support issues than it solved. Besides, when you get a look at some of the third party tools, you can find some really elegant solutions that can deal with the whole conversion, rather than just part. Please sign in to reply. Reply as... Cancel
David H Nebinger Nader Jafari 5 Years Ago Well, unfortunately most users expected a perfect solution rather than as a basic starting point. It caused more support issues than it solved. Besides, when you get a look at some of the third party tools, you can find some really elegant solutions that can deal with the whole conversion, rather than just part. Please sign in to reply. Reply as... Cancel
Tony Bigby 4 Years Ago I've just migrated a system from Hypersonic to MariaDB using David's 'Manual Migration' recommendations. Depending on your environment the below may or may not be the case, however in my case I also had to: 1. In the SQL insert statement import, I had to convert the table names from all uppercase (Hypersonic) to mixed case (MariaDB), before the INSERT commands would find the table to insert into. I couldn't find a quick process to do that so ended up with find/replace of the table names for each table in the SQL script. 2. The Unicode text wasn't converted automatically on import into MariaDB so HSQL data like '\u000d' was imported into MariaDB as the literal text rather than a single Unicode character (even though the DB was in UTF8MB4 mode). I used Notepad++ HTMLTag plugin to convert the SQL script as described in: https://stackoverflow.com/a/39126723 3. On startup the Liferay then failed to start with configuration errors after 'Starting initial bundles'. I traced this back to the values in the 'Configuration_' table in the database. In particular this seemed to be issues of having an equals sign in quoted text - these needed a backslash added. Eg. from: osgi.jaxrs.application.select="(osgi.jaxrs.extension.select=\(osgi.jaxrs.name=jaxb-json\))" to: osgi.jaxrs.application.select="(osgi.jaxrs.extension.select\=\\(osgi.jaxrs.name\=jaxb-json\\))" Same thing in one entry that had: mapping=["DELETE,PATCH,POST,PUT=everything,everything.write" ... Hope this helps anyone in the same scenario. Cheers, Tony Please sign in to reply. Reply as... Cancel David H Nebinger Tony Bigby 4 Years Ago - Edited Ugh, HSQL migrations can be especially painful. It's the big reason Liferay actually puts in your log, "Hey, you're using HSQL but you really shouldn't in production..." If I could ask, Tony, how you might have missed that message and what, if anything, might have been done to stop you from getting to that situation in the first place? Please sign in to reply. Reply as... Cancel Tony Bigby David H Nebinger 4 Years Ago Hi David - it's just a Dev server and we didn't realise that it would need proper DB access down the line. Don't worry, our prod and non-prod servers do use a DB. But when I started, your blog made it look easier to do the migration than re-add all dev deployments, users, sites, pages, roles, etc. Thankfully it only took a few hours even with figuring out those notes. Cheers, Tony Please sign in to reply. Reply as... Cancel
David H Nebinger Tony Bigby 4 Years Ago - Edited Ugh, HSQL migrations can be especially painful. It's the big reason Liferay actually puts in your log, "Hey, you're using HSQL but you really shouldn't in production..." If I could ask, Tony, how you might have missed that message and what, if anything, might have been done to stop you from getting to that situation in the first place? Please sign in to reply. Reply as... Cancel Tony Bigby David H Nebinger 4 Years Ago Hi David - it's just a Dev server and we didn't realise that it would need proper DB access down the line. Don't worry, our prod and non-prod servers do use a DB. But when I started, your blog made it look easier to do the migration than re-add all dev deployments, users, sites, pages, roles, etc. Thankfully it only took a few hours even with figuring out those notes. Cheers, Tony Please sign in to reply. Reply as... Cancel
Tony Bigby David H Nebinger 4 Years Ago Hi David - it's just a Dev server and we didn't realise that it would need proper DB access down the line. Don't worry, our prod and non-prod servers do use a DB. But when I started, your blog made it look easier to do the migration than re-add all dev deployments, users, sites, pages, roles, etc. Thankfully it only took a few hours even with figuring out those notes. Cheers, Tony Please sign in to reply. Reply as... Cancel