Applicable scenarios
This article is applicable to the scenario where an index execution error is reported in the OceanBase database, and is analyzed based on the internal table data and logs of the OceanBase database.
Currently, OceanBase database V4.2.3.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.
Can import environment variables
Variable name |
Is it required |
Data type |
Default value |
Description |
|---|---|---|---|---|
| tenant_name | Yes | string | "" | Tenant name |
| table_name | yes | string | "" | table name |
| database_name | Yes | string | "" | Database name |
| index_name | Yes | string | "" | Index name |
Usage example
The execution example of configuring the analysis scenario and specifying tenants, tables and other related information is as follows:
obdiag rca run --scene=index_ddl_error --env tenant_name=cudb_test --env table_name=test1245 --env database_name=test --env index_name=idx_name