obdiag V4.2.0

Version information

• Published: March 13, 2026
• Version number: V4.2.0

New version changes function points

Added new commands and scenarios

• [New] obdiag rca run adds a new SQL execution memory root cause analysis scenario (--scene=execute_memory_high), supports OceanBase database V4.0 and above, and can check the execution memory in __all_virtual_memory_info, GV$OB_SQL_WORKAREA_MEMORY_INFO, memory parameters and Top consumption SQL/modules to facilitate locating the issue of excessive execution memory. For detailed introduction, please refer to Root cause analysis scenario: SQL execution memory is too high.

• [New] obdiag check run pre-deployment environment verification (--cases=build_before) adds docker0 network interface check. When deploying OBProxy through OCP, if a docker0 interface exists, a prompt may be displayed showing the docker0 address instead of the actual physical host address to avoid deployment configuration errors. For detailed introduction, please refer to One-click cluster inspection.

Function enhancement

• [New] The obdiag gather perf command supports collecting perf performance data of the OBProxy process. When an OBProxy node exists in the configuration, the perf information of the OceanBase cluster and OBProxy can be collected together; the OBProxy node in the Docker/Kubernetes environment will be automatically skipped. For detailed introduction, please refer to Flame Diagram/Bianque Diagram Collection.

• [New] obdiag gather tabledump command appends CREATE TABLE DDL to the create_tables_{timestamp}.sql file in the output to facilitate direct execution of table creation statements; the output summary will include the SQL file path. For detailed introduction, please refer to Table related information collection.

• [Optimization] obdiag gather plan_monitor deduplicates the parsed table to avoid repeated processing when the same table is referenced multiple times, and improves the efficiency of schema reporting and statistical information collection; at the same time, it fixes the SQLTableExtractor comma connection and invalid reference filtering issues. For detailed introduction, please refer to SQL details collection.

• [Optimization] obdiag analyze memory optimizes the display style of memory analysis results, improves HTML template indentation and chart parameter readability. For detailed introduction, please refer to One-click diagnostic analysis of memory.

• [Optimization] Added column group Schema problem check in card merger root cause analysis scenario (obdiag rca run --scene=major_hold), supports detection of old __co_all records in __all_virtual_column_group_history in heterogeneous row and column conversion scenarios, and provides processing steps. For detailed introduction, please refer to Root Cause Analysis Scenario: Card Merger.

• [Optimization] DDL disk full root cause analysis scenario (obdiag rca run --scene=ddl_disk_full) supports multiple indexes in a single DDL, the index_name parameter supports comma separation (such as index_name=idx1,idx2,idx3), and the estimated size of each index is accumulated by node. For detailed introduction, please refer to Root Cause Analysis Scenario: DDL Disk Full.

• [Optimization] obdiag gather plan_monitor adds verification when the specified database does not exist to avoid invalid connections; the error message is clearer.

• [Change] The checking framework introduces SSH connection management: added check.ssh_manager configuration (max_connections_per_node, idle_timeout) in inner_config.yml, implements SSHConnectionManager connection pool, multi-task shares each node SSH connection, improves efficiency and resource management; inspection task version check logic update, upper_trans_version requires OceanBase database V4.0.0.0 and above. For detailed introduction, please refer to obdiag configuration and One-click cluster inspection.

Installation and Build

• [Note] V4.2.0 continues to use pyproject.toml to manage dependencies and builds. For details, see obdiag installation.