From migrating-oracle-to-postgres-stored-procedures
Migrates Oracle PL/SQL stored procedures to PostgreSQL PL/pgSQL, translating Oracle-specific syntax while preserving method signatures and type-anchored parameters. Use during Oracle-to-PostgreSQL database migrations.
How this skill is triggered — by the user, by Claude, or both
Slash command
/migrating-oracle-to-postgres-stored-procedures:migrating-oracle-to-postgres-stored-proceduresThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Translate Oracle PL/SQL stored procedures and functions to PostgreSQL PL/pgSQL equivalents.
Translate Oracle PL/SQL stored procedures and functions to PostgreSQL PL/pgSQL equivalents.
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:
PARAM_NAME IN table_name.column_name%TYPE).NUMERIC, VARCHAR, INTEGER) for output parameters passed to other procedures — do not type-anchor these.COMMENT or GRANT statements.COLLATE "C" only when Oracle-compatible binary ordering is required and no other sort order is specified.NLS_SORT = French), map to an explicit PostgreSQL locale collation instead of "C".SELECT collname, collprovider, collcollate, collctype FROM pg_collation ORDER BY collname; to discover collations in the target environment.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).orafce extension when it improves clarity or fidelity.Consult the PostgreSQL table/view definitions at .github/oracle-to-postgres-migration/DDL/Postgres/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/Procedures and Functions/{PACKAGE_NAME_IF_APPLICABLE}/. One procedure per file.
npx claudepluginhub simplycubed/skills --plugin migrating-oracle-to-postgres-stored-proceduresIdentifies Oracle-to-PostgreSQL migration risks by cross-referencing code against behavioral differences (empty strings, refcursors, type coercion, sorting, timestamps). Use when planning or validating a database migration.
Orchestrates Oracle to ScalarDB migration: collects DB connection params, updates config, runs schema extraction, migration analysis, AQ integration, and SP/trigger-to-Java conversion.
Generates, validates, and deploys stored procedures, functions, and triggers for PostgreSQL, MySQL, SQL Server with error handling and transactions. Trigger on 'generate stored procedure' or similar.