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 Deployer

V4.3.0Community Edition
  • What is obd
  • Quick Start
    • Install obd
    • Quick deployment of OceanBase Database
    • Quickly deploy OCP
  • obd Command
    • Quick deployment commands
    • Cluster commands
    • Command groups
    • Image and repository commands
    • Test command groups
    • Tool commands
    • obdiag commands
    • Binlog service commands
    • Hardware commands
    • License commands
    • Password commands
    • Telemetry commands
  • User Guide
    • Usage overview
    • Deploy through GUI
      • Overview
      • Pattern configuration rules
      • Deploy an OceanBase cluster
      • Deploy OCP
      • Deploy OMS
      • Change components
      • Upgrade OCP
      • Upgrade OMS
    • Deploy through CLI
      • Configuration file
      • Component deployment
        • Deploy an OceanBase cluster
        • Deploy seekdb
        • Deploy obconfigserver
        • Deploy OMS
        • Deploy OCP
        • Deploy Alertmanager
        • Deploy obbinlog
        • Deploy oblogproxy
      • Cluster management
        • Physical Standby Database
          • Create a standby tenant
          • Role switching and decoupling
          • Switch the synchronization mode between primary and standby tenants
        • seekdb primary/standby instance
          • Create a standby instance
          • Role switching and decoupling
        • Scale out and component changes
        • Performance test
        • Diagnose a cluster
        • Backup and restore
        • Add a GUI monitoring system to an existing cluster
      • Cluster management
        • Use OCP to take over an OceanBase cluster deployed by obd
        • Take over an OceanBase cluster
      • Component upgrade
        • Upgrade OceanBase Database
        • Upgrade ODP
        • Upgrade OMS
  • Upgrade obd
  • FAQ
  • Error codes
  • Release Notes
    • Version rules
    • V4.3
      • OceanBase Deploy V4.3.0
    • V4.2
      • OceanBase Deployment Tool V4.2.0
    • V4.1
      • OceanBase Deployer V4.1.0
    • V4.0
      • OceanBase Deployer V4.0.0
    • V3.6
      • OceanBase Deployer V3.6.0
    • V3.5
      • OceanBase Deployer V3.5.0
    • V3.4
      • OceanBase Deployer V3.4.0
    • V3.3
      • OceanBase Deployer V3.3.0
    • V3.2
      • OceanBase Deployer V3.2.2
      • OceanBase Deployer V3.2.1
      • OceanBase Deployer V3.2.0
    • V3.1
      • OceanBase Deployer V3.1.2
      • OceanBase Deployer V3.1.1
      • OceanBase Deployer V3.1.0
    • V3.0
      • OceanBase Deployer V3.0.1
      • OceanBase Deployer V3.0.0
    • V2.10
      • OceanBase Deployer V2.10.1
      • OceanBase Deployer V2.10.0
    • V2.9
      • OceanBase Deployer V2.9.2
      • OceanBase Deployer V2.9.1
      • OceanBase Deployer V2.9.0
    • V2.8
      • OceanBase Deployment Tool V2.8.0
    • V2.7
      • OceanBase Deployment Tool V2.7.0
    • V2.6
      • OceanBase Deployment Tool V2.6.2
      • OceanBase Deployment Tool V2.6.1
      • OceanBase Deployment Tool V2.6.0
    • V2.5
      • OceanBase Deployer V2.5.0
    • V2.4
      • OceanBase Deployer V2.4.0
    • V2.3
      • OceanBase Deployment Tool V2.3.1
      • OceanBase Deployer V2.3.0
    • V2.2
      • OceanBase Deployment Tool V2.2.0
    • V2.1
      • OceanBase Deployer V2.1.1
      • OceanBase Deployment Tool V2.1.0
    • V2.0
      • OceanBase Deployment Tool V2.0.1
      • OceanBase Deployment Tool V2.0.0
    • V1.6
      • OceanBase Deployer V1.6.2
      • OceanBase Deployer V1.6.1
      • OceanBase Deployer V1.6.0
    • V1.5
      • OceanBase Deployer V1.5.0
    • V1.4
      • OceanBase Deployer V1.4.0
    • V1.3
      • OceanBase Deployer V1.3.3
      • OceanBase Deployer V1.3.2
      • OceanBase Deployer V1.3.0
    • V1.2
      • OceanBase Deployer V1.2.1
      • OceanBase Deployer V1.2.0
  • Interactive deployment of OceanBase Database Community Edition
  • Deploy a Community Edition cluster using the obd graphical interface
  • Deploy a Community Edition cluster by using an obd configuration file

Download PDF

Document Feedback
  1. Documentation Center
  2. OceanBase Deployer
  3. V4.3.0

Quick deployment commands

Last Updated:2026-09-04 08:21:29

obd demo
Examples
obd perf
Examples

This topic describes the quick deployment commands of obd. You can deploy and start a specified component on the local server without specifying a configuration file.

You can use the -h or --help option in each command to view the help information of the command. You can also use the -v or --verbose option to view the detailed execution process of the command when an error occurs.

obd demo

You can use this command to deploy and start the specified component in OceanBase Database with the minimum specifications on your local server without specifying a configuration file. The deployment name is fixed to demo. After deployment, you can view the cluster list by running the obd cluster list command and manage the cluster by using other cluster commands, such as obd cluster display demo.

obd demo [-c/--components] 

The following table describes the options.

Option
Required
Data type
Default value
Description
-c/--components No string oceanbase-ce,obproxy-ce,obagent,prometheus,grafana The list of components to be deployed, separated by commas (,).

