Meet OceanBase AI Database, the unified database for operational data, real-time analytics, and AI. Explore ->

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 Cloud

OceanBase Database

Tools Connectors and Middleware

QUICK START

OceanBase Cloud OceanBase 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

OceanBase Diagnostic Tool

V4.3.0

obdiag Overview
obdiag installation
obdiag configuration
One-click Cluster Inspection
- One-click cluster inspection
- Detailed explanation of cluster inspection indicators
One-click Information Gathering
- One-click routine information collection
  - OceanBase cluster log collection
  - Host information collection
  - SQL details collection
  - Stack information collection
  - Flame Picture/Bian Que Picture Collection
  - ASH report collection
  - Collect table-related information
  - Cluster parameter collection
  - Variable collection
  - clog/slog collection
  - DBMS_XPLAN information collection
  - Core file collection
  - AWR report collection
  - obproxy log collection
  - OMS log collection
  - Collect all information
- One-click scenario-based information collection
  - Overview
  - Collect basic cluster information
  - Collect backup problem information
  - Collect backup cleanup problem information
  - Collect clog disk full problem information
  - Collect cluster downtime problem information
  - Collect merge problem information
  - Collect CPU high problem information
  - Collect information on delay issues in primary and standby databases
  - Collect I/O problem information
  - Collect log archiving problem information
  - Collect long transaction problem information
  - Collect memory problem information
  - Collect SQL performance problem information
  - Collect PX error reporting information
  - Collect recovery problem information
  - Collect observer restart information without reason
  - Collect owner-cutting problem information
  - Collect information about hanging transaction issues
  - Collect copy imbalance problem information
  - Collect SQL error reporting information
  - Collect cluster TopSQL information
  - Collect application error information
  - Collect obproxy restart problem information for no reason
  - Collect ODP parameter information
  - Collect unspecified scenario problem information
One-click Diagnostic Analysis
- One-click diagnostic analysis log
- One-click full-link diagnostic log analysis
- Parameter analysis (compared with default values)
- Parameter analysis (parameter differences on different observers)
- Analyze variables
- Instructions for using index space analysis
- One-click diagnostic analysis of memory
- One-click diagnosis and analysis of queue backlog
One-click Root Cause Analysis
- One-click root cause analysis
- Root cause analysis scenario: disconnection
- Root cause analysis scenario: card merging major_hold
- Root cause analysis scenario: lock conflict lock_conflict
- Root cause analysis scenario: executing DDL and reporting disk full error ddl_disk_full
- Root cause analysis scenario: clog disk is full clog_disk_full
- Root cause analysis scenario: log error log_error
- Root cause analysis scenario: DDL failure ddl_failure
- Root cause analysis scenario: Troubleshooting index build execution error index_ddl_error
- Root cause analysis scenario: transaction disconnection scenario transaction_disconnection
- Root cause analysis scenario: transaction execution times out and error transaction_execute_timeout
- Root cause analysis scenario: transaction does not end and error transaction_not_ending is reported
- Root cause analysis scenario: transaction other errors transaction_other_error
- Root cause analysis scenario: transaction rollback error transaction_rollback
- Root cause analysis scenario: transaction wait timeout error transaction_wait_timeout
- Root cause analysis scenario: OMS full migration exception oms_full_trans
- Root cause analysis scenario: OMS obcdc component analysis oms_obcdc
- Root cause analysis scenario: suspended transaction suspend_transaction
- Root cause analysis scenario: Unit GC exception unit_gc
- Root cause analysis scenario: OceanBase cluster playback card
- Root cause analysis scenario: OceanBase cluster memory explosion
- Root cause analysis scenario: Abnormal deletion of OBServer node
- Root cause analysis scenario: GC troubleshooting gc_troubleshooting
- Root cause analysis scenario: Schema leak schema_leak
- Root cause analysis scenario: partition split scheduling error split_schedule_error
- Root cause analysis scenario: weak read problem troubleshooting weak_read_troubleshooting
- Root cause analysis scenario: SQL execution memory is too high execute_memory_high
One-click Cluster Insights
- Overview
- Cluster overview information insights
- Cluster node information insight
- Cluster unit information insight
- Cluster Zone Information Insights
- Cluster RS Information Insights
- Cluster tenant information insight
- Cluster event information insight
- Cluster lock information insight
- Cluster topsql information insight
- Cluster slowsql information insight
- Cluster table information insight
- Cluster processlist information insight
- SQL execution plan information insights
- Insights into database disk usage information
- Insight on the disk usage of the specified table in the database
- Insights into the full tenant information of the cluster
- Cluster node CPU usage information insights
- Internal table name fuzzy matching information insight
- Cluster leader information insight
- Information insights into locks held on a certain table
- Cluster long transaction information information insight
- Actual execution plan operator information insight
- Memory information insights for all tenants
- processlist Real-time session summary information insights
- Table/index storage method information insight
- Table NDV Information Insights
- Table index information insight
- Merge status display
- clog log volume/capacity statistics
Plug-in file upgrade
Update and uninstall
Telemetry Mode
FAQ
Tools
- Configuration file encryption
- AI Intelligent Diagnosis Assistant
- Disk IO performance detection
- Configure verification tool
Release Notes
- obdiag V4.2.0
- obdiag V4.1.0
- obdiag V4.0.0
- obdiag V3.7.2
- obdiag V3.7.1
- obdiag V3.7.0
- obdiag V3.6.0
- obdiag V3.5.0
- obdiag V3.4.0
- obdiag V3.3.0
- obdiag V3.2.0
- obdiag V3.1.0
- obdiag V3.0.0
- 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

Root cause analysis scenario: log error log_error

Last Updated：2026-06-30 15:09:40 Updated

Applicable scenarios

This article is applicable to the scenario where log stream errors are reported in OceanBase database, and is analyzed based on the internal table data and logs of OceanBase database.

Currently, OceanBase database V4.0.0.0 and later versions are supported. When using obdiag, you need to configure the cluster information in the ~/.obdiag/config.yml file according to your choice, or configure the cluster information through the --config option in the command.

Attention

Due to the timeliness of internal data, only current data is supported for analysis.
Currently, only the scenario where the log stream has no owner is supported.

Usage example

Configure the analysis scenario. The default execution example is as follows:

obdiag rca run --scene=log_error

Previous topic

Root cause analysis scenario: clog disk is full clog_disk_full

Last

Next topic

Root cause analysis scenario: DDL failure ddl_failure