RE: MySQL to Oracle Migration

From: Jeff Smith <jeff.d.smith_at_oracle.com>
Date: Wed, 17 Dec 2014 10:04:07 -0800 (PST)
Message-ID: <ae060074-9038-4e0b-88c9-e7e9491e5acd_at_default>

One advantage of using SQL Developer, other than it being free, is that when you migrate your objects, it creates a data model first. If a column or table name is changed based on an incompatible identifier - maybe it's too long or contains a keyword - that propagates to the rest of the model.

There are many other advantages...

25gb you could probably get away with doing an online migration, but I'd do the offline one. It will unload your data to SQL*Loader files that you can upload at your convenience to your new Oracle schema.

Oracle Workbench Migration is deprecated - all that it WAS, is now SQL Developer. Unless you're moving Informix.

Jeff

From: Alex Nunes [mailto:alex.nunes.xmn_at_gmail.com] Sent: Wednesday, December 17, 2014 11:38 AM To: oracle-l_at_freelists.org
Subject: MySQL to Oracle Migration

Greetings Oracle-L,
I am seeking your expert advice (ideas and/or proven solutions as well as any pitfalls) on ways to migrate data from MySQL (v. 5.6.19) to Oracle 11g R2. The data volume in question here is around 25gb (small) but there are 160 tables that needs to be migrated to Oracle. Business can afford to take an outage for this migration. So far I came up with this initial list:

1) GoldenGate: seems an overkill for me.
2) SQL Developer
3) Oracle Workbench Migration
4) Export -> flat files / Sql*Loader

Thanks in advance for any info on this.
Alex Nunes

--
http://www.freelists.org/webpage/oracle-l

Received on Wed Dec 17 2014 - 19:04:07 CET