MySQL to Oracle conversion and synchronization.

DBConvert/ DBSync software is intended for migration and synchronization of databases from MySQL Server to Oracle. Direct connections to source and target databases are used for quick reliable connection.

The whole database or only needed database’s single elements optionally can be transferred using our migration software. Schemas and views conversion can be performed as well.

Using an intuitive Wizard interface, applications walk you through the necessary steps to successfully migrate your databases. You can also adapt conversion and synchronization to your needs customizing the rules for copying data to a target database. For example, you can transfer data directly to a server or to a Dump file to read it later directly on server. Software supports command line that allow users to automate transferring processes.

DBConvert and DBSync software converts data types between MySQL and Oracle automatically. But you can adjust types casting by hands with the help of smart mapping feature.

Built-in Scheduler presented as a stage in all our tools will help you to run conversion and synchronization tasks in automatic mode. Besides, Trigger-based database synchronization and three sync types could be used to keep your data constantly up-to-date.

Supported databases:
  • Oracle On-Premises
  • Oracle Cloud
  • MySQL
  • MariaDB
  • SingleStore DB (formerly MemSQL)
  • TiDB
  • Percona Server for MySQL
  • Vitess
  • Amazon RDS for MySQL
  • Amazon Aurora (MySQL Compatible)
  • Google Cloud
  • Azure Database for MySQL
  • MySQL Dump
  • PHP Script
 DBConvert for Oracle & MySQL

Version: 2.2.7

Release Date: May 31, 2023

 DBSync for Oracle & MySQL

Version: 1.7.7

Release Date: Nov. 3, 2023

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

DBConvert Studio

 Version: 3.5.4

Release Date: Feb. 14, 2024

Supported databases:

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

Using MySQL to Oracle conversion and synchronization tools.

When launching the DBConvert or DBSync application in GUI mode, it seamlessly guides you through the steps to initiate database migration or synchronization:

1. Connect to MySQL source database.

Specify the username/password and host/port parameters if your source database requires login credentials.

Connect to MySQL source database from DBConvert

2. Connect to Oracle destination database.

Specify parameters for the destination database similar to the source, defining connection settings and username/password pairs.

Connect to Oracle target database from DBConvert

NOTE #1: Each DBConvert or DBSync tool's name comprises two different databases, enabling any specified database to operate as the source or destination. Furthermore, the same type of database can function as both the source and destination.

NOTE #2: Connections to cloud databases (e.g., Amazon RDS, Google Cloud, or Azure SQL) aren't explicitly specified in the user interface but use the same settings as traditional on-premises databases.

NOTE #3: Connections to source and target databases remain active until you close the DBConvert/DBSync application or reopen new connections.

Refer to our documentation for specific source/ destination configurations for different databases.

3. Configure database migration options.

Specify the tables, fields, indices, and views you want to transfer to the Oracle destination database by checking/unchecking the corresponding boxes.

Customize general database/ tables settings. Or configure specific table , field, index object individually when migrating data.

Explore our articles in the user's manual about Configuring database migration options. for detailed information.

The screenshot below summarizes the general features available in DBConvert software.

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

The database enforces certain relations on the data, and on the customization step, an intelligent error checker verifies all possible data integrity and referential integrity issues. It highlights any problems before migration starts.

By default, DBConvert attempts to automatically map the database types of the source MySQL database to the closest equivalent of the target Oracle database types. However, you can manually change the data types for the entire database globally using the "Global mapping" or individually for each field.

Explore the Intelligent error checker for more information. on errors and warnings

5. Execution. The final stage of data migration.

Initiate the conversion or synchronization process after configuring source and destination databases in the previous steps.

Click the "Commit" button to start conversion. Here, you can also monitor the migration/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

Explore more about the options available during the execution stage

Command line mode

Pass previously saved sessions as parameters to the Command-Line DBConvert Client. A session retains MySQL source and Oracle target database connection settings with other specified options.

Example:

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

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

Built-in scheduler.

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

Find more Information about the built-in scheduler

DBConvert screenshot

Supported OS:

Requirements

  • 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.
  • 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)

Related Links

Highlights

Explore details regarding reverse migration.