OceanBase logo

OceanBase

A unified distributed database ready for your transactional, analytical, and AI workloads.

DEPLOY YOUR WAY

OceanBase Cloud

The best way to deploy and scale OceanBase

OceanBase Enterprise

Run and manage OceanBase on your infra

TRY OPEN SOURCE

OceanBase Community Edition

The free, open-source distributed database

OceanBase seekdb

Open source AI native search database

Customer Stories

Real-world success stories from enterprises across diverse industries.

View All
BY USE CASES

Mission-Critical Transactions

Global & Multicloud Application

Elastic Scaling for Peak Traffic

Real-time Analytics

Active Geo-redundancy

Database Consolidation

Resources

Comprehensive knowledge hub for OceanBase.

Blog

Live Demos

Training & Certification

Documentation

Official technical guides, tutorials, API references, and manuals for all OceanBase products.

View All
PRODUCTS

OceanBase Cloud

OceanBase Database

Tools

Connectors and Middleware

QUICK START

OceanBase Cloud

OceanBase Database

BEST PRACTICES

Practical guides for utilizing OceanBase more effectively and conveniently

Company

Learn more about OceanBase – our company, partnerships, and trust and security initiatives.

About OceanBase

Partner

Trust Center

Contact Us

International - English
中国站 - 简体中文
日本 - 日本語
Sign In
Start on Cloud

A unified distributed database ready for your transactional, analytical, and AI workloads.

DEPLOY YOUR WAY

OceanBase Cloud

The best way to deploy and scale OceanBase

OceanBase Enterprise

Run and manage OceanBase on your infra

TRY OPEN SOURCE

OceanBase Community Edition

The free, open-source distributed database

OceanBase seekdb

Open source AI native search database

Customer Stories

Real-world success stories from enterprises across diverse industries.

View All
BY USE CASES

Mission-Critical Transactions

Global & Multicloud Application

Elastic Scaling for Peak Traffic

Real-time Analytics

Active Geo-redundancy

Database Consolidation

Comprehensive knowledge hub for OceanBase.

Blog

Live Demos

Training & Certification

Documentation

Official technical guides, tutorials, API references, and manuals for all OceanBase products.

View All
PRODUCTS
OceanBase CloudOceanBase Database
ToolsConnectors and Middleware
QUICK START
OceanBase CloudOceanBase Database
BEST PRACTICES

Practical guides for utilizing OceanBase more effectively and conveniently

Learn more about OceanBase – our company, partnerships, and trust and security initiatives.

About OceanBase

Partner

Trust Center

Contact Us

Start on Cloud
编组
All Products
    • Databases
    • iconOceanBase Database
    • iconOceanBase Cloud
    • iconOceanBase Tugraph
    • iconInteractive Tutorials
    • iconOceanBase Best Practices
    • Tools
    • iconOceanBase Cloud Platform
    • iconOceanBase Migration Service
    • iconOceanBase Developer Center
    • iconOceanBase Migration Assessment
    • iconOceanBase Admin Tool
    • iconOceanBase Loader and Dumper
    • iconOceanBase Deployer
    • iconKubernetes operator for OceanBase
    • iconOceanBase Diagnostic Tool
    • iconOceanBase Binlog Service
    • Connectors and Middleware
    • iconOceanBase Database Proxy
    • iconEmbedded SQL in C for OceanBase
    • iconOceanBase Call Interface
    • iconOceanBase Connector/C
    • iconOceanBase Connector/J
    • iconOceanBase Connector/ODBC
    • iconOceanBase Connector/NET
icon

OceanBase Admin Tool

