OceanBase logo

OceanBase

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

Product Overview
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

OceanBase

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

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

Download PDF

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

The Unified Distributed Database for the AI Era.

Follow Us
Products
OceanBase CloudOceanBase EnterpriseOceanBase Community EditionOceanBase seekdb
Resources
DocsBlogWhite PaperLive DemosTraining & CertificationTicket
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
Databases
  • OceanBase Database
  • OceanBase Cloud
  • OceanBase Tugraph
  • Interactive Tutorials
  • OceanBase Best Practices
Tools
  • OceanBase Cloud Platform
  • OceanBase Migration Service
  • OceanBase Developer Center
  • OceanBase Migration Assessment
  • OceanBase Admin Tool
  • OceanBase Loader and Dumper
  • OceanBase Deployer
  • Kubernetes operator for OceanBase
  • OceanBase Diagnostic Tool
  • OceanBase Binlog Service
Connectors and Middleware
  • OceanBase Database Proxy
  • Embedded SQL in C for OceanBase
  • OceanBase Call Interface
  • OceanBase Connector/C
  • OceanBase Connector/J
  • OceanBase Connector/ODBC
  • OceanBase Connector/NET
  • V 4.5.1
  • 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-06-16 06:57:16  Updated
Share
What is on this page
Prerequisites
Install OAT using the oat-all-in-one installation package
Install OAT using the OAT Docker image

folded

Share

This topic describes how to deploy OAT using Docker.

Prerequisites

Before you deploy OAT, confirm the following information:

  • Your operating system meets the following requirements:

    Server type
    Operating system
    Supported version
    x86_64/ARM aarch64 RHEL (and compatible RockyLinux, CentOS, etc.) 7.2 and later
    x86_64/ARM aarch64 Anolis (and compatible Alibaba Cloud Linux, Kylin V10, Unity Operating System (UOS), China Mobile BC-Linux, NeoKylin OS, Zhongke Fangde OS, etc.) 8.4 and later
    x86_64/ARM aarch64 Debian (and compatible Ubuntu, etc.) 11 and later
    x86_64/ARM aarch64 openSUSE 12 SP3 and later
    x86_64/ARM aarch64 openSUSE 12 SP3 and later
    x86_64/ARM aarch64 NeoKylin OS V6.0.99 and later
  • If you use an OAT image package for installation, you must have already installed and started Docker. Docker Community Edition 18.09.9 or later is recommended.

    Notice

    If you deploy OAT using the oat-all-in-one installation package, the install.sh script in oat-all-in-one will automatically install Docker. You do not need to install Docker separately.

  • The default OAT port 7000 is not occupied.

Install OAT using the oat-all-in-one installation package

Note

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

