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 NLB

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

Prerequisites
Procedure
What to do next

This topic describes how to take over NLB 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 NLB, make sure that the following conditions are met:

  • You have added the image used by NLB.
  • You have installed OAT and logged on as either a super administrator or an O&M engineer. For more information, see Install OAT.
  • You have added a server where NLB is to be installed. For more information, see Add a server.
  • The server meets the requirements for installing NLB.

Procedure

To install NLB, perform the following steps:

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

  2. On the Component Management page, click Take Over Component in the upper-right corner, and choose Take Over NLB.

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

    The following table describes the basic parameters of NLB.

    Parameter
    Description
    NLB Image The Docker image of NLB.
    Component Name The name of the component, which must be unique. Default value: NLB.
    Server The IP address of the server where NLB is to be installed.
    CPU The number of CPU cores on the server available for NLB. Default value: 32C.
    Memory The memory on the server available for NLB. Default value: 90G.
  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 NLB, you can take over other products. For more information, see Take over products.

Previous topic

Take over InfluxDB
Last

Next topic

Manage images
Next
on this page
Prerequisites
Procedure
What to do next