After you create an application record and upload SQL files, Hybrid Manager (HM) automatically runs an assessment and produces a compatibility report. This page explains how to read those results and use them to remediate incompatibilities before you migrate your application.
Opening the SQL Assessment tab
- In HM, go to Migrate > Applications.
- Select the application you want to review.
- On your application details page, select the SQL Assessment tab.
The SQL Assessment tab aggregates findings across all SQL files uploaded to the application.
Reviewing assessment details
The Assessment Details section at the top of the SQL Assessment tab gives you a feature-compatibility summary and key metadata about the assessment run.
Feature compatibility cards
Compatibility cards show how Oracle-specific features in your SQL files break down by compatibility status:
| Card | Description |
|---|---|
| Compatible features | Features that work on EDB Postgres Advanced Server (EPAS) without any changes. |
| Features with available workaround | Features that aren't natively compatible but have a known, established workaround you can apply. |
| Features with new workaround | Features for which a new workaround has been identified, which may require additional review before adopting. |
| Features with no workaround | Features that can't be automatically transformed and have no known workaround. These items require manual remediation. |
Assessment metadata
Below the cards, a metadata strip shows context for the assessment run:
| Field | Description |
|---|---|
| Application name | The name of the application record. |
| Source database(s) | The migration databases linked to this application. |
| Target database version(s) | The EPAS version the assessment was run against. |
| Total input files provided | The number of SQL files uploaded to this application. |
| Total queries parsed | The number of SQL statements successfully parsed across all files. |
| Total queries with suggested repairs | The number of queries for which HM produced a suggested transformation. |
| Last assessment timestamp | When the most recent assessment completed. |
Downloading the assessment report
To share or archive the full assessment, select Download Report. The report contains a complete summary of all findings across files and is useful for offline review, team handoffs, or migration planning documentation.
Downloading transformed queries
Select Download Transformed Queries to export all transformed queries for the application as a single archive. You can use this output to:
- Inspect how HM adapted specific queries for EPAS.
- Feed transformed statements into a test environment before completing the migration.
- Seed a review process with your development team.
Reviewing incompatible features
The Incompatible Features table identifies Oracle-specific features found in your SQL files that aren't directly compatible with EPAS. Use this table to understand categories of issues across your codebase before drilling into individual queries.
| Column | Description |
|---|---|
| Feature | The Oracle-specific syntax, function, or construct that's incompatible. |
| File | The SQL file where this feature appears. |
| Oracle User UIDs | The Oracle schema owner(s) associated with this feature, if provided at upload. |
| Workaround Status | The current remediation state for this feature. |
| Queries | The number of queries in the file that use this feature. |
| Occurrences | The total number of times this feature appears across all queries in the file. |
| Query ID | A reference to the specific query where the feature is found. |
Reviewing incompatible queries
The Incompatible Queries table gives you a query-by-query breakdown of SQL statements that need changes before your application can run against EPAS. This table is your primary tool for understanding the scope of application-side remediation work.
Each row represents a single SQL statement with one or more incompatibilities. Queries listed here won't run correctly as-is and require action before application cutover.
| Column | Description |
|---|---|
| Query ID | A stable identifier for the query in the assessment results. |
| File | The SQL file that contains this query. |
| Oracle User UIDs | The Oracle schema owner(s) associated with this query, if provided at upload. |
| Query | A preview of the SQL statement. |
| # of Incompatible Features | The number of distinct incompatible features detected in this query. |
| Occurrences | How many times this query appears across the uploaded files. |
Expanding a query to see transformations and repair guidance
If HM was able to repair the query, use the + sign for that query row to expand it. The expanded panel shows:
- Transformed query — HM's EPAS-compatible version of the original SQL. This output is the suggested replacement you can use to update your application code.
- Repair handlers — details about the specific changes made during transformation, including:
- What Oracle construct was changed.
- Which transformation rules were applied.
- Any remaining steps that require manual attention.
Not every incompatible query can be transformed automatically. Where HM can't produce a transformation, the repair handler notes describe what needs to be changed, so you can make the fix manually in your application code.
Fixing incompatibilities before application migration
After reviewing the assessment results, use the findings to adapt your application before cutover. A typical remediation workflow looks like this:
Triage using incompatible features. Start with the Incompatible Features table to understand the categories of issues. Use the Workaround Status column to prioritize: features marked None / Needs Investigation have no known workaround and require the most attention, while Available and New Workaround entries have established remediation paths. A small number of feature types often account for a large share of incompatible queries — identifying these patterns lets you plan remediation in bulk rather than query by query.
Review transformed queries. For each incompatible query in the Incompatible Queries table, expand the row to compare the original Oracle SQL with the transformed EPAS version. Where HM's transformation is correct, you can adopt it directly in your application code.
Handle queries without automatic transformations. Where no transformation is available, the Repair Handler Applied field in the expanded row describes what was attempted and what still needs manual attention. Update your application code accordingly and retest against a non-production EPAS environment.
Test on a non-production environment. Before migrating production, run your updated application against a non-production EPAS cluster with migrated data and schema. Use the # Leftover Incompatible Features count in each expanded query row to confirm all issues have been resolved. Resolve any remaining runtime errors before cutover.
Note
Addressing SQL incompatibilities before the production cutover window reduces risk and shortens the maintenance window. See Oracle to HM-managed migration guide for guidance on sequencing these steps.
Related topics
- Creating an application record — Set up an application record and upload SQL files for assessment.
- Application assessment overview — Understand how HM assesses application SQL and the supported file formats.
- Migration assessment — Review schema- and database-level assessments alongside application-level findings.