MySQL and the Oracle DBA

After 10 years I have come back to MySQL and there is quite a lot of things which may concern an Oracle DBA.

MySQL and Oracle live under the same company roof
as I have predicted 12 years ago and the results of the meanwhile peaceful  conjugal live have turned out to be impressing for Oracle DBA's as well.

I am focussing here on the flagship SqlDeveloper. Even Oracle's critics e.g. TechRepublic acknowledge some features.

My esteemed colleague Rex Baldazo would certainly share my view, that the latest improvements in migrating technology have been implemented very well in SqlDeveloper 4.1.

I have permitted myself to apply the capabilities of that tool in my latest project train.oracle12.migration in a very special way.

Step by step

 click on the pictures to enlarge

1. There is a MySQL installation on my host and I want to work SqlDeveloper on that. Let us create a new connection with these properties:

Note the connection types Oracle and MySQL. How to arrange for that see Martin Berger  unfortunately only in German or look for equivalents.

It's  quite simple: find the ODBC driver for your RDBMS (Sybase, MS SqlServer, MS Access, MySQL, PostgreSql, IBM DB2, Teradata, Informix) and insert it into to Preferences here:

2.  Test the connection

and note the existing databases. classicmodels is the equivalent for the EXAMPLE tablespace well
known to all Oracle DBAs.

3.  Enjoy the known features











i.e. display quickly all aspects of a table.

4. Enjoy some new feature

and look at the referential embedding of the table.

5. Why do I do that ? - The sense of all that is: i want to migrate this MySQL database into an Oracle12c database using the Migration feature of SqlDeveloper.

6. Create a project

7. Choose the source database

 8. Choose the source schema

9. Specify the conversion rules

10. Choose the target database for the repository

FTEX is an Oracle12c daabase in the guest VM. After some last control steps you start the data move, which takes less than 2 minutes.


And now comes the first joy and the first disappointment.

The first joy is, that you see in the target database the new new Oracle tables under the user schema classicmodels.

As usual, SqlDeveloper shows all atrributes of the tables, but one: there is no data. Why that?

To find the cause, you have to look into the repository. After a migration, there is a table MIGRLOG in the user schema SYSTEM. And here you see the reason:

The user CLASSICMODELS was created by the the migration scripts without the privileges to his default tablespace USERS. This is minor error. After granting the privileges - alter user classicmodels quota unlimited on users; - you can repeat the migration and see the result:

Conclusion:
Not bad at all. There is the other possibility of an offline migration, with the scripts in the output directory:

Enjoy your own tests.