Thanks, Muhammad!Sent from my iPhone On Jul 23, 2024, at 12:55 PM, Muhammad Ikram <mmikram@xxxxxxxxx> wrote:
Hi Ron,
An explanation here about what I said above. EDB's Migration toolkit is not a choice if you want to migrate code objects (Procedures, Packages, Functions, Triggers etc) to community PostgreSQL. Migration Portal again assesses and converts for EDB Postgres which is much Oracle compatible. EDB Migration toolkit can be good for data objects and data transfer to Community Postgres. If you want to migrate to EDB Postgres (EPAS) then these tEDB ools are best for migrating code and data objects including data.
For Oracle to Community Postgres Ora2PG is good enough
Regards, Muhammad Ikram Bitnine.
Hi,
Three tools I know which can help .
Ora2pg : A free tool that helps in migration of schema and data both. Rich in options and best suits for target vanila PG.
EDB’s Migration toolkit can migrate both schema and dara but for vanila PG code objects won’t migrate. Amazon SCT converters schema and Amazon has service to migrate data.
Regards, Muhammad Ikram
Bitnine Global
Howdy,
We have a project to migrate our Oracle databases that are hosted on an Oracle Database Appliance to Postgres hosted on a Linux VM. Questions:
- Is there a tool out there that we can use to analyze resource sizing on the Appliance that will give resource sizing recommendations for the VM?
The appliance doesn't tell you how much space your database uses???
Anyway, we converted an 8TB on-prem Oracle 12 db (heavy on CLOBs) to RDS Postgresql 12; the resulting db was about 6TB. I'm sure that vanilla PG would be about the same size (or smaller now, since compression on dupes-allowed b-tree indices is much better now than in PG 12). - Is there a schema conversion tool or similar out there that we can use to convert Oracle ==> Postgres?
As Keith said, Google is your friend.
That's how I found ora2pg, which we used in our conversion project (for the data only; someone had to rewrite all the stored procedures).
If you use ora2pg, remember to tell it to convert all of the NUMERIC(38,0) columns to BIGINT.
--
|
