OceanBase
English日本語简体中文
Docs Home
Products
Integrations
Release Notes

Databases

OceanBase DatabaseOceanBase Cloud OceanBase Best Practices

Tools

OceanBase Cloud PlatformOceanBase Migration ServiceOceanBase Developer CenterOceanBase Migration AssessmentOceanBase Admin ToolOceanBase Loader and DumperOceanBase DeployerKubernetes operator for OceanBaseOceanBase Diagnostic Tool OceanBase Binlog Service

Connectors and Middleware

OceanBase Database Proxy OceanBase Connector/C OceanBase Connector/J OceanBase Connector/ODBC OceanBase Connector/NETOceanBase Command-Line Client

Databases

OceanBase DatabaseOceanBase Cloud OceanBase Best Practices

Connectors and Middleware

OceanBase Database Proxy OceanBase Connector/C OceanBase Connector/J OceanBase Connector/ODBC OceanBase Connector/NETOceanBase Command-Line Client

Tools

OceanBase Cloud PlatformOceanBase Migration ServiceOceanBase Developer CenterOceanBase Migration AssessmentOceanBase Admin ToolOceanBase Loader and DumperOceanBase DeployerKubernetes operator for OceanBaseOceanBase Diagnostic Tool OceanBase Binlog Service
OceanBase DatabaseOceanBase Cloud ToolsConnectors and MiddlewareLifecycle Support Policy

OceanBase Migration Assessment

V4.2.0Enterprise Edition
  • Product Introduction
    • Features
    • Application scenarios
    • System architecture
    • Product form
  • Install OMA
  • Compatibility assessment
    • Assess the compatibility with objects
    • Assess the compatibility with SQL statements
    • Assess the compatibility with business code
    • Export SQL statements from an OceanBase database
    • Database assessment
      • Overview
      • Assess an Oracle database
      • Assess a MySQL database
      • Assess a TiDB database
      • Assess a PostgreSQL database
      • Assess a DB2 LUW database
  • Performance assessment
    • Standalone edition
      • Overview
      • Assess the performance differences between an Oracle database and an OceanBase database
      • Assess the performance differences between a MySQL database and an OceanBase database
      • Assess the performance differences between different versions of OceanBase Database

Download PDF

Document Feedback
  1. Documentation Center
  2. OceanBase Migration Assessment
  3. V4.2.0

Features

Last Updated:2026-09-04 08:16:35

Supported versions
Compatibility assessment
Performance assessment
Object and SQL statement export from OceanBase Database

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 the workload capture replay (WCR) files of Oracle 11g, 12c, 18c, and 19c only.

  • MySQL: 5.6, 5.7, and 8.0

  • PostgreSQL: 9, 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

  • DRDS: all versions

  • MSSQL: all versions

  • openGauss: all versions

Compatibility assessment

OMA can assess the compatibility for data migration from Oracle, MySQL, PostgreSQL, TiDB, DB2 LUW, RDS for MySQL, PolarDB for MySQL, PolarDB for Oracle, DRDS, MSSQL, and openGauss instances to OceanBase Database and generate compatibility assessment reports. The assessment report for compatibility with the Oracle and MySQL databases lists specific causes of the incompatibility and suggests corresponding solutions. The assessment reports list only the reasons for the incompatibility with other types of database instances.

OMA can assess the objects and SQL or PL statements of databases.

  • Database object assessment

    • You can directly connect OMA to the source database, automatically obtain information about objects in the source database, and assess the compatibility of OceanBase Database with the source database.

    • OMA can assess the compatibility of DDL statements in Oracle and MySQL databases. It can also assess DDL statements separated with double dollar signs ($$) in TEXT files.

    • You can use a lightweight client to connect OMA to an Oracle database and export DDL statements for compatibility assessment.

    • OMA can directly read the DDL statements exported by using MySQLDump for compatibility assessment.

    • OMA allows you to use db2look to export DDL statements for compatibility assessment.

  • Assessment of SQL or PL statements

    • You can directly connect OMA to an Oracle database, scan the V$SQL view to obtain SQL statements of the corresponding schema, and then assess the compatibility of these SQL statements with OceanBase Database.

    • OMA can assess the compatibility of SQL or PL statements that are separated with semicolons (;) or double dollar signs ($$) in TEXT files.

    • OMA can directly parse SQL statements in MyBatis and iBatis files to assess the compatibility of these statements.

    • You can directly connect OMA to an Oracle database, periodically scan the V$SQL view to obtain all SQL statements in a specific period, and then assess these SQL statements.

    • You can directly connect OMA to a DB2 LUW database, periodically scan the snapshots for dynamic SQL statements to obtain all SQL statements in a specific period, and then assess these SQL statements.

  • Database assessment

    The database assessment feature allows you to assess 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 SQL replay and stress testing.

  • You can connect OMA to the source database, collect SELECT statements, and then replay the SQL statements in an OceanBase database to verify the compatibility of the SQL statements and the performance of OceanBase Database.

  • OMA allows you to collect the workload capture replay (WCR) files of an Oracle database, parse the WCR files to obtain SQL statements, and then assess the compatibility of the SQL statements. You can also replay the SQL statements in an OceanBase database to verify their accuracy and performance.

  • OMA can parse and replay the general log files of MySQL databases.

  • During the upgrade of an OceanBase database, OMA supports pulling query statements from the database before the upgrade and replaying the statements in the database after the upgrade.

Object and SQL statement export from OceanBase Database

  • OMA allows you to export DDL statements for objects in the corresponding schema from an OceanBase database.

  • OMA allows you to export all SQL statements in the SQL_AUDIT view for a specific period from an OceanBase database.

Next topic

Application scenarios
Next
on this page
Supported versions
Compatibility assessment
Performance assessment
Object and SQL statement export from OceanBase Database