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 Admin Tool

V4.2.1
  • What's New
  • Product introduction
    • What is OAT?
    • Architecture
    • Concepts
  • Quick start
    • Install OAT
    • Get started with OAT
  • oatcli
  • Upgrade guide
  • User guide
    • Log on to OAT
    • Page layout of the OAT console
    • Servers
      • Add a server
      • Edit a server
      • Perform O&M operations on a server
      • Remove a server
      • Manage credentials
    • Product services
      • Install, upgrade, and uninstall OCP
      • Install, upgrade, and uninstall ODC
      • Install, upgrade, and uninstall OMS
      • Install, Upgrade, Modify, and Uninstall OBSharding
      • Install and uninstall MetaDB
      • Install and uninstall OBDNS
      • Install and uninstall InfluxDB
      • Install and uninstall NLB
      • Install and uninstall OpenSearch
      • Install and uninstall SQLAuditStore
      • Install and uninstall OBLB
      • Take over OCP
      • Take over ODC
      • Take over OBSharding
      • Take over OMS
      • Take over MetaDB
      • Take over OBDNS
      • Take over InfluxDB
      • Take over NLB
      • Manage images
      • Modify the resources of products and components
      • Manage tools
      • Refresh data
      • Container operations
    • System security
      • Task center
      • Package management
      • User management
      • Operation audit
      • System parameter
        • View and modify system parameters
        • OAT configuration parameters
  • FAQ

Download PDF

Document Feedback
  1. Documentation Center
  2. OceanBase Admin Tool
  3. V4.2.1

Take over OMS

Last Updated:2026-09-03 09:50:14

Prerequisites
Procedure
What to do next

This topic describes how to take over OceanBase Migration Service (OMS) in the OceanBase Admin Toolkit (OAT) console. Earlier versions of OAT cannot be smoothly upgraded to the current version because the new version has been restructured. Therefore, the current version of OAT must take over the products and components deployed by using earlier versions of OAT to monitor their status and manage their upgrades.

Prerequisites

Before you take over OMS, make sure that the following conditions are met:

  • You have added the image used by OMS.

  • You have taken over the components that OMS depends on.

  • You have added a server to take over OMS. For more information, see Add a server.

  • The server meets the requirements for taking over OMS.

Procedure

To take over OMS, perform the following steps:

  1. In the left-side navigation pane, choose Product Service > Product Management.

  2. On the Product Management page, click Take Over Products in the upper-right corner, and choose Take Over OMS.

  3. On the Take Over OMS page, configure the parameters.

    The following table describes the basic parameters of OMS.

    Parameter
    Description
    OMS Image The Docker image of OMS.
    Product Name The name of the product, which must be unique.
    Server The IP address of the server to take over OMS.
    CPU The number of CPU cores on the server available for OMS. Default value: 8C.
    Memory The memory on the server available for OMS. Default value: 20G.

    The following table describes the MetaDB parameters of OMS.

    Parameter
    Description
    MetaDB Type Select the type of MetaDB.
    Select Created MetaDB Select an existing MetaDB for OMS.

    The following table describes the InfluxDB parameters of OMS.

    Parameter
    Description
    Time Series Database Storage Select the type of InfluxDB.
    Select Created InfluxDB Select an existing InfluxDB for OMS.

    The following table describes the load balancing parameters, which are optional.

    Parameter
    Description
    Load Balancing Mode Select the load balancing mode.
    MetaDB TCP Proxy IP The TCP address for connecting to MetaDB.
    MetaDB TCP Proxy Port The TCP port number for connecting to MetaDB.
  4. After you set the parameters, click Submit. You can also click Reset to restore to the default configurations.

What to do next

After you take over OMS, you can upgrade it. For more information, see Upgrade OMS.

Previous topic

Take over OBSharding
Last

Next topic

Take over MetaDB
Next
on this page
Prerequisites
Procedure
What to do next