OceanBase logo
  • Products
    OceanBase database

    Products

    High-quality database products to meet full lifecycle enterprise data management needs.

    OceanBase Dedicated
    A fully-managed cloud DBaaS for mission-critical workloads at any scale, effortlessly handles your most demanding workloads.
    OceanBase Database
    The ideal solution for running OceanBase on-premises or in your private and hybrid clouds, allowing you to manage the entire OceanBase lifecycle seamlessly.
  • Solutions
    OceanBase database

    Solutions

    Enterprise data management solutions for all scenarios

    View All
    Multi-Scenario General OLTP
    The next-generation native distributed architecture provides users with high scalability with low costs.
    Real-time Analytics
    Use one set of data for both OLTP and OLAP tasks, realizing real-time analytics while saving ETL process.
    Database Consolidation
    The distributed multi-tenant architecture realizes resource pooling while ensuring isolation and availability.
    Multi-cloud Architecture
    Support multi-cloud, cross-cloud, or hybrid cloud deployment architecture.
    Cold Data Archiving
    The intelligent archive database solution helps users quickly archive cold data with reduced costs.
    Database Scaling
    Real-time high concurrency, multi-level elastic scaling with minimum cost implementation for massive online promotions.
    Database Active Geo-redundancy
    High availability architecture to support the core business scenarios with fast recovery, and zero data loss.
  • Customers
    OceanBase database

    Customers

    Check our successful cases to inspire your business

    View All
    Fintech
    GCash
    DANA
    Alipay
    Easypaisa
    Digital Economy
    Haidilao
    POP MART
    Kwai
    Ctrip
    Enterprise
    ICBC
    China Mobile Jiangsu
    Sinopec
  • Resources
    OceanBase database

    Resources

    Various types of resources about OceanBase and the database industry

    White Paper
    Find white papers about OceanBase and the distributed database technology.
    Blog
    Find the product features, best practices, customer cases and latest distributed database insights from the experts in OceanBase Blog.
    Training and Certification
    Learn about OceanBase's core technologies and distinctive features, get your skill certificate.
    GitHub
    View the source code of OceanBase, participate in co building open source projects.
  • Docs
    OceanBase database

    Docs

    Rich content to meet the content demands of using products and solving product usage problems

    View All
    Products
    OceanBase DatabaseOceanBase Cloud
    OceanBase DatabaseOceanBase Database
    Tools
    Connectors and Middleware
    Quick Start
    OceanBase Cloud
    OceanBase Database
    Architecture Overview
    Explore the architecture and technology of distributed database
OceanBase logo
编组
icon

OceanBase Deployer

V2.5.0Community Edition
 
箭头

  • What is OBD
  • Quick Start
    • Install and configure OBD
    • Quickly start OceanBase Database
    • Deploy an OceanBase cluster on the GUI
  • OBD Command
    • Quick deployment command
    • Cluster commands
    • Mirror and repository commands
    • Testing commands
    • Tool commands
    • obdiag commands
    • Telemetry commands
  • User Guide
    • Configuration files
    • Deploy through GUI
      • GUI operation overview
      • Deploy OCP through the GUI
    • Deploy through CLI
      • Deploy OceanBase Database on a single OBServer node
      • Deploy OCP Express by using commands
      • Deploy and use Config Server
      • Deploy OBLogProxy by using the CLI
      • Use OCP to take over a cluster deployed by OBD
      • Add GUI-based monitoring for an existing cluster
      • Upgrade OCP Express
      • Upgrade OceanBase Database
      • Physical Standby Database
        • Deploy primary and standby tenants by using OBD
        • Switch the roles of tenants and decouple a standby tenant from the primary tenant
      • Scale out a cluster and change cluster components
  • FAQ
    • FAQ
    • How do I upgrade an OBProxy to obproxy-ce 3.2.3?
  • Mode configuration rules
  • Error codes
  • Release Notes
    • Version rules
    • V2.5
      • OceanBase Deployer V2.5.0
    • V2.4
      • OceanBase Deployer V2.4.0
    • V2.3
      • OceanBase Deployer V2.3.1
      • OceanBase Deployer V2.3.0
    • V2.2
      • OceanBase Deployer V2.2.0
    • V2.1
      • OceanBase Deployer V2.1.1
      • OceanBase Deployer V2.1.0
    • V2.0
      • OceanBase Deployer V2.0.1
      • OceanBase Deployer 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

Download PDF

