Applicable scenarios
This article is suitable for root cause analysis based on transaction error codes. The currently supported error codes are -4030, -4121, -4122, -4124, and -4019. The analysis is based on the internal table data and logs of the OceanBase database.
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 |
|---|---|---|---|---|
| error_code | Yes | string | "" | Error code, optional -4030, -4121, -4122, -4124, -4019 |
Usage example
Configure the analysis scenario and specify the error code. The execution example is as follows:
obdiag rca run --scene=transaction_not_ending --env error_code=-4121