I keep seeing the same demo. Someone copies a few hundred lines of Oracle DDL and a package body into a chat window, asks for PostgreSQL, and gets back something that looks great. It compiles. The tables are there. The functions are there. It took two minutes.
I spent a lot of years as an Oracle DBA, and my honest reaction to that demo is "nice, now let's find out what it changed."
Because an Oracle schema isn't just its DDL. A lot of how an Oracle database behaves is never written down in the schema at all. It lives in defaults, in conventions the database enforces quietly, and in code that runs when you aren't looking. A model converting text can only convert what's in the text.
This post is about those invisible parts, and a small open source tool I built to find them before anyone starts converting: azure-data-oracle2pg-toolkit .
Five things the model can't see
None of these are exotic. You will find most of them in any Oracle schema that has been in production for a while.
1.…