Coming from MySQL Moving to Oracle: Pitfalls

All my life. I have been working with MySQL for a long time and for a client we now need to work with an Oracle database for performance testing and tuning.

Any obvious mistakes when moving from MySQL to Oracle I should watch out for?

What I have discovered so far:

  • There is only one database
  • What MySQL calls in the database is the schema in Oracle
  • User and schema are almost the same (differences are still unclear here)
  • There is no automatic increase. Instead, you need to create your own sequence
  • Inserting multiple records at the same time across multiple letter tuples is not possible.
  • The number formats are localized, which can cause headaches when importing from CSV files.

More tips would be greatly appreciated. Any good resources / documented past experiences with the transition would be appreciated as well. Please note that we are not actually transferring the database from one to another, this is more about settings that I would need to do personally in my way of thinking, etc.

+2


source to share


2 answers


See these resources

Porting MySQL to Oracle Part I

Migrating MySQL to Oracle Part 2



Great tool

Oracle Migration Workbench Tool

Bye.

+3


source


If you insert or update a string that is longer than the varchar2 column length, Oracle will throw an exception. MySQL will silently truncate it. Better to double check if your code is (even unintentionally) dependent on this behavior.



+2


source







All Articles