What is OBD Install and configure OBD Quickly start OceanBase Database Deploy an OceanBase cluster on the GUI Quick deployment command Cluster commands Mirror and repository commands Testing commands Tool commands obdiag commands Telemetry commands Configuration files GUI operation overview Deploy OCP through the GUI Deploy OceanBase Database on a single OBServer node Deploy OCP Express by using commands Deploy and use Config Server Deploy OBLogProxy by using the CLI Use OCP to take over a cluster deployed by OBD Add GUI-based monitoring for an existing cluster Upgrade OCP Express Upgrade OceanBase Database Scale out a cluster and change cluster components FAQ How do I upgrade an OBProxy to obproxy-ce 3.2.3? Mode configuration rules Error codes Version rules OceanBase Deployer V2.5.0 OceanBase Deployer V2.4.0 OceanBase Deployer V2.3.1 OceanBase Deployer V2.3.0 OceanBase Deployer V2.2.0 OceanBase Deployer V2.1.1 OceanBase Deployer V2.1.0 OceanBase Deployer V2.0.1 OceanBase Deployer V2.0.0 OceanBase Deployer V1.6.2 OceanBase Deployer V1.6.1 OceanBase Deployer V1.6.0 OceanBase Deployer V1.5.0 OceanBase Deployer V1.4.0 OceanBase Deployer V1.3.3 OceanBase Deployer V1.3.2 OceanBase Deployer V1.3.0 OceanBase Deployer V1.2.1 OceanBase Deployer V1.2.0
OceanBase

Company

About OceanBaseContact Us

Product

OceanBase DedicatedOceanBase DatabaseQuick StartDownloadPricing

Resources

DocsBlogWhite PaperTrust Center

Follow us

linkedinLinkedIntwitterTwittergithubGitHubStack OverflowStack OverflowslackSlack

© OceanBase 2024. All rights reserved | Cloud Service Agreement | Privacy Policy | Legal | Security

Document Feedback
  1. Documentation Center
  2. OceanBase Deployer
  3. V2.5.0
iconOceanBase Deployer
V 2.5.0Community Edition
  • V3.1.0 Community Edition
  • V3.0.0 Community Edition
  • V2.10.1 Community Edition
  • V2.10.0 Community Edition
  • V2.9.0 Community Edition
  • V2.8.0 Community Edition
  • V2.7.0 Community Edition
  • V2.6.0 Community Edition
  • V2.5.0 Community Edition
  • V2.4.0 Community Edition
  • V2.3.1 Community Edition
  • V2.3.0 Community Edition
  • V2.2.0 Community Edition
  • V2.1.0 Community Edition
  • V2.0.0 Community Edition
  • V1.6.1 Community Edition

Error codes