By default, this command deploys the components with the minimum specifications in the home directory of the current user. The deployed component version is the latest version. The supported components are: oceanbase-ce, oceanbase, oceanbase-standalone, obproxy-ce, obproxy, obagent, grafana, prometheus, and ob-configserver.

Note

Starting from V2.9.0, you can use the obd demo command to deploy the ob-configserver component. Starting from V3.2.0, you can use the obd demo command to deploy the oceanbase-standalone component. Starting from V3.4.0, you can use the obd demo command to deploy the oceanbase and obproxy components.

Examples

You can use options to specify the deployment version and configuration. For example:

Specify components

  • Deploy OceanBase Database Community Edition and ODP

    obd demo -c oceanbase-ce,obproxy-ce
    
  • Deploy only obconfigserver

    obd demo -c ob-configserver
    

Specify component versions

  • Deploy components with specified versions

    obd demo -c oceanbase-ce,obproxy-ce --oceanbase-ce.version=4.3.2.0
    
  • Deploy components with specified hash values

    obd demo -c oceanbase-ce,obproxy-ce --oceanbase-ce.package_hash=f38723204d49057d3e062ffad778edc1552a7c114622bf2a86fea769fbd202ea
    

Specify component configurations

This example specifies the installation path and port of components. For more information about the related configuration items in the configuration file, see the Configuration item description section in Configuration file description.

Notice

This command supports only the first-level configuration items under global.

  • Specify the installation path of components

    Deploy oceanbase-ce and obproxy-ce to the /data/demo directory and create the corresponding working directories for the components.

    obd demo -c oceanbase-ce,obproxy-ce --home_path=/data/demo
    
  • Specify the installation path of a specific component

    Deploy oceanbase-ce to the home directory of the current user and create the corresponding working directory for the component. Deploy obproxy-ce to the /data/demo/obproxy-ce directory.

    obd demo -c oceanbase-ce,obproxy-ce --obproxy-ce.home_path=/data/demo/
    
  • Specify the port of components

    obd demo --oceanbase-ce.mysql_port=3881
    

obd perf

You can use this command to deploy and start the specified component on the specified server in the maximum specification without specifying a configuration file. The deployment name is fixed to perf. After the deployment, you can run the obd cluster list command to view the cluster list and see the cluster. You can also manage the cluster by using other cluster commands, such as obd cluster display perf.

Note

The obd pref command for deploying components in the maximum specification was introduced in V3.4.0 of OceanBase Database. In V4.0.0 and later, the command is updated to obd perf.

obd perf [-c/--components]

The following table describes the options.

Option
Required
Data type
Default value
Description
-c/--components No string oceanbase-ce,obproxy-ce,obagent,prometheus,grafana The list of components to be deployed. Separate the components with commas (,). The deployed components are in the latest version in the obd image library. The supported components are: oceanbase-ce, oceanbase, oceanbase-standalone, obproxy-ce, obproxy, obagent, grafana, prometheus, and ob-configserver.
--server No string The current server The IP address of the server where the OceanBase cluster is to be deployed. If not specified, the default value is the current server.
--username No string The user who executes the command The username for SSH connection. If not specified, the default value is the user who executes the command. The maximum specification deployment will be performed in the home directory of the specified user.
--password No string Empty The login password of the connection user. If the connection user on the target server is configured with a password and no SSH password-free connection is configured between the user who executes the command and the connection user on the target server, you must specify the user password by using this option.
--port No int 22 The port for SSH connection.
--key-file No string Empty The path of the private key file for SSH connection. You must configure an absolute path for password-free SSH authentication based on the private key.

Examples

You can specify the deployment version and configuration by using options, for example:

Specify the deployment server

  • Specify the deployment server and connect by using a password

    obd perf -c oceanbase-ce --server=10.10.10.1 --username=admin --password=******
    
  • Specify the deployment server and connect by using a private key

    obd perf -c oceanbase-ce --server=10.10.10.1 --username=admin --key-file=/home/admin/.ssh/id_rsa
    

    Note

    If the private key file is in the default path (~/.ssh/id_ rsa), you can omit the --key-file option in the command.

Specify the component

  • Deploy OceanBase Database Community Edition and ODP

    obd perf -c oceanbase-ce,obproxy-ce
    
  • Deploy only obconfigserver

    obd perf -c ob-configserver
    

Specify the component version

  • Deploy the component in the specified version

    obd perf -c oceanbase-ce,obproxy-ce --oceanbase-ce.version=4.3.2.0
    
  • Deploy the component in the specified hash

    obd perf -c oceanbase-ce,obproxy-ce --oceanbase-ce.package_hash=f38723204d49057d3e062ffad778edc1552a7c114622bf2a86fea769fbd202ea
    

Customize the component configuration

This section uses the installation path and port of the component as an example. For more information about the related parameters in the configuration file, see the Parameters section in Configuration file description.

Notice

This command only supports specifying the first-level parameters under global by using options.

  • Specify the installation path of the component

    Deploy oceanbase-ce and obproxy-ce to the /data/perf directory and create the corresponding working directories for the components.

    obd perf -c oceanbase-ce,obproxy-ce --home_path=/data/perf
    
  • Specify the installation path of the specific component

    Deploy oceanbase-ce to the home directory and create the corresponding working directory for the component. Deploy obproxy-ce to the /data/perf/obproxy-ce directory.

    obd perf -c oceanbase-ce,obproxy-ce --obproxy-ce.home_path=/data/perf/
    
  • Specify the port of the component

    obd perf --oceanbase-ce.mysql_port=3881
    

Previous topic

Quickly deploy OCP
Last

Next topic

Cluster commands
Next
on this page
obd demo
Examples
obd perf
Examples