A single OceanBase Database implementation can include both MySQL and Oracle mode tenants. You may select the MySQL or Oracle compatibility mode when you create a tenant. After you create a tenant, you cannot change its compatibility mode. All its data types, SQL functions, and internal views are in line with the MySQL or Oracle mode that you selected.
MySQL mode
This tenant type is designed to reduce system retrofitting costs arising from migrating database from MySQL to OceanBase Database, and to enable database designers, developers, and administrators to get a quick start on OceanBase Database by reusing their knowledge and experience gained from using MySQL database systems. Currently, OceanBase Database supports the entire MySQL 5.6 syntax, which makes it possible to seamlessly switch business from MySQL systems.
Oracle mode
Starting from OceanBase Database 2.x, an Oracle compatibility mode was included to reduce system retrofitting costs arising from migrating database from Oracle to OceanBase Database, and to enable database designers, developers, and administrators to get a quick start on OceanBase Database by reusing their knowledge and experience gained from using Oracle database systems. Currently, OceanBase Database supports a majority of Oracle syntax and procedural language features, making it possible to automatically migrate most applications running on Oracle after minor adjustments.