Applicable scenarios
This article is suitable for root cause analysis of non-end transaction errors, based on 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 |
|---|---|---|---|---|
| phase | Yes | string | "" | The phase of the transaction, optional UNSUBMITTED, COMMIT, REPLAY |
| tx_id | yes | string | "" | Transaction ID |
Usage example
Configure the analysis scenario and specify the transaction stage and transaction ID. The execution example is as follows:
obdiag rca run --scene=transaction_not_ending --env phase=UNSUBMITTED --env tx_id=0x1