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.3Enterprise Edition
  • Product Introduction
    • Overview
    • Application scenarios
    • System architecture
    • Product form
  • Install OMA
  • Compatibility assessment
    • Overview
    • 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.3

Export SQL statements from an OceanBase database

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

Background
Command

OceanBase Migration Assessment (OMA) allows you to export DDL and SQL statements from an OceanBase database to a file to facilitate error locating.

Background

Run start.sh with reference to the sample command in this topic. For more information about the parameters in the script, see Product form. In Microsoft Windows, replace sh bin/start.sh with start.bat.

Command

sh bin/start.sh \
# The task name, which can be set to any value.
--name dump_ob \
# A fixed value. The value is DUMP.
--mode DUMP \   
# The export type. Valid values: SQL, DDL, and ALL. SQL indicates that only SQL statements are exported. DDL indicates that only DDL statements are exported. ALL indicates that SQL and DDL statements are exported.
--dump-type  ALL \
# A fixed value.
--from-type DB \  
# The type of the source database. Valid values: OBORACLE and OBMYSQL.
--source-db-type OBORACLE \
# The version of the source OceanBase database.
--source-db-version 3.1.20 \
# The IP address of the source OceanBase database.
--source-db-host xxx.xxx.xxx.xxx \
# The port number of the source OceanBase database.
--source-db-port port \  
# The complete username of the source OceanBase database. We recommend that you use the SYS user or the root user.
--source-db-user username \
# The password of the source OceanBase database.
--source-db-password password \
# The schema to be exported.
--schemas "OMT,TEST" \
# The time interval of SQL statement collection, in seconds.
--collect-interval 5 \  
# The type of the object to be exported.
--objects "TABLE,INDEX,VIEW,SEQUENCE,SYNONYM,FUNCTION,PROCEDURE,PACKAGE,PACKAGE\ BODY,TRIGGER,TYPE,TYPE\ BODY" \  
# The start time of SQL statement collection.
# The default value is a timestamp one hour before the current time, which indicates that only the SQL statements executed within the last hour are collected.
--collect-start-time "2021-12-29\ 23:23:00" \
# The end time of SQL statement collection. The default value is the current time, which indicates that the collection is performed only once.  
--collect-end-time "2021-12-29\ 23:43:00"

After you run the preceding command, OMA generates an export file in the ./dump/ directory. The file name is corresponding to the task name.

Previous topic

Assess the compatibility with business code
Last

Next topic

Overview
Next
on this page
Background
Command