Is EDB Postgres Migration Portal free to use?
Yes. Our Migration Portal is 100% free and can be accessed from most of the browsers; Chrome, Firefox, Safari and Edge.
What versions of Oracle does Migration Portal support?
Currently, Migration Portal 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 is no limit on how many projects can be created or how many schemas a user can assess on the EDB Postgres Migration Portal.
Can I export the repaired schemas?
Yes, you can download the repaired and compatible schemas on your local machine or deploy them on an EDB Postgres Advanced Server in the cloud.
Do I need to run the EDB DDL Extractor to assess the schemas?
Yes. In order for Migration Portal to recognize and assess schemas, it requires a simplified SQL file. For more information, see the EDB DDL Extractor Guide.
Note: You must use the latest version of the EDB DDL Extractor.
Can I migrate data using EDB Postgres Migration Portal?
Data migration can be performed with the EDB Postgres Migration Toolkit, MTK. For more information, see EDB Postgres Migration Toolkit Guide.
What objects can I assess?
EDB Postgres Migration Portal can assess and migrate most of the objects supported by Oracle Database to EDB Postgres Advanced Server. For more information on the supported object types, see the Migration Portal Guide.
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 EDB Postgres Advanced Server compatible DDLs in a .sql file and use any client application such as pgAdmin, ToadEdge, or PSQL to create the schema in your target EDB Postgres Advanced 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 EDB Postgres Advanced Server using EDB Migration Toolkit. The data can be migrated in online and offline mode. For more information, see EDB Migration Toolkit Guide.
What can I do when some of my objects fail during an assessment?
EDB Postgres Migration Portal automatically repairs the incompatible objects to make them compatible with EDB Postgres Advanced Server. If some of the objects are not repaired automatically, you can manually repair the objects by referring to the Knowledge Base and reassess the objects. If you are unable to repair the objects, you can contact our experts at firstname.lastname@example.org.
In the following example, the DDL uses Oracle’s BITAND function. However, EDB Postgres does not support the BITAND function.
To assess the DDL file and make manual changes, complete the following steps:
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, EDB Postgres 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 the BITAND function.
4. After editing the DDL, click Reassess to check the compatibility.
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 EDB DDL Extractor utility, edb_ddl_extractor.sql. The utility uses Oracle's dbms_metadata package to extract definitions of different object types from the database. The extracted files must be uploaded to EDB Postgres Migration Portal. For more information, see the Quick Start Guide
Note: You can run the EDB DDL Extractor tool on SQL*Plus, SQLDeveloper, or any other IDE/Client tool. However, we recommend using SQLDeveloper to ensure the right encoding for output messages.
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 Advanced Server. Migration Portal uses the EDB DDL Extractor tool that extracts the objects to make them compatible with EDB Postgres Advanced Server.
In the following sample, you can see that Migration Portal automatically applies repair handlers to make objects compatible with EDB Postgres Advanced Server:
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 Advanced Server.
Can I assess the Oracle schema for PostgreSQL using EDB Postgres Migration Portal and deploy the assessed schema on the PostgreSQL server?
No, you can assess your source schema only against EDB Postgres Advanced Server. The downloaded script can only be deployed on the respective EDB Postgres Advanced Server version.
Which EDB Postgres versions are supported?
Currently, Migration Portal supports EDB Postgres Advanced Server version 10 and later.
How do I migrate from Microsoft SQL Server?
Migration from SQL Server and other legacy databases will be supported in future versions. The current version allows only migration from Oracle. However, you can use EDB Migration Toolkit to migrate databases from Oracle, SQL Server, Sybase, MySQL, and PostgreSQL. For more information, see EDB Postgres Migration Toolkit Guide.
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.
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 see the consolidated list of reasons for the failed objects?
Yes, you can view the reason for the failed objects for the selected schemas in the “Common Failures” tab on the Workspace Page.
Can I export the common object failures in a file?
Yes, you can download a CSV file having the common failures for the project.
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 for the selected 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 Advanced Server compatible schema and deploy on EDB Postgres Advanced Server on any cloud service provider.
The newly converted database schema was imported successfully to EDB Postgres Advanced Server. Why are some of my PL/SQL or code objects still failing when called or executed?
Oracle compiles code objects (e.g. stored procedures, functions, triggers, packages, package bodies, types, type bodies. ) when they are created to determine if they are valid or invalid to execute. Postgres only validates the syntax of the object definition such as parameters and data types; it does not validate the code body of the objects at the compile time. Additional errors such as dependencies on objects or functions not migrated to Postgres (which would have been uncovered by the Oracle compiler) may occur when executing a statement in a stored procedure, trigger, or function for the first time. It’s important to test/verify all code paths in the Postgres to ensure that users will not uncover run time or execution time errors.
Why does my stored procedure language look different after using the Migration Portal?
EDB Postgres Advanced Server uses the edbspl language for compatibility with Oracle PL/SQL. Another stored procedure language plpgsql is available in Community Postgres and EDB Postgres Advanced Server. Still, it doesn't provide full compatibility with the PL/SQL used in Oracle and may require syntax changes to be made for your stored procedures to execute successfully.