Creating an application record Innovation Release

An application record is how Hybrid Manager (HM) represents a software application. It maps the application to the source databases and schemas it depends on, and holds the SQL files you upload to assess their compatibility with EDB Postgres Advanced Server (EPAS). Creating an application record is the first step in the application assessment workflow.

Prerequisites

Before creating an application record, ensure the following:

• You have access to the HM project where you want to create the application.
• Your user role includes the migration_applications permission for that HM project.
• You have your SQL artifacts ready to upload. See supported import formats for the accepted file types. If you need to generate them first, see Preparing SQL files for assessment.

Creating an application record

The HM console guides you through defining the application's general metadata and associating it with your migration databases.

1. In HM, open your project.

2. In the left navigation, go to Migrate > Applications.

3. Select +New Application.

4. Enter the application's metadata:

   Field	Required	Description
   Name	Yes	A descriptive name for the application. This name appears in the Applications table and on the details page.
   Description	No	A short explanation of what the application does or its business purpose.
   Target database version	Yes	The EPAS version your SQL will be assessed against, ensuring the correct compatibility rules are applied. Becomes the default for every file you upload to this application, so you don't have to select it again at upload time.
   Programming language	Yes	The primary language or framework the application uses to interact with the database, for example, Java, Go (sqlx), or Python.

5. If you want to link an application to source databases, optionally continue to the Next: Databases (Optional) step.

6. Optionally, select the checkbox next to each database you want to include. You can select multiple databases across pages.

   Note

   Linking a source database is optional. If you don't link one, HM assumes Oracle 19c as the source database version. This can affect assessment accuracy if your SQL contains Oracle 21c-specific syntax. To register an Oracle database first, see Configuring the EDB Postgres AI agent to register your Oracle database.

7. Select Create application.

HM creates the application record and takes you to your application details page. You can edit the record's metadata, such as its name or description, later — in Migrate > Applications, select the pencil icon in the Actions column for the application.

Uploading SQL files

After creating the application record, upload your SQL artifacts for assessment.

1. On your application details page, go to the Overview tab.

2. In the SQL File Assessments section, select Upload New File(s).

3. Drag and drop your files into the upload area, or select them using the file picker. You can upload plain SQL files (.sql), Oracle trace files (.trc), or EDB Query Extractor output (.out). You can select up to 20 files in a single upload operation. Individual files must be 2 GB or smaller. If a file exceeds the limit, it's rejected at upload with an error message.

4. Review the list of files. Any pre-validation errors appear here.

5. Select Next: Databases to continue.

6. For each uploaded file, configure the following settings:

   Field	Required	Description
   Source database	No	The migration database the file's SQL was extracted from. Linking a file to a source database lets HM map queries to specific schemas for more precise assessment.
   Target database version	Yes	The EPAS version to assess against, for example, EPAS 18. This action prefills the target version for all assessed databases at the application record level.
   Oracle User UIDs	No	One or more Oracle user IDs whose objects appear in the SQL file. Used to scope the assessment to the relevant schema owners.

7. Select Confirm to upload the files and queue them for assessment.

Deleting an application record

You can permanently delete an application record you no longer need. HM disables the delete option for any application that still has uploaded SQL files — you must remove them first.

1. Remove the application's uploaded SQL files:

   a. On the application details page, go to the Overview tab.

   b. In the SQL File Assessments section, select the trash can icon in the Actions column for a file.

   c. In the Delete SQL File confirmation dialog, select Delete.

   d. Repeat for each remaining file until # of Assessment Files shows 0.

2. In the left navigation, go to Migrate > Applications.

3. In the Actions column for the application, select the trash can icon.

   Note

   If the icon is disabled, hover over it. A tooltip confirms that you must first remove the application's uploaded SQL files.

4. In the Delete the Application dialog, type delete application into the field to confirm, then select Delete.

HM permanently deletes the application record. This action can't be undone.

Next steps

HM automatically runs an assessment after you upload the files. See Reviewing assessment results to understand how to interpret the compatibility report, identify incompatible queries, and plan remediation before migrating your application.

Related topics

• Preparing SQL files for assessment — Generate Oracle trace files, EDB Query Extractor output, or prepare plain SQL files for upload.
• Reviewing assessment results — Interpret the assessment output, explore incompatible queries, and plan remediation before application migration.
• Application assessment overview — Understand how HM assesses application SQL and the supported file formats.
• Migration assessment — Review schema- and database-level assessments alongside application assessments.