Tips and Tricks for Migrating from Oracle to MariaDB
summary
Migration strategy focuses on concrete gaps: SQL_MODE=ORACLE gives PL/SQL syntax and data type aliases but does not add new types and can map Oracle NUMBER to double by default, so inspect column values and choose INT/BIGINT/DECIMAL instead. Schema migration covers varchar/NVARCHAR, DATE→DATETIME, BLOB/CLOB API differences, and sequences→AUTO_INCREMENT. Procedural code runs under SQL PL but DBMS_SQL not supported and dynamic SQL often needs rewrite; many object types get replaced with JSON or normalized tables. Test on staging and plan effort per procedure.
AI-written summary · about
chapters (7)
- 0:00Intro
- 0:39Agenda
- 2:27Intro to migration
- 5:30High level Differences
- 9:59SQL_MODE=ORACLE?
- 12:10Schema migration
- 22:14Conclusion
related talks
16mMigrating from other databases to MariaDB
22mMigration from Oracle to MariaDB with no application change
06mMigration Consideration Oracle to PostgreSQL
41mMariaDB The New MySQL
47mOn the past, present and future of Open Source databases
40mMySQL at Scale: Booking MariaDB to MySQL Migration
33mMigrating from Oracle to
19mMariaDB Roles