Last Updated:  Updated
share
What is on this page
General errors
OBD-1000: Configuration conflict x.x.x.x: xxx port is used for x.x.x.x
OBD-1001: x.x.x.x:xxx port is already used
OBD-1002: Fail to init x.x.x.x path
OBD-1003: fail to clean x.x.x.x:xxx
OBD-1004: Configuration conflict x.x.x.x: xxx is used for x.x.x.x
OBD-1005: Some of the servers in the cluster have been stopped
OBD-1006: Failed to connect to xxx
OBD-1007: (x.x.x.x) xxx must not be less than xxx (Current value: xxx)
OBD-1008: (x.x.x.x) failed to get fs.aio-max-nr and fs.aio-nr
OBD-1009: x.x.x.x xxx need config: xxx
OBD-1010: x.x.x.x No such net interface: xxx
OBD-1011: (x.x.x.x) Insufficient AIO remaining (Avail: xxx, Need: xxx), The recommended value of fs.aio-max-nr is 1048576
OBD-1012: xxx
OBD-1013: xxx@x.x.x.x connect failed: xxx
OBD-1015: Unable to confirm the primary-standby relationship, rerun with "--ignore-standby" option if you want to proceed despite the risks
OBD-1016: xx.xx.xx.xx failed to get kernel parameter using command "sysctl -a"
OBD-1017: xx.xx.xx.xx [kernel] xxx must be xxx
OBD-1018: could not change xxx
OBD-1019: component xxx already in cluster
OBD-1020: Update config for component xxx failed
OBD-1021: Component xxx is not in cluster
OBD-1022: Component xxx still depends by xxx, could not remove
OBD-1023: Failed to merge config: xxx
OBD-1024: The cluster will have no remaining components
OceanBase deployment errors
OBD-2000: x.x.x.x not enough memory
OBD-2001: server can not migrate in
OBD-2002: failed to start x.x.x.x observer
OBD-2003: not enough disk space for clog. Use redo_dir to set other disk for clog, or reduce the value of datafile_size
OBD-2004: Invalid: xxx is not a single server configuration item
OBD-2005: Failed to register cluster. xxx may have been registered in xxx
OBD-2006: x.x.x.x has more than one network interface. Please set devname for x.x.x.x
OBD-2007: x.x.x.x xxx fail to ping x.x.x.x
OBD-2008: Cluster clocks are out of sync
OBD-2009: x.x.x.x: when production_mode is True, xxx can not be less then xxx
OBD-2010: x.x.x.x: system_memory too large. system_memory must be less than memory_limit/memory_limit_percentage
OBD-2011: x.x.x.x: fail to get memory info.\nPlease configure 'memory_limit' manually in configuration file
Test-related errors
OBD-3000: parse cmd failed
OBD-3001: xxx.sql not found
OBD-3002: Failed to load data
OBD-3003: Failed to run TPC-C benchmark
OBAgent-related errors
OBD-4000: Fail to reload x.x.x.x
OBD-4001: Fail to send config file to x.x.x.x
ODP-related errors
OBD-4100: x.x.x.x need config "rs_list" or "obproxy_config_server_url"
OBD-4101: failed to start x.x.x.x obproxy: xxx
Grafana-related errors
OBD-4200: x.x.x.x grafana admin password should not be 'admin'
OBD-4201: x.x.x.x grafana admin password length should not be less than 5
OCP Express-related errors
OBD-4300: x.x.x.x: failed to query java version, you may not have java installed
OBD-4301: x.x.x.x: ocp-express need java with version xxx
OBD-4302: x.x.x.x not enough memory. (Free: xxx, Need: xxx)
OBD-4303: x.x.x.x xxx not enough disk space. (Avail: xxx, Need: xxx)
OBD-4304: OCP express xxx needs to use xxx with version xxx or above
OBD-4305: There is not enough xxx for ocp meta tenant
OBD-4306: xxx ocp-express admin_passwd invalid
OCP-related errors
OBD-4350: The Server have running task
OBD-4351: The Server have gone
OBD-4352: Metadb version not fewer than V2.2.50
OBD-4353: {server}: Excessive deviation between machine time and ob time
OBD-4354: {user}@{server}: Not exist
OBD-4355: {user}@{ip}: user xxx not in sudoers or sudoers file not exist
OBD-4356: failed to connect meta db
OBD-4357: database in jdbc_url is not exist
OBD-4358: unmatched jdbc url, skip meta db connection check
OBD-4359: {server}: ocp-server need java with version xxx and update release must greater than 161
OBD-4360: {server}: clockdiff not exists. Please install clockdiff manually
OBD-4361: tenant(xxx) already exist
OBD-4362: {server}:{path} access failed for current user, {server}:{cur_path} access succeed, please run chmod -R 755 {cur_path}
Config Server-related errors
OBD-4401: Failed to start x.x.x.x ob-configserver
OBD-4402: x.x.x.x ob-configserver config error
OBD-4403: ob-configserver connect to sqlite failed: x.x.x.x: /xxx/xxx/xxx: permission denied
OBD-4404: ob-configserver connect to mysql failed: xxx: failed url to connect to database: xxx
OBLogProxy errors
OBD-4501: OBLogProxy xxx needs to use xxx with version xxx or above
SQL-related errors
OBD-5000: sql execute failed
obdiag-related errors
OBD-6000: Failed to executable obdiag command, you may not have obdiag installed
OBD-6001: obdiag must contain depend components xxxx
OBD-6002: obdiag options xxx format error, please check the value : xxx
OBD-6003: Failed to execute obdiag function xxx
Unexpected errors
OBD-9999: Unexpected exception: need to be posted on "https://ask.oceanbase.com", and we will help you resolve them

folded

