Oracle's CO (Customer Orders) schema is the modern replacement for the older OE schema.
It ships with Oracle 19c, it is actively maintained, and it is built the way most real Oracle applications are built today: IDENTITY columns instead of sequence-trigger pairs, JSON stored in BLOB columns, and views that use Oracle-specific SQL functions.
Ejecuté la migración completa usando ora2pg 25.0 con Oracle 19c como origen y PostgreSQL 18 como destino.
This post covers the five problems that required manual intervention — and why each one will appear in almost every production schema you migrate.
This is the third post in the series.
En HR schema post covered sequence-trigger patterns, %TIPO parameters, and the FK re-apply bug.
En SH schema post covered partitioned tables, bitmap indexes, and materialized views.
CO introduces three new problem categories not seen in either of those.
Continuar leyendo “Oracle to Postgres Migration: CO Schema Issues and Fixes”