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 Developer Center

V4.5.0
  • Topics Overview
  • Overview
    • What is ODC?
    • Features
    • Architecture
    • Limitations
    • ODC console
  • Quick Start
    • Client ODC
      • Overview
      • Install Client ODC
      • Use Client ODC
    • Web ODC
      • Overview
      • Deploy Web ODC
      • Use Web ODC
  • Data Source Management
    • Create a data source
    • Data sources and project collaboration
    • Database O&M
      • Session management
      • Global variable management
      • Recycle bin management
  • SQL Development
    • Edit and execute SQL statements
    • Perform PL compilation and debugging
    • Use the command-line window
    • Edit and export the result set
    • Execution Analysis
    • Generate test data
    • System settings
    • Intelligent SQL development
    • Common features
    • Database objects
      • Table objects
        • Overview
        • Create a table
      • View objects
        • Overview
        • Create a view
        • Manage views
      • Materialized view objects
        • Overview
        • Create a materialized view
        • Manage materialized views
      • Function objects
        • Overview
        • Create a function
        • Manage functions
      • Stored procedure objects
        • Overview
        • Create a stored procedure
        • Manage stored procedures
      • Sequence objects
        • Overview
        • Create a sequence
        • Manage sequences
      • Package objects
        • Overview
        • Create a program package
        • Manage program packages
      • Trigger objects
        • Overview
        • Create a trigger
        • Manage triggers
      • Type objects
        • Overview
        • Create a type
        • Manage types
      • Synonym objects
        • Overview
        • Create a synonym
        • Manage synonyms
      • External resource objects
        • External resources
        • Create an external resource
        • Manage external resources
  • Database Change Risk Management
    • Project collaborative management
      • Project management
      • Manage databases
      • Manage logical databases
      • Add object storage files
      • Manage project members
      • Desensitize data
      • Notification management
        • Overview
        • View notification records
        • Manage notification channels
          • Create a notification channel
          • View, edit, and delete a notification channel
          • Configure a custom channel
        • Manage notification rules
    • Manage user permissions
      • Users and roles
      • Automatic authorization
      • Apply for project permissions
      • Apply for database permissions
      • Apply table/view permissions
    • Security standards
      • Environment configuration
        • SQL check specifications
        • SQL window specification
      • Risk Management
        • Overview
        • Manage risk identification rules
        • Manage approval processes
      • Desensitization algorithms
      • Operation audit
  • Ticket Management
    • Import schemas and data
    • Export schemas and data
    • Database change management
    • Manage changes to logical databases
    • Batch database change management
    • Online schema changes
    • Synchronize shadow tables
    • Schema comparison
  • Data Lifecycle Management
    • Data archiving
    • Data cleanup
    • Manage partitioning plans
      • Manage partitioning plans
      • Set partitioning strategies
      • Examples of partitioning strategies
    • SQL Plan
  • System Integration
    • Login integration
    • Approval integration
    • SQL approval integration
    • Bastion host integration
    • Integrate with LLMs
  • Deployment Guide
    • Deployment overview
    • Preparations before deployment
    • Deploy ODC in single-node mode
    • Deploy ODC in high-availability mode
    • Deployment verification
  • Upgrade Guide
    • Upgrade Overview
    • Preparations for upgrade
    • Update single-node ODC
    • Update high-avaliability ODC
    • Upgrade verification
    • Rollback after upgrade failed
  • Best Practices
    • Tips for SQL development
    • Explore ODC team workspaces
    • Understanding real-time SQL diagnostics for OceanBase AP
    • OceanBase historical database solutions
    • ODC SQL check for automatic identification of high-risk operations
    • Integration with ODC enterprise-level account system
    • Manage and modify sharded databases and tables via ODC
    • Data masking and control practices
    • Enterprise-level control and collaboration: Safeguard every database change
  • Troubleshooting
    • ODC troubleshooting process
    • Collect message
      • View the runtime environment and version information
      • View web ODC logs
      • View client ODC logs
      • View end-to-end ODC-related logs
      • View ODC MetaDB data
      • Query the index status in OceanBase Database V4.x
      • Query the index status in OceanBase Database V1.4.x to V3.2.x
      • Collect JVM runtime information
      • Use tcpdump to capture packets
    • FAQ
      • Installation of client ODC
      • Web ODC deployment and startup
      • Connection Information
      • Command-line window
      • DDL statement display
  • Release Notes
    • V4.5
      • ODC V4.5.0
    • V4.4
      • ODC V4.4.0
      • ODC V4.4.1
      • ODC V4.4.2
      • ODC V4.4.3
    • V4.3
      • ODC V4.3.4
      • ODC V4.3.3
      • ODC V4.3.2
      • ODC V4.3.1
      • ODC V4.3.0
    • V4.2
      • ODC V4.2.4
      • ODC V4.2.3
      • ODC V4.2.2
      • ODC V4.2.1
      • ODC V4.2.0
    • V4.1
      • ODC V4.1.3
      • ODC V4.1.2
      • ODC V4.1.1
      • ODC V4.1.0
    • V4.0
      • ODC V4.0.2
      • ODC V4.0.0
    • V3.4
      • ODC V3.4.0
    • V3.3
      • ODC V3.3.3
      • ODC V3.3.2
      • ODC V3.3.1
      • ODC V3.3.0
    • V3.2
      • ODC V3.2.3
      • ODC V3.2.2
      • ODC V3.2.1
      • ODC V3.2.0

Download PDF

Document Feedback
  1. Documentation Center
  2. OceanBase Developer Center
  3. V4.5.0

Deploy Web ODC

Last Updated:2026-10-09 03:23:33

