Is EDB Postgres Migration Platform free to use?

Yes. Our migration platform is 100% Free and can be accessed from most browsers - Chrome, Firefox, Safari, Internet Explorer, Edge. 

 

What versions of Oracle does Migration Portal support?

The Migration portal currently supports Oracle 11G and 12C source databases. The target database is the EDB Postgres Advanced Server, which is compatible with Oracle. 

 

How many schemas can a user assess?

There are no limits on how many projects can be created or how many schemas a user can assess with the EDB Migration platform.

 

Can I export the repaired schemas?

Yes, a user can download the repaired and compatible schemas on a local machine or launch them on an EDB Postgres Advanced Server in the cloud. 

 

The downloaded schemas are compatible with which database?

Downloaded schemas are compatible with EDB Postgres Advanced Server. 

 

Do I need to run the DDL extractor tool to assesses the schemas?

Yes. In order for Migration Portal to assesses the schemas, it needs a simplified text file. You can read about DDL extractor here and how to use it. The latest version of the DDL Extractor tool should always be used.

 

Can I migrate data with the Platform?

Data migration can be performed with the EDB Migration Toolkit - MTK.  Read more here.

 

What objects can I assess?

EDB Postgres Migration Platform can assess and convert objects supported by Oracle Database to EDB Postgres Advanced Server. The Migration Portal Users Guide provides a list of object types supported.

 

I have assessed my schema with 100% success, what can I do next?

Once you have assessed all your schemas with 100% success, you can either export the Advanced Server compatible DDLs in a .sql file and use any of client application such as pgAdmin, ToadEdge, or PSQL client to create the schema in target EPAS server or you can directly migrate your schema to a Cloud Database Service (CDS) Cluster. For more information about Cloud Database Service, see EDB Postgres CDS documentation.

You can also move data from Oracle to Postgres using EDB Migration Toolkit. For more information, see EDB Migration Toolkit.

DEPLOYMENT EXAMPLE     

Following is the example to use EDB-PSQL to deploy exported DDLs for schema HR:

edb=# \i <path_to_file>/ProjHR_hr.sql

 

DATA MIGRATION EXAMPLES IN ONLINE MODE

Following are the examples of data migration in online mode: 

  • JDBC COPY API
    /runMTK.sh -sourcedbtype oracle -targetdbtype enterprisedb -targetSchema HR - dataOnly -truncLoad HR

     

  • -copyViaDBLinkOra module
    The dblink_ora module provides Advanced Server-to-Oracle connectivity at the SQL level. A dblink_ora is bundled and installed as a part of the Advanced Server database installation. The dblink_ora utilizes the COPY API method to transfer data between databases. This method is considerably faster than the JDBC COPY method.
    ./runMTK.sh -sourcedbtype oracle -targetdbtype enterprisedb -targetSchema HR -copyViaDBLinkOra -dataOnly -truncLoad HR

     

  • SQL INSERT statements
    SQL INSERT statements for each row in the table
    ./runMTK.sh -sourcedbtype oracle  -targetdbtype enterprisedb  -dataOnly -truncLoad -safeMode HR

     

 

DATA MIGRATION EXAMPLES IN OFFLINE MODE

Following are the examples of data migration in offline mode:

  • .cpy (copy) files
    To generate the .cpy (copy) files, run the following command:
     
    ./runMTK.sh -sourcedbtype oracle -targetdbtype enterprisedb -targetSchema HR - dataOnly  -offlineMigration /data_folder/hr_schema/  HR

    Note: Only one file per table is generated.

  • Inserts as SQL Statements
    To generate Inserts as SQL Statements, run the following command:
     
    ./runMTK.sh -sourcedbtype oracle -targetdbtype enterprisedb -targetSchema HR - dataOnly -safeMode -offlineMigration /data_folder/hr_schema/  HR

    Note: Only one file per table is generated.

  • -singleDataFile keyword
    To generate a single file that contains the data from all tables, run the following command:
     
    ./runMTK.sh -sourcedbtype oracle -targetdbtype enterprisedb -targetSchema HR - dataOnly -safeMode -singleDataFile -offlineMigration /data_folder/hr_schema/ HR

     

