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 Diagnostic Tool

V2.6.0
  • Overview
  • Install obdiag
  • Configure obdiag
  • One-click Cluster Inspection
    • Use obdiag to inspect an OceanBase cluster
    • Inspection metrics
  • One-click Information Collection
    • One-click General Information Collection
      • obdiag gather log
      • obdiag gather sysstat
      • obdiag gather plan_monitor
      • obdiag gather stack
      • obdiag gather perf
      • obdiag gather ash
      • obdiag gather tabledump
      • obdiag gather parameter
      • obdiag gather variable
      • obdiag gather clog/obdiag gather slog
      • obdiag gather obproxy_log
      • obdiag gather all
    • One-click Scenario-based Information Collection
      • Overview
      • observer.base
      • observer.backup
      • observer.backup_clean
      • observer.clog_disk_full
      • observer.cluster_down
      • observer.compaction
      • observer.cpu_high
      • observer.delay_of_primary_and_backup
      • observer.io
      • observer.log_archive
      • observer.long_transaction
      • observer.memory
      • observer.perf_sql
      • observer.px_collect_log
      • observer.recovery
      • observer.restart
      • observer.rootservice_switch
      • observer.suspend_transaction
      • observer.unit_data_imbalance
      • observer.perf_sql
      • other.application_error
      • obproxy.restart
      • observer.unknown
  • One-click Diagnostic Analysis
    • obdiag analyze log
    • obdiag analyze flt_trace
    • obdiag analyze parameter default
    • obdiag analyze parameter diff
    • obdiag analyze variable diff
    • obdiag analyze index_space
    • obdiag analyze memory
    • obdiag analyze queue
  • One-click Root Cause Analysis
    • Use obdiag for root cause analysis
    • disconnection
    • major_hold
    • lock_conflict
    • ddl_disk_full
    • clog_disk_full
    • log_error
    • ddl_failure
    • index_ddl_error
    • transaction_disconnection
    • transaction_execute_timeout
    • transaction_not_ending
    • transaction_other_error
    • transaction_rollback
    • transaction_wait_timeout
  • One-click Cluster Display
    • Overview
    • Basic information of a cluster
    • Information about nodes in a cluster
    • Information about units in a cluster
    • Information about zones in a cluster
    • RootService information of a cluster
    • Information about tenants in a cluster
    • Information about events in a cluster
    • Information about locks in a cluster
    • Information about top SQL statements in a cluster
    • Information about slow SQL statements in a cluster
    • Information about tables in a cluster
    • Information about the process list in a cluster
    • Information about the execution plan of an SQL statement
    • Disk usage of a database
    • Disk usage of the specified table in a database
  • Upgrade obdiag by using add-on files
  • Upgrade and uninstall obdiag
  • Telemetry Mode
  • FAQ
  • Release Notes
    • obdiag V2.6.0
    • obdiag V2.5.0
    • obdiag V2.4.0
    • obdiag V2.3.0
    • obdiag V2.2.0
    • obdiag V2.1.0
    • obdiag V2.0.0
    • obdiag V1.6.2
    • obdiag V1.6.1
    • obdiag V1.6.0
    • obdiag V1.5.2
    • obdiag V1.5.1
    • obdiag V1.5.0
    • obdiag V1.4.0
    • obdiag V1.3.0

Download PDF

Document Feedback
  1. Documentation Center
  2. OceanBase Diagnostic Tool
  3. V2.6.0

Install obdiag

Last Updated:2026-09-04 08:22:11

Environment requirements
Prerequisites
Procedure
Method 1: Use obdiag independently
Method 2: Use obdiag in combination with obd

This topic describes how to install OceanBase Diagnostic Tool (obdiag).

Environment requirements

The server where obdiag is to be installed runs on Linux.

Prerequisites

To collect fault information, inspect a cluster, perform root cause analysis, analyze logs online, and perform online end-to-end diagnostics, network access must be available between the server where obdiag is to be installed and the hosts of the target OceanBase cluster whose information is to be collected.

Procedure

You can use obdiag independently or in combination with OceanBase Deployer (obd).

Method 1: Use obdiag independently

If the cluster to be diagnosed is not deployed by using obd, you can run the following commands to install and deploy obdiag:

  • Online deployment (when Internet access is available)

    sudo yum install -y yum-utils
    sudo yum-config-manager --add-repo https://mirrors.aliyun.com/oceanbase/OceanBase.repo
    sudo yum install -y oceanbase-diagnostic-tool
    sh /usr/local/oceanbase-diagnostic-tool/init.sh
    

    Note

    The online deployment method is supported on CentOS 7 and 8. If you use CentOS 9, perform the following operations for offline deployment.

  • Offline deployment (when Internet access is unavailable): Download the obdiag package from OceanBase Download Center.

    yum localinstall -y oceanbase-diagnostic-tool*.rpm
    sh /usr/local/oceanbase-diagnostic-tool/init.sh
    
  • Deployment on a Debian-based system, such as Ubuntu: Download the obdiag package from OceanBase Download Center.

    apt-get update
    apt-get install alien -y
    alien --scripts --to-deb  oceanbase-diagnostic-tool*.rpm # Convert the RPM package to a DEB package.
    dpkg -i oceanbase-diagnostic-tool*.deb
    sh /usr/local/oceanbase-diagnostic-tool/init.sh
    

    Note

    Package conversion is supported in Alien 8.95.0 and earlier. We recommend that you use the native image of Debian 10.

Method 2: Use obdiag in combination with obd

If the cluster to be diagnosed is deployed by using obd, we recommend that you upgrade obd to V2.5.0 or later. Then, you can directly run obdiag commands on obd without the need to configure the ~/.obdiag/config.yml file. For more information about the commands, see obdiag commands.

  • Online deployment (when Internet access is available)

    # Enable obd to pull remote images
    obd mirror enable remote
    # Deploy obdiag by using obd
    obd obdiag deploy
    
  • Offline deployment (when Internet access is unavailable)

    Download the obdiag package from OceanBase Download Center.

    # Copy the offline obdiag package to the image repository of obd
    obd mirror clone oceanbase-diagnostic-tool-xxxxxxxx.rpm
    # Deploy obdiag by using obd
    obd obdiag deploy
    

Previous topic

Overview
Last

Next topic

Configure obdiag
Next
on this page
Environment requirements
Prerequisites
Procedure
Method 1: Use obdiag independently
Method 2: Use obdiag in combination with obd