mcpField
M
migrating-oracle-to-postgres-stored-procedures

migrating-oracle-to-postgres-stored-procedures

github.com/githubData & databases40.5k1.8k installsUpdated 1d ago
Repository

About migrating-oracle-to-postgres-stored-procedures

A skill for translating Oracle PL/SQL stored procedures and functions into PostgreSQL PL/pgSQL. It guides source and schema inspection, applies explicit translation constraints, and specifies where each output procedure is saved.

Key features

  1. 01Read Oracle procedure and schema definitions
  2. 02Translate Oracle syntax to PostgreSQL equivalents
  3. 03Preserve signatures and specified control flow
  4. 04Review collation and UNION ALL behavior
  5. 05Write one procedure per output file

Use cases

  1. 01Port an Oracle stored procedure to PostgreSQL
  2. 02Translate functions using target schema details
  3. 03Review ordering and collation choices
  4. 04Prepare procedure files in the required output layout

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/github/awesome-copilot --skill migrating-oracle-to-postgres-stored-procedures

After installing, type/migrating-oracle-to-postgres-stored-proceduresin Claude Code to confirm it loaded.

Details

From the project README

Migrating Stored Procedures from Oracle to PostgreSQL

Translate Oracle PL/SQL stored procedures and functions to PostgreSQL PL/pgSQL equivalents.

Workflow

Progress:
- [ ] Step 1: Read the Oracle source procedure
- [ ] Step 2: Translate to PostgreSQL PL/pgSQL
- [ ] Step 3: Write the migrated procedure to Postgres output directory

Step 1: Read the Oracle source procedure

Read the Oracle stored procedure from .github/oracle-to-postgres-migration/DDL/Oracle/Procedures and Functions/. Consult the Oracle table/view definitions at .github/oracle-to-postgres-migration/DDL/Oracle/Tables and Views/ for type resolution.

Step 2: Translate to PostgreSQL PL/pgSQL

Apply these translation rules:

  • Translate all Oracle-specific syntax to PostgreSQL equivalents.
  • Preserve original functionality and control flow logic.
  • Keep type-anchored input parameters (e.g., PARAM_NAME IN table_name.column_name%TYPE).
  • Use explicit types (NUMERIC, VARCHAR, INTEGER) for output parameters passed to other procedures — do not type-anchor these.
  • Do not alter method signatures.
  • Do not prefix object names with schema names unless already present in the Oracle source.
  • Leave exception handling and rollback logic unchanged.
  • Do not generate COMMENT or GRANT statements.
  • Apply collation intentionally when ordering text:
    • Use COLLATE "C" only when Oracle-compatible binary ordering is required and no other sort order is specified.
    • If Oracle used explicit linguistic sorting (for example NLS_SORT = French), map to an explicit PostgreSQL locale collation instead of "C".
    • Use SELECT collname, collprovider, collcollate, collctype FROM pg_collation ORDER BY collname; to discover collations in the target environment.
  • Treat UNION ALL as a review checkpoint. Validate plan quality per branch and restructure if combined-branch planning causes regressions (for example, unexpected sequential scans on large tables).
  • Leverage the orafce extension when it improves clarity or fidelity.

Consult the PostgreSQL table/view definitions at .github/oracle-to-postgres-migration/DDL/Postgres/{ProjectName}/Tables and Views/ for target schema details.

Step 3: Write the migrated procedure to Postgres output directory

Place each migrated procedure in its own file under .github/oracle-to-postgres-migration/DDL/Postgres/{ProjectName}/Procedures and Functions/{PACKAGE_NAME_IF_APPLICABLE}/. One procedure per file.

{ProjectName} is the project's assembly/folder name with spaces normalized to - (e.g. MyApp.DataAccess). This matches the path used by the agent and other migration skills.

Comments

Markdown supported