To install OAT, perform the following steps:

  1. Contact technical support to obtain the oat-all-in-one installation package for OAT.

  2. Extract the oat-all-in-one installation package.

    Example:

    tar -xf oat-all-in-one-arm-xxx.tar
    
  3. Run the installation script install.sh.

    Example:

    sh oat-all-in-one-arm/install.sh
    

    Running this command automatically installs Docker (if it is not already present in your environment), deploys OAT, and scans the images and tool software packages included in oat-all-in-one.

  4. As prompted, confirm the following information:

    1. Enter the root directory of Docker (it is recommended to set it as a separately mounted directory). The default value is /docker. You can customize this. If Docker is already installed, this step is skipped.
    2. Enter the path for the OAT data directory. The default value is /oat_data. You can customize this.
    3. Enter the OAT HTTP listening port. The default value is 7000. You can customize this.
    4. Enter the OAT database port. The default value is 3306. You can customize this.
    5. Enter the password for the OAT administrator account (set an initial login password). You can customize this.
    6. Access OAT using the returned URL to verify the availability of the OAT service.

    Example:

    Note

    Docker is already installed on the server, so the Docker installation step is skipped this time.

    1. Change the OAT data directory path to /data/oat_data and press Enter.

      Input the OAT data dir: /data/oat_data
      
    2. Use the default value for the OAT HTTP listening port and press Enter directly.

      Input the OAT HTTP listen port: 7000
      
    3. Use the default value for the OAT database port and press Enter directly.

      Input the OAT database port: 3306
      
    4. After modifying the password for the OAT administrator admin user (initial login password), press Enter.

      Input the OAT admin user password(login password): ******
      
    5. Access OAT using the returned URL to verify the availability of the OAT service.

      The return result is as follows:

      Start prepare docker
      Docker is already exists, start check...
      Already installed docker check healthy, skip install docker
      Start prepare OAT
      Loaded image: xxx/oceanbase/oat:x.x.x_20241025_arm
      45fd5a9b31b0af6aeb07b3e485503ad4c64629170b91d1d3c9e8128e8e532125
      check OAT url http://127.0.0.1:7000/hc
      OAT API not ready, please wait, sleep 5s retry...
      OAT API not ready, please wait, sleep 5s retry...
      OAT API not ready, please wait, sleep 5s retry...
      OAT API not ready, please wait, sleep 5s retry...
      OAT API not ready, please wait, sleep 5s retry...
      OAT API not ready, please wait, sleep 5s retry...
      OAT API ready
      Copy images and binary_packages to OAT data dir
      Trigger OAT scan api to find images and binary_packages
      Trigger scan task success, please visit OAT web site and wait for scan task finished
      OAT is ready for visit
      url is: http://<current_ip>:7000
      user/password is: admin/******
      

Note

  • The install.sh script starts the OAT container by default using --net host (host network mode). If you need to configure it to another network mode, manually start the container using the OAT image.
  • The x86 (aarch64) version of oat-all-in-one by default only contains images and software packages for x86 (aarch64) and noarch architectures. If you need the aarch64 (x86) architecture, download it yourself and copy it to the corresponding directory mounted by the OAT container, then initiate a scan task to add it.

Install OAT using the OAT Docker image

  1. Obtain the OAT installation package.

    Notice

    Contact OAT technical support to obtain the installation package.

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

    Here, oat_server is the IP address of the server where OAT is to be deployed.

    scp oat.tgz <oat_server_user>@<oat_server_ip>:~/
    

    Example:

    scp oat_x.x.x_20241025_arm.tgz root@xxx.xxx.xxx.xxx:/home/admin/oat_rpm
    
  3. Mount the OAT directory.

    Create a /data_dir directory on the server (the path can be customized; this example uses /data_dir) to store persistent data for 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 to store OAT system logs, Docker images for components and products, and OAT database files, respectively.

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

    docker load -i oat_xxx_xxxxxxxx_xxx.tgz
    

    Here, oat_xxx_xxxxxxxx_xxx.tgz is the name of the installation package.

    Example:

    docker load -i oat_x.x.x_20241025_arm.tgz
    

    The return result is as follows:

    Loaded image: xxx/oceanbase/oat:x.x.x_20241025_arm
    
  5. Run the docker images command to obtain the tag of the OAT image.

    Note

    If only one OAT installation package is loaded, use the example command. If multiple installation packages are loaded, run the docker images command to view the output, and concatenate the contents of 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.

    Here, $oat_image is the tag of the OAT image.

    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 HTTP service of OAT listens on port 7000 by default. You can specify the -e HTTP_PORT=7001 parameter to change it to another port.
    • You can specify the -e OAT_INITIAL_ADMIN_PASSWORD=xxx parameter to change the password of OAT.
    • OAT uses MariaDB as its data store by default. It listens on port 3306 by default. You can specify the -e DB_PORT=3307 parameter to change it to another port.
    • We recommend that you use the --net host parameter to start OAT, because a container started in bridge network mode may be affected by docker0 bridge failures or the operating system parameter ip_forward.

    Here is an example:

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

    The return result is as follows:

    490344724bfcb2801da271196ebc38b5c15547b796178dc7660553ae62b668c2
    
  7. After OAT starts successfully, enter http://<oat_server_ip>:7000 in the browser address bar.

    Replace <oat_server_ip> with the IP address of the server where OAT is deployed.

    If the login page appears in the browser window, OAT has been installed and started successfully.

Previous topic

Terms
Last

Next topic

Get started with OAT
Next
What is on this page
Prerequisites
Install OAT using the oat-all-in-one installation package
Install OAT using the OAT Docker image