V4.3.2

  • What's New
  • Product introduction
    • What is OAT?
    • Architecture
    • Terms
  • Quick start
    • Install OAT
    • Get started with OAT
  • oatcli
  • Upgrade guide
  • User guide
    • Log in to OAT
    • Page layout of the OAT console
    • Servers
      • Add a server
      • Edit a server
      • Maintain a server
      • Remove a server
      • Manage credentials
    • Product services
      • Product service versions that support IPv6
      • Install, upgrade, roll back, and uninstall OCP
      • Install, upgrade, roll back, and uninstall ODC
      • Install, upgrade, and uninstall OMS
      • Install, upgrade, roll back, modify, and uninstall OB Sharding
      • Install, upgrade, 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 OB Sharding
      • Take over OMS
      • Take over MetaDB
      • Take over OBDNS
      • Take over InfluxDB
      • Take over NLB
      • Manage images
      • Change resources of services and components
      • Manage tools
      • Refresh data
      • Manage containers
    • Operation and maintenance
      • In-depth inspection
        • Overview
        • Configure inspection items
        • Initiate an in-depth inspection
          • Initiate an in-depth inspection for a single object
          • Initiate a global in-depth inspection
          • Initiate an in-depth inspection for multiple objects
        • View an inspection task
        • Manage an inspection report
          • View an inspection report
          • Download an inspection report
    • System security
      • Use the task center
      • Manage packages
      • Manage users
      • Audit operations
      • System parameters
        • View and modify system parameters
        • OAT configuration parameters
  • FAQ

Download PDF

What's New What is OAT? Architecture Terms Install OAT Get started with OAT oatcli Upgrade guide Log in to OAT Page layout of the OAT console Add a server Edit a server Maintain a server Remove a server Manage credentials Product service versions that support IPv6 Install, upgrade, roll back, and uninstall OCP Install, upgrade, roll back, and uninstall ODC Install, upgrade, and uninstall OMS Install, upgrade, roll back, modify, and uninstall OB Sharding Install, upgrade, 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 OB Sharding Take over OMS Take over MetaDB Take over OBDNS Take over InfluxDB Take over NLB Manage images Change resources of services and components Manage tools Refresh data Manage containers Use the task center Manage packages Manage users Audit operations FAQ
OceanBase logo

The Unified Distributed Database for the AI Era.

Follow Us
Products
OceanBase CloudOceanBase EnterpriseOceanBase Community EditionOceanBase seekdb
Resources
DocsBlogLive DemosTraining & Certification
Company
About OceanBaseTrust CenterLegalPartnerContact Us
Follow Us

© OceanBase 2026. All rights reserved

Cloud Service AgreementPrivacy PolicySecurity
Contact Us
Document Feedback
  1. Documentation Center
  2. OceanBase Admin Tool
  3. V4.3.2
iconOceanBase Admin Tool
V 4.3.2
  • V 4.5.0
  • V 4.4.1
  • V 4.4.0
  • V 4.3.2
  • V 4.3.1
  • V 4.3.0
  • V 4.2.1
  • V 4.1.2

Install OAT

Last Updated:2026-04-13 08:27:13  Updated
share
What is on this page
Prerequisites
Use the oat-all-in-one installation package to install OAT
Use the installation package to install OAT

folded

share

This topic describes how to deploy OceanBase Admin Toolkit (OAT) in a Docker container.

Prerequisites

Before you deploy OAT, make sure that the following conditions are met:

  • Your operating system meets the conditions described in the following table.

    Server type Operating system Supported version
    x86_64 or ARM aarch64 Red Hat Enterprise Linux (RHEL) and its compatible operating systems such as Rocky Linux and CentOS 7.2 and later
    x86_64 or ARM aarch64 Anolis and its compatible operating systems such as Alibaba Cloud Linux, Kylin V10, Unity Operating System (UOS), BC-Linux of China Mobile, Linx OS, and NFSChina 8.4 and later
    x86_64 or ARM AArch64 Debian and its compatible operating systems such as Ubuntu 11 and later
    x86_64 or ARM AArch64 openSUSE 12SP3 and later
    x86_64 or ARM AArch64 openSUSE 12SP3 and later
    x86_64 or ARM AArch64 Linx V6.0.99 and later
  • You have installed and started Docker. Docker Community Edition 17.03 or later is recommended. If you use the oat-all-in-one installation package to deploy OAT, the install.sh script in the package will automatically install Docker.

  • The default port 7000 of OAT is not occupied.

