The Hybrid Manager (HM) console includes the capability to assess SQL statements of your applications. This assessment allows you to evaluate the compatibility of Oracle application SQL statements with EDB Postgres Advanced Server (EPAS) in the scope of Oracle database migrations.
While HM's migration tools focus on database schemas and data, this feature addresses the application side of the migration. It provides a structured way to manage the relationship between your application code and the databases they inhabit, ensuring that SQL queries executed by your application will function correctly in an EDB Oracle-compatible environment.
Overview
Database migration is rarely limited to the database itself, it's an application migration. Even if a schema is successfully migrated, the SQL queries embedded within application code (Java, .NET, etc.) or external scripts might contain Oracle-specific syntax that fails on the target database.
By identifying these incompatibilities early, you can:
Reduce risk: Discover code-level issues before the application testing phase.
Accurate planning: Estimate the effort required for application refactoring.
Automate transformation: Leverage EDB’s transformation engine to automatically convert complex Oracle SQL to EPAS-compatible syntax.
Application records in HM
In HM, you can create an application record. The record acts as a logical container that stores metadata about the software using your databases and holds the SQL artifacts (trace files, scripts, or extracted queries) that need assessment.
Key capabilities include:
Many-to-many mapping: Associate one application with multiple schemas/databases, reflecting real-world microservices or monolithic architectures.
SQL transformation: Automatically converts Oracle DML, DCL, TCL, and DDL into EPAS-compatible versions.
Application record management limitation
Currently, the HM console supports the creation of new application records and the reading (viewing) of assessment results.
Support for updating (editing metadata) and deleting application records is planned for a future release. Ensure your application metadata and associated schemas are correct at the time of creation.
Application assessment
HM performs application assessments automatically after you create an application record and upload the SQL artifacts.
Application record creation with metadata definition: You define the application’s purpose, its tech stack, and the databases it accesses.
SQL ingestion: You upload SQL artifacts (Oracle trace
.trc, EDB Query Extractor files, or plain SQL).Assessment: The system uses the EDB PLTE engine to parse queries, and identify incompatibilities. You can then review the assessment results.
Supported import formats
HM supports three primary methods for gathering SQL statements:
| File Type | Description | Extension |
|---|---|---|
| Oracle trace | Standard files generated by the Oracle trace utility. | .trc |
| EDB Query Extractor | SQL statements extracted from Oracle Unified Auditing using EDB scripts. | .out |
| Plain SQL | Manual scripts or utility files containing standard SQL statements. | .sql |
Creating application record
Create an application record in Hybrid Manager to group SQL artifacts and assess their compatibility with EDB Postgres Advanced Server.
Reviewing assessment results
Review application SQL assessment results in Hybrid Manager to identify incompatible queries, understand suggested transformations, and plan remediation before migrating your application.