This topic describes the features of OceanBase Migration Assessment (OMA), including compatibility assessment and performance assessment.
Supported versions
OMA supports the following database types and versions:
Oracle: 11g, 12c, 18c, and 19c
Notice:
OMA can replay only the workload capture replay (WCR) files of Oracle databases 11g, 12c, 18c, and 19c.
MySQL: 5.6, 5.7, and 8.0
PostgreSQL: 10, 11, 12, 13, and 14
TiDB: 3.0, 4.0, and 5.0
DB2 LUW: 10.1.0, 10.5.0, 11.1, and 11.5
RDS for MySQL: all versions
PolarDB for MySQL: all versions
PolarDB for Oracle: all versions
Compatibility assessment
OMA can assess the compatibility of OceanBase Database with Oracle, MySQL, PostgreSQL, TiDB, and DB2 LUW databases and provide a compatibility report. The assessment report for compatibility with the Oracle database lists specific causes of the incompatibility and suggests corresponding solutions. The assessment report for compatibility with the MySQL, PostgreSQL, TiDB, or DB2 LUW database contains only the compatibility assessment result.
OMA can assess the objects and SQL or PL/SQL statements of databases.
Database object assessment
Directly accesses the source database, automatically obtains information about the objects in the source database, and assesses the compatibility of OceanBase Database with the source database.
Assesses the compatibility with DDL statements in Oracle and MySQL databases, as well as DDL statements separated with double dollar signs ($$) in TEXT files.
Accesses an Oracle database from a lightweight client and exports DDL statements for compatibility assessment.
Directly reads the DDL statements exported by MySQLDump for compatibility assessment.
Allows you to extract DDL statements by using the db2look tool for compatibility assessment.
Assessment of database SQL or PL/SQL statements
Directly accesses an Oracle database, directly scans the V$SQL view to obtain SQL statements of the corresponding schema, and assesses the compatibility with OceanBase Database.
Assesses the compatibility with SQL or PL/SQL statements separated with semicolons (;) or double dollar signs ($$) in TEXT files.
Directly parses SQL statements in MyBatis and iBatis files to assess their compatibility.
Directly accesses an Oracle database, scans the V$SQL view periodically to obtain all SQL statements in a specific period of time, and assesses the SQL statements.
Directly accesses a DB2 LUW database, scans the snapshot for dynamic SQL statements periodically to obtain all SQL statements in a specific period of time, and assesses the SQL statements.
Database assessment
The database assessment feature allows you to perform the assessment of objects, SQL statements, and database profiles in one assessment task and view the corresponding assessment results in one report.
OMA supports different database assessment modes for Oracle, MySQL, TiDB, PostgreSQL, and DB2 LUW databases. For more information, see Database assessment.
Performance assessment
OMA supports replay and stress testing for SQL statements:
Accesses the source database, collects SELECT statements, and replays the SQL statements in an OceanBase database to verify the compatibility with the SQL statements and the performance of OceanBase Database.
Parses the WCR files of an Oracle database, and assesses the compatibility with the obtained SQL statements, or replays the SQL statements in an OceanBase database to verify the accuracy and performance of the SQL statements.
Parses and replays the General Log file of MySQL databases.
During an upgrade of OceanBase Database, pulls query statements from the OceanBase database of an earlier version and replays the statements in an OceanBase database of a later version.
Export OceanBase Database objects and SQL statements
Exports the DDL statements of objects in the corresponding schema from OceanBase Database.
Exports all SQL statements in the SQL_AUDIT view of a specific period of time from OceanBase Database.