Convert Oracle to PostgreSQL.

Our DBConvert/DBSync software assists with your data conversions and synchronizations from Oracle to PostgreSQL, Amazon RDS PostgreSQL or Heroku Postgres instances. In case you have no direct connection to PostgreSQL, you can also use Dump files and PHP scripts as a target.

Several migration options are presented in the configuration step in our GUI wizard. Our powerful command line mode to automate migration tasks is available in DBConvert/DBSync for Oracle and MySQL as well.

It takes between 4-7 minutes to migrate 1 million records.

Trigger-based database replication methods and simultaneous bi-directional synchronizations help you to manage your data easy and efficiently.

 DBConvert for Oracle & PostgreSQL

Migration directions:

  • Oracle → PostgreSQL, PostgreSQL Dump, PHP Script
  • PostgreSQL → Oracle
  • PostgreSQL ↔ Amazon RDS | Aurora ↔ Oracle
  • PostgreSQL ↔ Heroku Postgres ↔ Oracle

Version: 1.1.9

Release Date: Dec. 15, 2020

 DBSync for Oracle & PostgreSQL

Sync directions:

  • PostgreSQL ↔ Oracle
  • PostgreSQL ↔ Amazon RDS/ Aurora↔ Oracle
  • PostgreSQL ↔ Heroku Postgres ↔ Oracle

Version: 1.2.2

Release Date: April 28, 2021

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

DBConvert Studio

 Version: 2.0.6

Release Date: March 23, 2021

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 Oracle to PostgreSQL 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 PostgreSQL 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 PostgreSQL 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 PostgreSQL
  • PostgreSQL to Oracle
  • Oracle to Oracle
  • PostgreSQL to PostgreSQL

NOTE #2: Don't be confused by the fact that connections to cloud databases like Amazon RDS, 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 PostgreSQL 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 PostgreSQL.

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.

By default, DBConvert tries to automatically map the database types of the source Oracle database to the closest equivalent of the target PostgreSQL database types. However, you can manually change the data types for the entire database globally using the "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 PostgreSQL

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 PostgreSQL target database connection settings with other specified options.

Example: C:\Program Files\DBConvert\oracle2postgresqlPro\oracle2postgresqlPro_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.

Find more Information about built-in scheduler

DBConvert screenshot

Supported OS:

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 PostgreSQL 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.

Related Links

Highlights

Read information about reverse migration.