All Products
Search

This Product

    ApsaraDB for OceanBase:Overview

    Document Center

    ApsaraDB for OceanBase:Overview

    Last Updated:Jun 15, 2023

    This topic describes the application scenarios and operation process of the compatibility assessment and performance assessment features of OceanBase Migration Assessment (OMA).

    Compatibility assessment

    The compatibility assessment feature of OMA systematically analyzes your database objects and SQL statements and provides automatic conversion solutions based on the best practices of migration to OceanBase Database, to significantly lower the technical barrier and reconstruction costs in migration to the cloud.

    OMA assesses the compatibility of objects and SQL or PL/SQL statements of databases, and supports database profiling.

    Feature

    Description

    Database object assessment

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

      The following lists the types and versions of databases that support object assessment:

      • Oracle databases: 11g, 12c, 18c, and 19c

      • MySQL databases: 5.6, 5.7, and 8.0

      • DB2 LUW databases (support only file collection for assessment)

      • ApsaraDB for RDS

      • PolarDB O engine

      • PolarDB MySQL engine

    • OMA can perform compatibility assessment for DDL statements in Oracle and MySQL databases and DDL statements separated with double dollar signs ($$) in TEXT files.

    • OMA can be connected to Oracle, MySQL, and DB2 LUW databases from a lightweight client and export DDL statements as files for compatibility assessment.

    Assessment of database SQL or PL/SQL statements

    • OMA can be directly connected to an Oracle database, scan the SqlArea view to obtain SQL statements of the corresponding schema, and assess the compatibility of OceanBase Database with these SQL statements.

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

    • OMA can directly parse SQL statements from MyBatis and iBatis files for compatibility assessment.

    Database profile

    • OMA can be directly connected to a source database instance and obtain the following basic information of the database instance:

      • System information such as the CPU, memory, and disk information

      • Business information such as the table schemas, proportion of tablespace to disk space, table growth rate, whether tables use indexes, and whether tables have no visits

      • Business SQL information such as whether full table scans are performed and whether multiple JOIN and WITH statements exist

    • OMA can provide optimization and rewrite solutions for certain SQL statements.

    The operation process of compatibility assessment:

    1. Collect database objects.

      You can manually collect database object definitions or use the OMA collector, which automatically collects database objects. For more information, see Collect database objects by using the OMA collector.

    2. Execute the compatibility assessment task.

      OMA supports online assessment and offline assessment. For more information, see Execute online assessment and Execute offline assessment.

    3. Execute assessment and generate a report.

      After you start an assessment task, OMA generates a corresponding assessment report based on the specified assessment type.

    4. View and download the assessment report.

      After the assessment report is generated, you can view and download it. For more information, see View and download the assessment report.

    Performance assessment

    In compatibility assessment, OMA performs feasibility analysis and provides intelligent conversion solutions for smooth migration of objects and SQL statements from a heterogeneous database. Before you switch your business applications to OceanBase Database, OMA also performs a thorough performance assessment.

    Performance assessment is performed in the following process:

    1. Enable Log Service (SLS) on your RDS instance, create a logstore , and export or upload the SQL audit file to Object Storage Service (OSS). For more information, see Prerequisite operations.

    2. Create a performance assessment task in the OMA console.

      You can select any of the following three modes for the performance assessment task as needed: Full Performance Assessment, SQL File Parsing, and SQL File Replay. For more information, see Create a performance assessment task.

    3. Launch OMA traffic load analysis.

    4. The system automatically starts the OMA load replay.

    5. OMA generates a replay report.

    Application scenarios

    OMA is applicable before you migrate data from your database system to OceanBase Database. You can use OMA to create a profile of the source database so that you can understand the current database topology, application topology, and overall database load and thereby develop proper migration strategies.

    In addition, OMA is capable of compatibility assessment for source database objects and SQL statements. This enables you to understand and handle the incompatibilities of OceanBase Database with the source database before migration, so as to ensure smooth data migration.

    You can also assess the performance of OceanBase Database in the following scenarios:

    • When you perform application load replay for data migration from a heterogeneous database, such as an RDS for MySQL database or an RDS for PostgreSQL database, to OceanBase Database.

    • When you perform a stress test on business changes or performance bottlenecks of a quasi-production cluster or a production cluster during off-peak hours.