Applicable scenarios
This article is suitable for root cause analysis of transaction execution timeout errors, and is based on the analysis of OceanBase database internal table data and logs.
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.
Can import environment variables
Variable name |
Is it required |
Data type |
Default value |
Description |
|---|---|---|---|---|
| tenant_id | yes | string | "" | tenant ID |
| trace_id | yes | string | "" | trace_id |
| err_type | Yes | string | "" | Error type, optionally statement is timeout or transaction is timeout |
Usage example
The execution example of configuring the analysis scenario and specifying the tenant, trace_id and other related information is as follows:
obdiag rca run --scene=transaction_execute_timeout --env tenant_id=1002 --env trace_id=YXXXXXXXXXX --env err_type=statement is timeout