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

V3.3.2Enterprise Edition
  • Product Introduction
    • Features
    • Application scenarios
    • System architecture
    • Product form
  • Install OMA
  • User Guide
    • 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
      • Distributed edition
        • Overview
        • Deploy workers and clients
        • Analyze and replay files

Download PDF

Document Feedback
  1. Documentation Center
  2. OceanBase Migration Assessment
  3. V3.3.2

Deploy workers and clients

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

Background
Deploy workers
Deploy clients

This topic describes how to deploy workers and clients.

Background

To deploy workers and clients on servers, decompress the GZ file on the servers. If you want to deploy multiple workers on one server, decompress the GZ file to different directories on the server.

As for the deployment, only workers are persistent. Therefore, you can deploy only workers. During each replay, you can run the corresponding command to start a client.

To deploy a worker, you must go to the corresponding folder and run the commands. Sample environment:

  • One server acts as a client. The IP address of the server is 192.168.0.10.

  • Two servers act as workers. The IP addresses of the servers are 192.168.0.20 and 192.168.0.30.

  • The network environment does not support multicast, and allows only fixed IP addresses.

Deploy workers

Access the servers where the workers are to be deployed, decompress the oma.tar.gz file, and run the following command to start the workers.

Notice:

Make sure that the value of the --name parameter is unique for each worker.

48500..48520 in --ip-addresses indicates the port range. Do not modify it.

sh bin/start.sh \
# A fixed value.
--mode WORKER \
# The name of the current worker.
--name abc
# The IP addresses of two workers. 48500..48520 indicates the port range. Do not modify it.
--ip-addresses "192.168.0.20:48500..48520,192.168.0.30:48500..48520"

The workers are started after the running of the command is completed, without the need to make any other configurations.

Deploy clients

You do not need to deploy clients. Instead, you only need to run a client when you want to start a replay task. The procedure is basically the same as that in the standalone edition.

Previous topic

Overview
Last

Next topic

Analyze and replay files
Next
on this page
Background
Deploy workers
Deploy clients