OAgent supports checking, changing, verifying OceanBase parameters, and generating rollback plans within a dialogue. To ensure change safety, OAgent only generates executable SQL and verification plans; it does not directly modify parameters without going through the approval process.
When to use
- During troubleshooting, if you suspect an abnormal parameter value and need to verify the current value against the default and valid range.
- When you need to adjust a parameter and want to obtain the change SQL, the verification method before and after the change, and the rollback SQL.
- If a change involves multiple interdependent parameters, and you want to confirm the order and scope of impact.
Prerequisites
- You have configured an OCP connection for the product to which the target cluster belongs.
- You have selected the target cluster in the session using
@. - For changes involving execution, the target cluster must be selected to execute the change SQL. See Database change ticket.
Procedure
Describe your parameter governance requirement in the session, for example:
Check the values of memory_limit and parallel_max_servers for this cluster. Change parallel_max_servers to 64 for me, and provide the change SQL, verification method, and rollback SQL. Which features will be affected by this parameter change?Press Enter to send the request and wait for the Agent to generate a plan.
The Agent typically processes the request in the following order:
- Check: Query the current parameter value, default value, whether it can be dynamically modified, its valid range, and compatibility with the cluster version.
- Change: Generate a change SQL in the
ALTER SYSTEM SET ...format and mark the adjustment order for interdependent parameters. - Verify: Provide the verification steps after the change (e.g., query the value again, observe related metrics, check for errors).
- Rollback: Provide the SQL to roll back to the original value and the corresponding verification method.
After confirming the plan, submit the generated change SQL to ODC for approval via a change ticket. See Database change ticket.
Note
OAgent does not directly perform parameter changes on the cluster; all changes must be approved via an ODC ticket before execution. Change auditing and traceability are handled by ODC.
Typical example
query: Change parallel_max_servers from 128 to 64 and provide the complete plan.
Agent output example:
* Check result: `parallel_max_servers = 128`, which can be dynamically modified. Value range: [0, 10000].
* Change SQL: `ALTER SYSTEM SET parallel_max_servers = 64;`
* Verification: Execute `SHOW PARAMETERS LIKE 'parallel_max_servers';` to confirm the value; observe whether parallel-related wait events have changed.
* Rollback SQL: `ALTER SYSTEM SET parallel_max_servers = 128;`
What to do next
If an exception occurs after the change, you can trigger root cause analysis in the same session. For more information, see Root cause analysis for exceptions.
Parameter changes are a type of database change. For related process specifications, see Database change ticket.