Convert Oracle to MySQL.

Our DBConvert and DBSync migration software provides both smooth and quick data migration and replication from Oracle to MySQL even when you have little or no SQL knowledge. Our tests show it takes 3-4 minutes to convert 1 million records from Oracle to MySQL. Larger volumes of data can also be processed using DBConvert's migration tools. For example, you can transfer 10 million records in just 35 minutes.

Migrate Oracle database to MySQL Dump when it’s necessary to get over server restrictions. Unicode support, Indexes and Primary keys conversion are among the other features.

Both MySQL and Oracle have their own feature sets aimed for different target audiences. It is difficult to directly compare them, as they are products in two different categories.

Oracle is intended primarily for big enterprise business applications. It offers a slew of features and functionality. Oracle is suited for doing very complex jobs in large environments.

MySQL is used commonly for web, small and medium data warehouses, and the gaming industry. It surpasses Oracle when high-speed reads are required. Many startup companies use MySQL, as it is both simple and lower cost. MySQL has fewer as Oracle but often many of Oracle's features are found to be excessive for small and medium projects.

If you need to move or sync the whole database from Oracle to MySQL in a heterogeneous environment, let our software to be your assistant. Partial Oracle DB datasets may also be transferred or replicated to MySQL according to your needs.

By default DBConvert automatically maps data types between Oracle and MySQL or you choose to adjust many of them manually.

Trigger-based database synchronizations and three sync types are available in our DBSync for Oracle and MySQL application. Synchronization features helps to keep your databases fresh and up-to-date. Moreover, the DBSync tool gives you notice about possible synchronization errors in advance before starting the actual replication.

Our built-in Scheduler and powerful command line mode help to launch your conversion and sync jobs automatically using predefined parameters.

 DBConvert for Oracle & MySQL

Migration directions:

  • Oracle → MySQL, MariaDB, MySQL Dump, PHP Script
  • MySQL, MariaDB → Oracle, MySQL Dump, PHP Script
  • Oracle ↔ Amazon RDS | Aurora↔ MySQL
  • Oracle ↔ Google Cloud ↔ MySQL
  • Oracle ↔ Azure Database for MySQL

Version: 2.2.2

Release Date: April 12, 2018

 DBSync for Oracle & MySQL

Sync directions:

  • MySQL ↔ Oracle ↔ MariaDB
  • Oracle ↔ Amazon RDS | Aurora ↔ MySQL
  • Oracle ↔ Google Cloud ↔ MySQL
  • Oracle ↔ Azure Database for MySQL

Version: 1.7.3

Release Date: Oct. 3, 2018

Try All-in-one DB migration and Sync software.

DBConvert Studio

 Version: 1.8

Release Date: Aug. 4, 2020

Supported databases:

  • SQL Server
  • MySQL
  • Oracle
  • PostgreSQL
  • Access
  • FoxPro
  • SQLite
  • Firebird
  • Excel
  • IBM DB2
  • Azure SQL
  • Amazon RDS
  • Amazon Aurora
  • Heroku Postgres
  • Google Cloud

Related Links

Supported OS:

Using Oracle to MySQL conversion and synchronization tools.

When you start DBConvert or DBSync application in GUI mode it guides you through several steps to set up the database migration or synchronization:

1. Connect to Oracle source database.

If a source database requires you to log in, you can specify a user name/ password and host/ port parameters.

Connect to Oracle source database from DBConvert

2. Connect to MySQL destination database.

Specifying parameters for destination database looks like the same as for source. Usually, it consists of defining connection settings and username/password pairs.

Connect to MySQL target database from DBConvert

NOTE #1: Every DBConvert or DBSync tool has two different databases in its name. That means any specified database from a pair can be set up as a source or destination. Besides, the same type of database may be set up both as a source or destination.

As an example, here is the list of possible migration directions with on-premises databases:

  • Oracle to MySQL
  • MySQL to Oracle
  • Oracle to Oracle
  • MySQL to MySQL

NOTE #2: Don't be confused by the fact that connections to cloud databases like Amazon RDS, Microsoft Azure SQL, Google Cloud, and Heroku are not explicitly specified in the configuration of a source or destination in the DBConvert / DBSync interface. To connect to Cloud database instances, use the same settings as you do for traditional on-premises databases.

NOTE #3: Your connections to source and target databases stay active until you close DBConvert/ DBSync application or reopen new connections on "source" and "destination" steps.

Read more about the specific source/ destination configurations for different databases.

3. Custoimzation and configuration.

At the next step, you can specify precisely which tables, fields, indices, views you want to transfer to the MySQL destination database. Just check/ uncheck the box in front of each database object you want to convert.

Customize general database/ tables settings. Or set up a particular table , field, index individually when migrating data from Oracle to MySQL.

Check out our articles about Custoimzation and configuration. for detailed information.

The screenshot below sums up general features available in DBConvert software solutions.

4. Detection of potential database migration issues. Errors and Warnings

The database typically constrains certain relations on the data that cannot be violated. On the customization step, a smart error checker verifies all possible Data integrity and Referential integrity issues and highlights them, if any, before performing a migration.

DBConvert software to default tries to automatically map database types from the source Oracle database to the closest equivalent of the target MySQL database types. But you can manually change data types for the whole database globally with "Global mapping" or individually for each field.

Check out Smart error checker. Errors and Warnings for more information.

5. Execution. The final stage of data migration from Oracle to MySQL

Once you configure source and destination databases for migration in the previous steps, you can start the actual conversion or synchronization process.

Click the "Commit" button to start conversion. Also, here, you can monitor the migtation/ synchronization process.

Optionally save connection settings and configuration parameters into the session file to schedule the launching of sync or migration jobs regularly.

Execution step of DBConvert products

Read more about execution stage available options.

Command line mode

Previously saved sessions can be passed as parameters to Command-Line DBConvert Client. A session keeps Oracle source and MySQL target database connection settings with other specified options.

Example: C:\Program Files\DBConvert\oracle2mysqlPro\oracle2mysqlPro_Cons.exe /Session:"Session_Name"

NOTE: First, you have to run the software in GUI mode to create a session file with initial parameters.

Built-in scheduler.

Our applications come with a built-in scheduler to run database migration and sync jobs at specified times. Just set the scheduled date and time to execute job sessions automatically.

DBConvert screenshot

Highlights

Requirements

  • Necessary privileges to write into database on the target Oracle server (this requirement is optional as there is an option to overcome the restrictions using dump file)
  • Necessary privileges to write into database on the target MySQL server (this requirement is optional as there is an option to overcome the restrictions using dump file or PHP Script)
  • Oracle 12.x versions require Oracle Database 12c Release 2 Client (12.2.0.1.0) for Microsoft Windows (32-bit) to be installed: