This is an original planning guide. It is not a vendor manual, an official standard, or legal advice. Example addresses use documentation ranges. Review every command before you paste it.
What this hour is for
The assessment is four steps. Inventory schemas, users, jobs, and size. Pick a target and map types. Load a copy and compare row counts and checksums. Rehearse the cutover, then switch the application connection string. It does not translate statements. The converter is a different page.
Do not cut over during the reading. Do not drop the Oracle source. Do not point the application at PostgreSQL until a copy has matching row counts. A password does not go in the inventory.
192.0.2.10, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. example.com is a documentation name. A sample password is replaced. It is not a password you keep.
The change you can finish
Apply nothing while you are writing the note. When the lab window opens, it is one change on the database named in the ticket. Read the draft, then the database, then decide.
Rollback is the backup, the file, or the snapshot you saved first. You do not invent a rollback after the only copy is gone.
- Write the inventory list.
- Write the type map as a map, not a finished schema.
- Name the copy.
- Do not switch the application.
- Stop.
Mistakes that outlive the statement
Oracle to PostgreSQL Migration goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- A cutover during the reading.
- The source dropped.
- The application pointed at the new engine early.
- A password in the inventory.
- The converter output run as if this page produced it.
Decisions to write down
One decision for Oracle to PostgreSQL Migration: The inventory is started. The copy is named. The source is still the source. And nothing was switched.
Checks before you call it done
Confirm this before you call the change done: Schemas, users, jobs, and size are listed or marked unknown. The copy is named. Row counts are still ahead. The source is still the source. And nothing was switched. If one of those fails, stop.
# Inventory, map, compare a copy, rehearse.
# This page does not convert SQL.
# Do not drop the source.
# Do not switch the application during the reading.Before you leave the database
Oracle to PostgreSQL Migration ends when the database in the prompt is the database in the ticket. If it is not, you are on the wrong database. Stop.
The draft stays a draft until a person has read the names in it. A generator does not log into the database. You delete a line that names a host, a database, or an account you did not write down.
192.0.2.10, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. example.com is a documentation name. They belong in the note. They are not values you leave on a database because a draft included them.
prompt-for-this is a reminder that a secret is missing. It is not a password, a key, or a token you save in the ticket or in git. A sample password in a draft is replaced. It is not a password you keep.
One change is the window. If two things move and the result is wrong, you will not know which one did it.
If the same step fails twice, stop for the day. Restore the copy you took first.
A second person reads the database name and the change aloud. If they cannot find them in the ticket, the note is not done.
This page is a planning guide. It is not a vendor manual, not an official standard, and not permission to touch a database you do not administer. You do not disable authentication, a firewall, or TLS to make a check pass.
Tools for this guide
These tools run in the browser on this site. They do not log into your machines.
Related pillar guides
More in this cluster
The pillar for this page, and the next published pages filed with it.