OceanBase Diagnostic Tool

V3.0.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
  - observer.topsql
  - 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
- oms_full_trans
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 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

OceanBase, A Highly Scalable Database for Transactional, Analytical, and AI Workloads.

Company

About OceanBase Contact Us Partner

Product

OceanBase Cloud OceanBase Enterprise Quick Start Download Pricing

Resources

Docs Blog White Paper Trust Center

Document Feedback

oms_full_trans

Last Updated：2025-03-21 08:45:14 Updated

Scenarios

You can use the obdiag rca run command to analyze the oms_full_trans scenario.

Supported environment variables

Variable	Required	Data type	Default value	Description
component_id	Yes	string	""	The ID of the full migration task, in the format of `{IP address}_connector_xxxxxx`.

Examples

Specify the scenario and task ID in the command.

obdiag rca run --scene=oms_full_trans --env component_id=xxxxxx

Previous topic

transaction_wait_timeout

Last

Next topic

Overview