We are currently running Liferay 6.0.6 connected to Oracle 11.2.0.2.0. Due to business requirements around licensing of Oracle I need to investigate moving this over to MySQL 5.5 with InnoDB. Downtime will be acceptable for this migration.
Can I just copy code and data structure over?
Would a new installation with MySQL be best, and then copy data over from the Oracle installation?
Has anyone here done this before?
On the side of migrating the database, the easiest way to do this is to go to the ControlPanel, under Server Administration you'll find a page with a Database migration UI. This will read from your current database (e.g. oracle) and write to a database that you configure on that UI. Make sure that nobody is accessing the portal during that time - this feature has been created specifically for migrating databases: There might be some differences between the databases, that will automatically be "translated" in this progress.
On a somewhat related side note: If you want to get updates and fixes (including security), you should consider to upgrade to a maintained version, CE or EE. 6.0 CE (which is what 6.0.6 is) has end-of-lifed a while ago. 6.0 EE is still available, as well as 6.1 CE and EE.
Edit in 2017: Note that this feature is no longer supported in Liferay 7 and DXP: The database migration tool doesn't cover (all of) the module's tables.
Related
My company has two web based project. Our main project (Starbooks) was built using xampp server and Codeigniter framework that installed in our Windows OS and the second project (Frontlearners) was built in Lamp server and moodle (LMS) framework with Postgres database that installed in ubuntu platform.
My goal is to collide this two projects into one by moving the second project (Frontlearners) into the main project (Starbooks) server which uses with xampp server windows platform.
My first attempt is to export the moodle Postgres database using PGAdmin then move the moodle project to the main project server on windows. But I don't know if this is the correct way or not because Postgres and mysql are different database type. I've searching across the internet hoping for the answer or tutorial related to my problem but the results are always fresh installation of moodle which is not related to my problem.
Anybody knows how to solve this problem, a tutorial link, or any article about this situation?
There is a database transfer tool in Moodle.
https://docs.moodle.org/311/en/Database_transfer
So you can convert the PostgreSQL database to MariaDB
First ensure MariaDB is installed on Ubuntu
Turn off cron and put the site in maintenance mode
Then go to Site administration > Development > Experimental > Database migration to convert the database.
Or direct to /admin/tool/dbtransfer/index.php
The tool will check the database structure matches the structures in the install.xml files. If there are any differences, then you will need to update the relevant install.xml file or database table before continuing.
If its a large database, then the UI will probably time out. So use the command line version instead:
php admin/tool/dbtransfer/cli/migrate.php --help
Having said all that, IMHO I would transfer the Windows project to Linux.
I have a Wordpress site that was developed on a server running the latest version of MYSQL, however, I've just found out the host server (BT) is running 5.1.1. and they have no plans to upgrade anytime soon.
Does anyone know if there is a way of converting the database so it runs on 5.1.1 with no issues caused re the site being built in the latest version of Wordpress?
If this is a massive issue, then I do have some alternative hosting options, but I'm hoping for a way forward re conversion - any geniuses out there?
Many thanks
I doubt that BT is running MySQL 5.1.1. That version was never released. It was an internal development milestone in 2005.
The first GA release of the 5.1 branch was 5.1.30 in 2008. The last 5.1 release was 5.1.73 in 2013. But after 2013, 5.1 has been in "sustaining support" which means they will not make any new versions or fixes.
You shouldn't deploy to a hosting site that still runs any 5.1.x version. A site that is so far behind is probably behind on other software too, and I would not be surprised if they have known security vulnerabilities.
Wordpress officially requires MySQL 5.6 or later, according to https://wordpress.org/about/requirements/.
You could try to test that by testing on MySQL 5.1 (assuming you can find an installation package of MySQL 5.1). Use mysqldump to export data from your 5.6 database server and then import that to MySQL 5.1. The output of mysqldump wraps newer syntax in special comments that will be ignored by older versions of MySQL Server.
Regardless, my recommendation is:
Find another hosting service running MySQL 5.6 or 5.7.
Develop and test your site with the same versions of all software (MySQL, PHP, Apache, etc.) that you will eventually deploy to.
For a new project which has to target Linux and Windows, I am searching for a solution to support MySQL (or MariaDB).
Because we have to support those different platforms I wish to work on DNX Core5.0. However I can't find any nuget packages / connectors which I can use to connect to the database. the one that i find are not supported by DNX core 5.0.
Is there a way to connect to mysql in DNX core 5.0 ? Or do you have to fall back on ODBC connections, i don't know if this would work...
Further i was searching for an ORM to support this, my research till now found out that
Entity Framework 7 is not supporting MySQL at this moment. (and EF is not my favorite ORM at this moment)
NHibernate: Currently nobody is working on it and it will be difficult (breaking changes) to port it to DNX Core
Dapper: (MicroORM I know ...): This is supporting DNXCore but i need a vallid IConnection which I can't create.
Thanks for your feedback!
Rob
I asked a similar question a couple of weeks ago. There is no MySql connector for DNX Core. I had to fall back to DNX 4.5.1 and was able to use MySql with Entity Framework in a project that's running inside a Docker container. Also see the response to my question.
I am trying to design a database application for my small business. I've created a number of form driven MS Access databases for use before but would like to create a permanent solution in something more advanced & common.
I was thinking of using mySQL for the database and would then program a C# or VB application to be used in Windows. I do not want or need a web based version at this time but the migration to VB.net in the far future may be something I'll look into.
I know I can use a MS Access backend for my windows application without having to install MS Office on any or all the computers the program will be run for.
But here is my question. Is it necessary to install mySQL Server on the PC hosting the database, on all the PCs accessing the database or can I just use the database file as the backend and Visual Studio will have all the necessary tools I need to access it?
If I have to install the server I may just stick with the MS Access database as the needs for an excessive amount of database storage won't ever be an issue.
You'd need to install MySQL server on the Server hosting the database. The clients would then connect via the network. You will however need a driver to access the MySQL-Server with VB.NET on the client machines. A simple DLL-File might be enough, though.
If you are looking for a file-based database solution have a look at SQLite. But you will have to watch out for concurrency issues here.
I've read through a number of pages detailing the version differences between the different MySQL versions, but none of them have given me a real clear picture as to what is best for the application I am making. I'm in the process of building a CRM which will handle 20,000 customers at launch and built on a LAMP stack. The OS will either be CentOS or FreeBSD.
Right now for test purposes we've been using a MySQL 5.0 server for the database, but we are wondering which version we should use for production. If anyone could give some thoughts as to the pros and cons of using 5.0 vs 5.1 vs 5.5 vs 5.6 in the context of a CRM application, it would be most appreciated.
TL;DR 5.5
For a new software rollout, it makes sense to integrate and do final testing with the latest generally available (GA) release of your infrastructure components.
Right now that's 5.5.20 of the MySQL community server. 5.6.x is considered a development release. It probably doesn't make sense for you to try to do integration and final testing with such a release, unless it offers a new feature that's a critical success factor for your new software. (But then you should ask yourself whether it makes sense to make your product dependent on exotic new features in unfinished dbms releases.)
EDIT... #rkosegi has a good point. If you're going to deploy on an enterprise grade linux server distro like Red Hat Enterprise Linux (rhel) use the version it supports. 5.1 works fine.
I think better you should use v5.1.XX because it's in active development state and stable too.
MySQL has stopped working on v5.0 i guess extend support also will expire soon.
http://dev.mysql.com/doc/refman/5.0/en/