Deploy single-node Web ODC
Log in to Web ODC
References

This topic describes how to deploy and log in to Web ODC.

Note

For more information about the environment requirements, see Limitations.

Deploy single-node Web ODC

  1. Apply for a tenant in MySQL compatible mode of OceanBase Database. Allocate 2 CPU cores and 8 GB of memory to the tenant. You can name the tenant as you like. Example: The cluster name of the tenant is odc_cluster and the tenant name is odc_tenant.

  2. Create a database and a user under the tenant as the ODC metabase. You can set the username, password, and metabase name as you like. Example: The metabase name is odc_metadb and both the database username and password are obodc.

  3. Record the name, username, password, tenant name, and cluster name of the metabase, which are required when you deploy ODC.

  4. Configure the deployment environment for the single-node Web ODC node based on the number of ODC users.

    Number of ODC users
    Server type
    Server quantity
    Minimum functional configuration
    Minimum performance configuration
    20 ODC Docker server 1 2 CPU cores and 4 GB of memory 4 CPU cores and 16 GB of memory
  5. For more information about how to install and run the Docker container, see Use bind mounts.

  6. Download the ODC image as needed to obtain the desired image architecture in the Maintenance Tools of the OceanBase Download Center.

    Notice

    • The images of ODC V4.2.0 and later versions have been published to Docker Hub. If your local device running ODC can access Docker Hub, you can directly start ODC Docker without downloading the image. For details, see Step 7 to load the image.
    • If Docker Hub cannot be accessed directly, you still need to download and load the image file.
  7. After obtaining the image file on the host, run the following statement in the command line tool to load the image:

    Syntax:

    gunzip -c obodc-{$version}.tar.gz | docker load
    

    Example:

    #!/usr/bin/env bash
    docker run -v /var/log/odc:/opt/odc/log   -v /var/data/odc:/opt/odc/data \
    -d -i --net host --cpu-period 100000 --cpu-quota 400000 --memory 8G --name "obodc" \
    -e "DATABASE_HOST=xxx.xx.xx.xx" \
    -e "DATABASE_PORT=60805" \
    -e "DATABASE_USERNAME=[username]@[tenant name]#[cluster name]" \
    -e "DATABASE_PASSWORD=******" \
    -e "DATABASE_NAME=odc_metadb" \
    -e "ODC_ADMIN_INITIAL_PASSWORD=******" \
    oceanbase/odc:4.2.2
    

    The following table describes the parameters in the preceding example.

    Parameter
    Description
    -v
    • Maps the /var/log/odc directory on the host to the /opt/odc/log directory in the ODC container. The /var/log/odc directory on the host must exist. If it does not exist, run the mkdir -p /var/log/odc command to create it.
    • Mounts the /var/data/odc directory on the host to the /opt/odc/data directory in the ODC container. The /var/data/odc directory on the host can be customized. If it does not exist, run the mkdir -p /var/data/odc command to create it.
    --net Specifies the network configuration of the container. If you set the value of this parameter to host, the container directly uses the host network. You can also use the --publish (-p) parameter to configure port mapping. However, in some environments, the container may fail to start due to DNS resolution errors in Docker. In this case, use the --net host method to start Docker.
    Default port number: 8989.
    --cpu-period --cpu-quota
    • ---cpu-period specifies the time interval for redistributing CPU resources to the container. Unit: microseconds.
    • ---cpu-quota specifies the maximum amount of time that can be allocated to the container in the specified period. Unit: microseconds.
    Together, these parameters specify the number of CPU cores available to the container. The value of cpu-quota divided by cpu-period indicates the number of CPU cores available to the container. For example, 400000/100000=4 indicates that the container can use up to 4 CPU cores.
    --memory Specifies the maximum memory available to the container.
    --name Specifies the container name.
    DATABASE_HOST The IP address of the metadata database.
    DATABASE_PORT The port number of the metadata database.
    Default port number: 8989.
    DATABASE_USERNAME The username of the metadata database. The username of OceanBase Database is in the db_user@tenant_name#cluster_name format.
    DATABASE_PASSWORD The password for connecting to the database.
    DATABASE_NAME The name of the metadata database.
    ODC_PROFILE_MODE Specifies the mode. The default value is alipay.
    ODC_ADMIN_INITIAL_PASSWORD Specifies the initial password of the ODC administrator account (admin).

    Notice

    • In a shell environment, if the string contains special characters such as ! or $, the variable value must be enclosed in single quotes. For example: DATABASE_PASSWORD='11111!'.
    • The ODC_ADMIN_INITIAL_PASSWORD parameter specifies the initial password of the ODC administrator account (admin). The initial password must meet the following conditions:
      • Contain at least 2 digits.
      • Contain at least 2 uppercase letters.
      • Contain at least 2 lowercase letters.
      • Contain at least 2 special characters, which can be . _ + @ # $ % .
      • Not contain spaces or other special characters, and the length must be 8 to 32.

Log in to Web ODC

  1. Open the browser, enter the endpoint of Web ODC, and press Enter.

  2. Enter the account and password to log in to Web ODC.

    Note

    You can also use SSO integration to automatically maintain account information. For more information, see Configure SSO.

    logon

  3. Select the target workspace.

  4. Log in to ODC and go to the connection management page. Click My in the lower-left corner of the navigation bar. The account name is displayed. Click Exit in the drop-down menu to return to the ODC logon page. You can log in to ODC with another account.

    3

References

  • Use Web ODC

Previous topic

Overview
Last

Next topic

Use Web ODC
Next
on this page
Deploy single-node Web ODC
Log in to Web ODC
References