How do I get started with Migration Portal?
Access www.enterprisedb.com in your browser and perform the following steps:
1. Select Migration under the PostgreSQL Software menu.
2. In the page that is loaded, click the Open Migration Portal button under the short description of the Migration Portal.
To access the Migration Portal, you need to have a user account on www.enterprisedb.com. Once logged in, a Getting Started pop-up guides first-time users on how to use the Migration Portal.
Is Migration Portal free to use?
Yes. Migration Portal is free to use, and you can easily access it from popular browsers such as Chrome, Firefox, Safari, and Edge.
Why should I use Migration Portal instead of my self-managed migration solution?
Migration Portal provides a seamless schema assessment and migration experience, allowing you to assess the compatibility of the Oracle schema and better plan your migration journey.
Some advantages of the Migration Portal are:
- Automatic schema repairing capability
- Parallel assessments of multiple projects
- Reassessment capabilities
- Report generation
- Direct migration to the cloud instance, etc.
Moreover, Migration Portal is being continuously enhanced based on customer feedback and market trends, and is a handy and easy tool to address your schema assessment and conversion requirements.
What databases and versions does Migration Portal support?
Currently, Migration Portal supports the assessment and migration of Oracle 11g, 12c, 18c, and 19c schemas. It assesses the schema against EDB Postgres Advanced Server, which is an Oracle compatible Postgres database.
Which EDB Postgres Advanced Server versions does Migration Portal support?
Currently, Migration Portal supports EDB Postgres Advanced Server versions 10 and later.
Can I assess the Oracle schema for PostgreSQL using Migration Portal and deploy the assessed schema on the PostgreSQL server?
No. You can only assess your source schema for EDB Postgres Advanced Server (EPAS). Ensure that you deploy the downloaded script on the same EPAS version used for assessing the schema/s.
How many schemas can a user assess?
There is no limit on the number of projects you can create or the number of schemas you can assess on the Migration Portal.
What should I do if Migration Portal crashes or if the browser hangs up for relatively large SQL files?
Migration Portal can hang while uploading large SQL files. Extract fewer schemas at a time to reduce the size of the SQL file that is uploaded to Migration Portal.
For more information about extracting schemas in an SQL file, see Performing a Schema Extraction.
Do I need to run the DDL Extractor to assess the schemas?
No. Migration Portal no longer supports DDLs extracted by the DDL extractor script. Instead, use the Oracle Data Pump utility to extract Object DDLs to an SQL dump file, as described in Performing a Schema Extraction.
What objects can I assess on the Migration Portal?
Migration Portal can assess and migrate most of the commonly used object types supported by the Oracle database to EDB Postgres Advanced Server. For more information on the supported object types, see Supported Object Types.
Can I run Oracle extracted files directly in EDB Postgres Advanced Server?
No. The script file extracted from Oracle contains syntax that is not compatible with EDB Postgres Advanced Server. Migration Portal uses the repair handlers or transformation logic to make DDLs compatible with EDB Postgres Advanced Server.
In the following example, you can see that Migration Portal automatically applies two repair handlers to make objects compatible with EDB Postgres Advanced Server:
- ERH-2075 (CONSTRAINT_CHECK_UNIQUE_PRIMARYKEY_DISABLE)
- ERH 2009 (Enable)
Does Migration Portal connect to Oracle via the application’s interface?
No. Migration Portal does not connect to the source database. Migration Portal uses SQL files that can be extracted using Oracle’s data pump utility.
Upload the extracted SQL files to Migration Portal. For more information, see Performing a Schema Assessment.
In addition to one-time schema assessment and migration, can I use Migration Portal for continuous schema assessments?
No. If there are any changes on the source schema/database, the DDLs have to be extracted and uploaded again in the Migration Portal for assessment and migration.
How do I assess Microsoft SQL Server schemas?
Currently, Migration Portal only assesses Oracle schemas. However, you can use Migration Toolkit to migrate databases from Oracle, Microsoft SQL Server, Sybase, MySQL, and PostgreSQL. For more information, see the Migration Toolkit documentation.
What can I do when some of my objects fail during an assessment?
Migration Portal automatically repairs the incompatible objects to make them compatible with EDB Postgres Advanced Server. If some objects are not repaired automatically, you can manually fix the objects by referring to the Knowledge Base and reassessing the objects. See the following example:
1. Create a project in Migration Portal, upload the extracted script from Oracle, and click Create & assess.
2. After completing the assessment, if there are any object failures, check the error details.
Oracle allows empty strings as a default value for numeric data type columns. However, EDB Postgres Advanced Server does not allow empty strings as a default value for numeric data type columns.
3. The Knowledge Base suggests using a numeric value for the numeric data type columns.
4. After editing the DDL, click Reassess to check the compatibility.
Note: If you cannot repair the objects, fill in the required information and submit the form in the Contact page. Someone from EDB will contact you with the resolution.
Can I see or identify the objects repaired or edited by me?
Yes. You can use the filters on the Workspace page and see the desired objects.
Can I see the consolidated list of reasons why objects failed?
Yes. You can view the reason the objects failed for the selected schemas. See 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 selected schemas. You can also view the count of distinct repair handlers applied to the DDLs under the selected schemas.
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 or on-premises.
I have assessed my schema with 100% success. What can I do next?
You can migrate your assessed schemas to EDB Postgres Advanced Server. There are three options for migrating the schemas:
- Existing on-premises on the EDB Postgres Advanced Server
- New on-premises on the EDB Postgres Advanced Server
- EDB Postgres Advanced Server in the cloud
For more information, see Schema Migration.
Alternatively, you can export the EDB Postgres Advanced Server compatible DDLs in a .sql file and then use any client application (e.g., pgAdmin, PEM, or PSQL) to create the schema in your target EDB Postgres Advanced Server.
Can I deploy the assessed schema to any cloud service?
You can deploy the assessed schema directly to an EDB Postgres Advanced Server in the cloud.
You can migrate to any of the following available cloud options, including BigAnimal. BigAnimal is EDB’s offering of a fully managed database-as-a-service with built-in Oracle compatibility. For more information, see the BigAnimal documentation.
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, or type bodies) at the time of creation to determine if they are valid or invalid. 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 compile time.
The PL/SQL code like stored procedures, triggers, functions etc, may migrate successfully to EDB Postgres Advanced Server but give runtime errors for missing dependencies or any other logical error.
It’s crucial to test and verify all code paths in Postgres to ensure that users do not encounter run time or execution time errors.
Why does my stored procedure language look different after using the Migration Portal?
Migration Portal fine-tunes PL/SQL to ensure full compatibility with EDB Postgres Advanced Server (EPAS).
Can I migrate data using Migration Portal?
No. You can migrate data with the Migration Toolkit (MTK). For more information, see the Migration Toolkit documentation.
I have an enhancement/feature request. Where should I submit it?
You can submit the enhancement request via the EDB Customer Support Portal or your Technical Account Manager, Sales Engineer, or Customer Service Representative team member.