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.4.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
  • 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
  • Upgrade obdiag by using add-on files
  • Upgrade and uninstall obdiag
  • Telemetry Mode
  • FAQ
  • Release Notes
    • 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.4.0

ddl_disk_full

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

Scenarios
Supported environment variables
Examples
Results
References

Scenarios

You can use the obdiag rca run command to analyze the ddl_disk_full scenario. You can specify the write magnification of OceanBase Database and the source table size in the command to check whether the nodes have sufficient storage space.

OceanBase Database V4.0.0.0 and later are supported for this feature. When you use obdiag commands, you must configure cluster information in the config.yml file stored in the ~/.obdiag directory or by specifying --config options in the commands.

Notice

  • Internal data is updated in real time. Therefore, obdiag only supports the analysis of current data.

  • The write magnification in OceanBase Database V4.2.3.0 and later is 1.5, and that in earlier versions is 5.5.

Supported environment variables

Variable
Required?
Data type
Default value
Description
table_name Yes string "" The name of the table.
tenant_name Yes string 10 The name of the tenant.
action_type No string add_index The action type. The valid value is add_index.
index_name Yes string "" The name of the index.

Examples

Specify the scenario and the environment variables in the command.

obdiag rca run --scene=ddl_disk_full --input_parameters='{"tenant_name":" test1","table_name":" t555","action_type":" add_index","index_name":" k1"}'

Results

In the following command output, -4.32 TB and -4.31 TB indicate insufficient storage space on the corresponding nodes. You can increase the storage space of the nodes.

+----------------------------------------------------------------------------------------------------------+
|                                                  record                                                  |
+------+---------------------------------------------------------------------------------------------------+
| step | info                                                                                              |
+------+---------------------------------------------------------------------------------------------------+
|  1   | table_id is 510175                                                                                |
|  2   | tenant_id is 1002                                                                                 |
|  3   | on xxx.xxx.xxx.xxx:xxxx tablet_size: 4545356170733 as 4.13 TB                                     |
|  4   | on xxx.xxx.xxx.xxx:xxxx tablet_size: 4541074892527 as 4.13 TB                                     |
|  5   | estimated_size is [{'svr_ip': 'xxx.xxx.xxx.xxx', 'svr_port': xxxx, 'estimated_data_size':         |
|      | Decimal('4545356170733')}, {'svr_ip': 'xxx.xxx.xxx.xxx', 'svr_port': xxxx, 'estimated_data_size': |
|      | Decimal('4541074892527')}]                                                                        |
|  6   | index_name is idx_user_tx                                                                         |
|  7   | action_type is add_index                                                                          |
|  8   | index_table_id is 512088                                                                          |
|  9   | main_table_sum_of_data_length is 336                                                              |
|  10  | index_table_sum_of_data_length is 80                                                              |
|  11  | estimated_index_size without magnification 1082227659698B as 1007.90 GB from:                     |
|      | index_table_sum_of_data_length(80)/main_table_sum_of_data_length(336) *                           |
|      | estimated_data_size(4545356170733)                                                                |
|  12  | magnification is 5.5                                                                              |
|  13  | estimated_index_size with magnification is 5952252128339B as 5.41 TB                              |
|  14  | On target_server_ip is xxx.xxx.xxx.xxx, target_server_port is xxxx, estimiated_index_size is      |
|      | 5952252128339B as 5.41 TB                                                                         |
|  15  | estimated_index_size without magnification 1081208307744B as 1006.95 GB from:                     |
|      | index_table_sum_of_data_length(80)/main_table_sum_of_data_length(336) *                           |
|      | estimated_data_size(4541074892527)                                                                |
|  16  | magnification is 5.5                                                                              |
|  17  | estimated_index_size with magnification is 5946645692592B as 5.41 TB                              |
|  18  | On target_server_ip is xxx.xxx.xxx.xxx, target_server_port is xxxx, estimiated_index_size is      |
|      | 5946645692592B as 5.41 TB                                                                         |
|  19  | On target_serveris xxx.xxx.xxx.xxx:xxxx                                                           |
|  20  | target_server_estimated_size is 5952252128339B as 5.41 TB                                         |
|  21  | target_server_total_size is 3221225472000B as 2.93 TB                                             |
|  22  | target_server_used_size is 1696442875904B as 1.54 TB                                              |
|  23  | data_disk_usage_limit_percentage is 90                                                            |
|  24  | available_disk_space is 1202660048896B as 1.09 TB                                                 |
|  25  | available_disk_space - target_server_estimated_size is -4749592079443B as -4.32 TB                |
|  26  | On target_serveris xxx.xxx.xxx.xxx:xxxx                                                           |
|  27  | target_server_estimated_size is 5946645692592B as 5.41 TB                                         |
|  28  | target_server_total_size is 3221225472000B as 2.93 TB                                             |
|  29  | target_server_used_size is 1695073435648B as 1.54 TB                                              |
|  30  | data_disk_usage_limit_percentage is 90                                                            |
|  31  | available_disk_space is 1204029489152B as 1.10 TB                                                 |
|  32  | available_disk_space - target_server_estimated_size is -4742616203440B as -4.31 TB                |
+------+---------------------------------------------------------------------------------------------------+

References

For more information, see OceanBase Database Diagnostics and Turning (11) - ddl_disk_full Error.

Previous topic

lock_conflict
Last

Next topic

clog_disk_full
Next
on this page
Scenarios
Supported environment variables
Examples
Results
References