INSERTING DATA IN TABLES IN EDB POSTGRES
 

  • Copy Command
    Below example deploys exported DDLs for schema HR using EDB-PSQL.
    edb=# COPY hr.locations FROM '/data_folder/hr_schema/mtk_hr_locations_data.cpy';

    The following example deploys exported DDLs for schema HR using EDB-PSQL.
     

    edb=# COPY hr.locations FROM '/data_folder/hr_schema/mtk_hr_locations_data.cpy';

     

  • SQL FILE
    edb=# \i /data_folder/hr_schema/mtk_hr_locations_data.sql

     

  • ONLINE RESOURCES
      EDB Postgres CDS
      EDB Migration Toolkit

 

What can I do when some of my objects failed to transform during an assessment?

The EDB Postgres Migration Portal uses Repair Handlers to transform object DDLs to make them EDB Postgres compatible. In case, there are some failed objects, one needs to check the error in the Output window and refer KB or online documentation to resolve the error. One can post a query on the  postgresrocks.com forum as well and someone from EDB will respond with possible solutions. In case of errors, you can check the error details in the Assessment output, and based on the error type, you can take one of the following options:

  • Apply the fix and run the assessment.
  • Refer to the Knowledge Base to resolve the error. (link)
  • Refer to the online documentation to resolve the error. (link)
  • In case you do not find a solution in the Knowledge Base and the online documentation, you can post your query on the PostgresRocks.com forum, and the EDB team member will respond with a possible solution.

In the following example, the DDL uses Oracle’s BITAND function. However, EDB Postgres does not support the BITAND function.

To remove the incompatibilities complete the following steps:

Create a project in EDB Postgres Migration Portal and load script extracted from Oracle.
 

1. Create a project in EDB Postgres Migration Portal, and upload the extracted script from Oracle, and click Create & Assess.

 

2. After completion of the assessment, if there are any object failures, check the error details.

 

 

3. Oracle supports the BITAND function; however, Advanced Server does not support it. 

You can enter the BITAND keyword in the Knowledge Base section and look for the workaround for the BITAND function, which suggests using the & operator instead of BITAND function.

 

Does EDB Postgres Migration Portal connect to Oracle via Application Interface?

No. EDB Postgres Migration Portal does not connect to the Source database. Migration Portal requires the script generated by Extractor Utility, edb_ddl_extractor.sql. The utility uses Oracle's dbms_metadata package to extract definitions of different object types from database. The extracted files must be uploaded to EDB Postgres Migration Portal. For more information see, Quick Start Guide

Note: We recommend to execute edb_ddl_extractor in Oracle SQL*PLUS.

 

Can I run Oracle extracted files directly in EDB Postgres?

No, the script file extracted from Oracle contains syntax, which is not compatible with EDB Postgres. The Migration Portal transforms the extracted objects to make them compatible with EDB Postgres.

The following samples display how Migration Portal automatically applies repair handlers to make objects compatible with EDB Postgres:

 

Table as extracted from Oracle

Sample 1: Migration Portal applied two repair handlers ERH 2005 (Using Index Enable) and ERH 2009 (Enable) for making the object compatible with EDB Postgres.

 

Can I transform Oracle schema for PostgreSQL using EDB Postgres Migration Portal to deploy on the PostgreSQL server? 

No, you can assess your source schema only against EDB Postgres. The downloaded script can only be deployed on the respective EDB Postgres version.

 

Which EDB Postgres versions are supported?

Migration Portal supports EDB Postgres 10 onwards as of now. And as and when a newer version of EDB Postgres is available, its support will be added to Migration Portal.

 

Unable to find the option to migrate from SQL Server on the EDB Postgres Migration Portal.

Migration from SQL Server and other legacy databases will be supported in future versions. The current version allows only migration from Oracle. In case you want to migrate right now, you may use EDB Migration Toolkit, which allows migration from Oracle, SQL Server, Sybase, MySQL, and PostgreSQL.

 

Can I use edb_ddl_extractor.sql to extract from databases other than Oracle e.g. SQL Server or Sybase?

No, edb_ddl_extractor can only be used to extract Oracle schema. In the future, we will provide extractors for other databases as well, and the updated DDL Extractor can be downloaded from the “Getting Started” menu.

 

Can I see or identify the objects repaired or edited by me?

Yes, you can filter the system repaired and manually repaired objects on the Workspace page.

 

  

Can I generate a report for the assessed schema?

Yes, once you assess the schema, click Report. You can either generate the report for all schemas or select the required schemas. You can also view the count of distinct repair handlers applied to the DDLs under the selected schemas.

 

Can I deploy the assessed schema to any cloud service? 

Yes, you can export the assessed schema and deploy directly on EDB Cloud Database Service's cluster or you can also download the EDB Postgres compatible schema and deploy on EDB Postgres on any cloud service provider.