Scenarios
You can use the obdiag rca run command to analyze the transaction_execute_timeout scenario based on internal table data and logs of OceanBase Database.
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.
Supported environment variables
| Variable | Required? | Data type | Default value | Description |
|---|---|---|---|---|
| tenant_id | Yes | string | "" | The ID of the tenant. |
| trace_id | Yes | string | "" | The trace ID. |
| err_type | Yes | string | "" | The error type. Valid values are statement is timeout and transaction is timeout. |
Examples
Specify the scenario, ID of the tenant, trace ID, and error type in the command.
obdiag rca run --scene=transaction_execute_timeout --input_parameters='{"tenant_id":" 1002","trace_id":" YXXXXXXXXXX","err_type":" statement is timeout"}'