share
Preview
What is on this page
General errors
OBD-1000: Configuration conflict x.x.x.x: xxx port is used for x.x.x.x
OBD-1001: x.x.x.x:xxx port is already used
OBD-1002: Fail to init x.x.x.x path
OBD-1003: fail to clean x.x.x.x:xxx
OBD-1004: Configuration conflict x.x.x.x: xxx is used for x.x.x.x
OBD-1005: Some of the servers in the cluster have been stopped
OBD-1006: Failed to connect to xxx
OBD-1007: (x.x.x.x) xxx must not be less than xxx (Current value: xxx)
OBD-1008: (x.x.x.x) failed to get fs.aio-max-nr and fs.aio-nr
OBD-1009: x.x.x.x xxx need config: xxx
OBD-1010: x.x.x.x No such net interface: xxx
OBD-1011: (x.x.x.x) Insufficient AIO remaining (Avail: xxx, Need: xxx), The recommended value of fs.aio-max-nr is 1048576
OBD-1012: xxx
OBD-1013: xxx@x.x.x.x connect failed: xxx
OBD-1015: Unable to confirm the primary-standby relationship, rerun with "--ignore-standby" option if you want to proceed despite the risks
OBD-1016: xx.xx.xx.xx failed to get kernel parameter using command "sysctl -a"
OBD-1017: xx.xx.xx.xx [kernel] xxx must be xxx
OBD-1018: could not change xxx
OBD-1019: component xxx already in cluster
OBD-1020: Update config for component xxx failed
OBD-1021: Component xxx is not in cluster
OBD-1022: Component xxx still depends by xxx, could not remove
OBD-1023: Failed to merge config: xxx
OBD-1024: The cluster will have no remaining components
OceanBase deployment errors
OBD-2000: x.x.x.x not enough memory
OBD-2001: server can not migrate in
OBD-2002: failed to start x.x.x.x observer
OBD-2003: not enough disk space for clog. Use redo_dir to set other disk for clog, or reduce the value of datafile_size
OBD-2004: Invalid: xxx is not a single server configuration item
OBD-2005: Failed to register cluster. xxx may have been registered in xxx
OBD-2006: x.x.x.x has more than one network interface. Please set devname for x.x.x.x
OBD-2007: x.x.x.x xxx fail to ping x.x.x.x
OBD-2008: Cluster clocks are out of sync
OBD-2009: x.x.x.x: when production_mode is True, xxx can not be less then xxx
OBD-2010: x.x.x.x: system_memory too large. system_memory must be less than memory_limit/memory_limit_percentage
OBD-2011: x.x.x.x: fail to get memory info.\nPlease configure 'memory_limit' manually in configuration file
Test-related errors
OBD-3000: parse cmd failed
OBD-3001: xxx.sql not found
OBD-3002: Failed to load data
OBD-3003: Failed to run TPC-C benchmark
OBAgent-related errors
OBD-4000: Fail to reload x.x.x.x
OBD-4001: Fail to send config file to x.x.x.x
ODP-related errors
OBD-4100: x.x.x.x need config "rs_list" or "obproxy_config_server_url"
OBD-4101: failed to start x.x.x.x obproxy: xxx
Grafana-related errors
OBD-4200: x.x.x.x grafana admin password should not be 'admin'
OBD-4201: x.x.x.x grafana admin password length should not be less than 5
OCP Express-related errors
OBD-4300: x.x.x.x: failed to query java version, you may not have java installed
OBD-4301: x.x.x.x: ocp-express need java with version xxx
OBD-4302: x.x.x.x not enough memory. (Free: xxx, Need: xxx)
OBD-4303: x.x.x.x xxx not enough disk space. (Avail: xxx, Need: xxx)
OBD-4304: OCP express xxx needs to use xxx with version xxx or above
OBD-4305: There is not enough xxx for ocp meta tenant
OBD-4306: xxx ocp-express admin_passwd invalid
OCP-related errors
OBD-4350: The Server have running task
OBD-4351: The Server have gone
OBD-4352: Metadb version not fewer than V2.2.50
OBD-4353: {server}: Excessive deviation between machine time and ob time
OBD-4354: {user}@{server}: Not exist
OBD-4355: {user}@{ip}: user xxx not in sudoers or sudoers file not exist
OBD-4356: failed to connect meta db
OBD-4357: database in jdbc_url is not exist
OBD-4358: unmatched jdbc url, skip meta db connection check
OBD-4359: {server}: ocp-server need java with version xxx and update release must greater than 161
OBD-4360: {server}: clockdiff not exists. Please install clockdiff manually
OBD-4361: tenant(xxx) already exist
OBD-4362: {server}:{path} access failed for current user, {server}:{cur_path} access succeed, please run chmod -R 755 {cur_path}
Config Server-related errors
OBD-4401: Failed to start x.x.x.x ob-configserver
OBD-4402: x.x.x.x ob-configserver config error
OBD-4403: ob-configserver connect to sqlite failed: x.x.x.x: /xxx/xxx/xxx: permission denied
OBD-4404: ob-configserver connect to mysql failed: xxx: failed url to connect to database: xxx
OBLogProxy errors
OBD-4501: OBLogProxy xxx needs to use xxx with version xxx or above
SQL-related errors
OBD-5000: sql execute failed
obdiag-related errors
OBD-6000: Failed to executable obdiag command, you may not have obdiag installed
OBD-6001: obdiag must contain depend components xxxx
OBD-6002: obdiag options xxx format error, please check the value : xxx
OBD-6003: Failed to execute obdiag function xxx
Unexpected errors
OBD-9999: Unexpected exception: need to be posted on "https://ask.oceanbase.com", and we will help you resolve them