The run
Follow ERP-Oracle to ERP-PG from start to switch-over
Oracle Database 19c to PostgreSQL 16.4 for Meridian Retail (example), with 5 schemas, 1,036 tables and 540 code objects.
- 1
Stage 1 · Assess
See the whole job before it starts
Datalobe reads every schema, table and code object, then scores readiness and lists what needs a person.
- 1,036 tables and 540 code objects in scope
- 214 findings, grouped by code
- Readiness 71 of 100
Assessment Report
ERP-Oracle to ERP-PG / Assessment Report
Ready with remediation71of 100
- Tables
- 1,036
- Rows
- 2,141,876,402
- Columns
- 71,940
- Constraints
- 7,969
- Indexes
- 4,212
- Code objects
- 540
Top findings
- DFLUX-301CONNECT BYINV.V_STOCK_POSITION and 17 views
- DFLUX-305Package stateFIN.PKG_GL_POSTING and 9 packages
- DFLUX-322NUMBER without precision1,284 columns
Stage 1 of 5
- 2
Stage 2 · Plan and convert
Agree the plan, review the code
Fixed rules convert tables, columns, types, keys and the data copy. AI converts stored code (procedures, functions, triggers, complex views). Nothing AI-written is deployed silently.
- Code first, then 3 waves
- In the example run, 540 of 540 compiled on the target before deploy
- Plan approved 1 Oct 2026, 16:20 UTC
Migration Plan
ERP-Oracle to ERP-PG / Migration Plan
- First540 code objects
- Wave 1COMMONHR
- Wave 2INVFIN
- Wave 3SALES
Decisions
- NUMBER without precision to NUMERIC(38,10)Sarah Mitchell
- CHAR(1) 'Y'/'N' to BOOLEANapproved
Plan approved 1 Oct 2026, 16:20 UTC · Sarah Mitchell
Stage 2 of 5
- 3
Stage 3 · Migrate and sync
Copy in parallel, keep the target current
Data moves by schema in parallel. Change capture keeps PostgreSQL in step with Oracle until switch-over.
- 2,141,876,402 rows in 13 h 48 min
- 43,100 rows/s average, 61,200 peak in the example run
- 1,204,318 changes synced
ERP-Oracle to ERP-PG / Run progress
Rows copied
2,141,876,402
- SALES312 tables
- FIN248 tables
- INV196 tables
- HR142 tables
- COMMON138 tables
- Average
- 43,100 rows/s
- Peak
- 61,200 rows/s
- Copy time
- 13 h 48 min
Changes synced 1,204,318 · lag at cut-over 4 s
Stage 3 of 5
- 4
Stage 4 · Validate
Check everything against the source
17 checks run on every table in six groups, and deterministic read-only functions are executed on both databases. Code computes the verdict.
- 17,612 check runs, 0 failed in the example run
- 7 FIN rounding warnings accepted by Sarah Mitchell
Validation ReportCertificate of Migration
ERP-Oracle to ERP-PG / Validation Report
- Checks
- 17,612
- Failed
- 0
- Warnings accepted
- 7
- Row counts match on 1,036 tables
- Values compared
- Keys and constraints hold
- 7 rounding warnings accepted by Sarah Mitchell
- 61 functions give the same answers
Stage 4 of 5
- 5
Stage 5 · Cut over
Switch over with the evidence in hand
Applications switch from Oracle to PostgreSQL once lag is low and the verdict is in.
- Lag at switch-over 4 s in the example run
- Downtime 18 min in the example run
Migration Report
ERP-Oracle to ERP-PG / Cut-over summary
Downtime
18 min
- Cut-over 4 Oct 2026, 02:00 UTC
- Lag at cut-over 4 s
- Applications switched to ERP-PG
Stage 5 of 5