Use the oat-all-in-one installation package to install OAT

Note

We recommend that you use the oat-all-in-one installation package to install OAT.

The oat-all-in-one package provides images of Docker 18.09.9, OAT V4.2.0, MetaDB V4.2.1, and Network Load Balancer (NLB) 4.0.0, and software packages of common tools. To obtain the oat-all-in-one installation package, go to OceanBase Download Center and click a version based on your business requirements in the OceanBase Administrator Tool card. Then, perform the following steps to install OAT:

  1. Decompress the oat-all-in-one installation package.
tar -xf oat-all-in-one-x86.tar
  1. Run the installation script install.sh.
sh oat-all-in-one-x86/install.sh

If Docker is not installed in your environment, this command automatically installs Docker, deploys OAT to Docker, and scans for existing images and tool packages. 3. Specify the root directory of Docker and the data directory, HTTP listening port, database port, and initial login password of OAT as prompted. You do not need to manually create the specified directories. By default, the HTTP listening port of OAT is 7000 and the database port of OAT is 3306. 4. Use the returned URL to access OAT and verify the availability of OAT.

Note

  • By default, the install.sh script starts the OAT container in host network mode by using --net host. If you want to use another mode, download the OAT container and start it manually.

  • By default, the oat-all-in-one installation package for x86 contains only the images and software packages for the x86_64 and Noarch architectures, and the oat-all-in-one installation package for AArch64 contains only the images and software packages for AArch64 and Noarch architectures. If you have only the oat-all-in-one installation package for x86 or AArch64 and you want to use the images and software packages for the AArch64 or x86_64 architecture, download and copy the required images and software packages to the directory to which the OAT container is mounted, and then initiate a scan task to add the images and packages.

Use the installation package to install OAT

  1. Download the installation package of OAT.

    You need to contact OceanBase Technical Support to obtain the installation package.

  2. Run the scp command to upload the OAT installation package to the server.

    oat_server specifies the IP address of the server on which OAT is deployed.

    scp oat.tgz <oat_server_user>@<oat_server_ip>:~/
    
  3. Mount the OAT directory.

    Create a directory named /data_dir on the server to save persistent data of OAT.

    After the /data_dir directory is mounted to the OAT container, OAT automatically creates the /data_dir/logs, /data_dir/images, and /data_dir/db directories respectively for storing OAT system logs, Docker images of related components and services, and database files of OAT.

    mkdir -p /data_dir
    
  4. Load the OAT installation package as an image.

    docker load -i oat.tar
    
  5. Run the docker images command to obtain the tag of the OAT image.

    Note

    If only one OAT installation package is loaded, run the sample command. If multiple installation packages are loaded, run the docker images command to view the displayed content and connect the first two columns with a colon (:).

    oat_image=`docker images | grep oat | awk '{printf $1":"$2"\n"}'`
    
  6. Run the docker run command to start OAT.

    docker run -d --net host --name oat  -v /data_dir:/data -e OAT_INITIAL_ADMIN_PASSWORD=xxx --restart on-failure:5 $oat_image
    

    Note

    • The default HTTP listening port of OAT is 7000. You can specify the -e HTTP_PORT=7001 parameter to modify the port.

    • You can specify the -e OAT_INITIAL_ADMIN_PASSWORD=xxx parameter to change the password of OAT.

    • By default, the built-in MariaDB of OAT listens on port 3306. You can specify the -e DB_PORT=3307 parameter to modify the port.

    • We recommend that you start OAT by specifying the --net host parameter because a container started in bridge mode can be affected by docker0 bridge failures or the ip_forward parameter of the operating system.

  7. After OAT is started, enter http://<<oat_server_ip>:7000 in the address bar of the browser.

    If the login page appears, OAT is installed and started.

Previous topic

Terms
Last

Next topic

Get started with OAT
Next
What is on this page
Prerequisites
Use the oat-all-in-one installation package to install OAT
Use the installation package to install OAT