OceanBase
English日本語简体中文
Docs Home
Products
Integrations
Release Notes

Databases

OceanBase DatabaseOceanBase AI DatabaseOceanBase Cloud OceanBase Best Practices

Tools

OceanBase Cloud PlatformOceanBase Migration ServiceOceanBase Developer CenterOceanBase Migration AssessmentOceanBase Admin ToolOceanBase Loader and DumperOceanBase DeployerKubernetes operator for OceanBaseOceanBase Diagnostic Tool OceanBase Binlog ServiceOceanBase DataPilotOceanBase OAgent

Connectors and Middleware

OceanBase Database Proxy OceanBase Connector/C OceanBase Connector/J OceanBase Connector/ODBC OceanBase Connector/NETOceanBase Command-Line Client

Databases

OceanBase DatabaseOceanBase AI DatabaseOceanBase Cloud OceanBase Best Practices

Connectors and Middleware

OceanBase Database Proxy OceanBase Connector/C OceanBase Connector/J OceanBase Connector/ODBC OceanBase Connector/NETOceanBase Command-Line Client

Tools

OceanBase Cloud PlatformOceanBase Migration ServiceOceanBase Developer CenterOceanBase Migration AssessmentOceanBase Admin ToolOceanBase Loader and DumperOceanBase DeployerKubernetes operator for OceanBaseOceanBase Diagnostic Tool OceanBase Binlog ServiceOceanBase DataPilotOceanBase OAgent
OceanBase DatabaseOceanBase Cloud ToolsConnectors and MiddlewareLifecycle Support Policy

OceanBase OAgent

V2.2.0
  • Product overview
    • What is OAgent?
    • Key features
    • System architecture
    • Use cases
  • Quick start
  • Deployment
  • Overview
  • Sessions and diagnosis
    • Manage sessions
    • Switch dialogue models
    • Use @ to mention the analysis target
    • View the tool invocation process
    • Upload an attachment
    • Data visualization
    • FAQ
    • Export a report
  • Tools
  • Skill Management
  • Channel management
  • Knowledge base
    • Built-in knowledge base
    • Custom knowledge base
  • Scheduled tasks
    • Overview of scheduled tasks
    • Create a scheduled task
  • View usage
  • Model configuration
    • Manage model services
    • Model scoring
  • Settings and security
    • Product management
    • Experimental features
  • Best practices
    • Perform a cluster health inspection
    • Query cluster and topology information
    • Query resource metrics and task status
    • Read-only queries
    • Alert query and troubleshooting guide
    • Root cause analysis of exceptions
    • ASH diagnostic report
    • Analyze slow SQL, TopSQL, and abnormal SQL
    • SQL pre-analysis and tuning recommendations
    • Interpret execution plans
    • Diagnostic information statistics
    • Parameter check and change governance
    • Database change ticket
  • Appendix
    • Feature list
    • Built-in Skills
  • Release notes
    • OAgent V2.2.0 Release note
    • OAgent V2.1.0 Release note
    • OAgent V2.0.0 Release note
    • OAgent V1.8.0 Release note

Download PDF

Document Feedback
  1. Documentation Center
  2. OceanBase OAgent
  3. V2.2.0

Experimental features

Last Updated:2026-11-20 07:25:11

Kernel read-only SQL query (Experimental)
Configure the database execution user
Enable status and effective capabilities
What to do next

Experimental Features are used to manage Agent capabilities that are still under validation. All features are disabled by default. Click Platform Settings in the left navigation bar to go to the Experimental Features page.

  • Enabling experimental features allows you to experience them earlier, but no formal commitment is made regarding stability and compatibility.

  • After disabling an experimental feature, the related capability and entry will no longer be visible.

Kernel read-only SQL query (Experimental)

Allows the Agent to execute read-only SQL (SELECT, SHOW, EXPLAIN) on managed clusters through OCP for kernel diagnostic scenarios such as slow SQL evidence collection and execution plan analysis. Credentials are centrally managed by OCP; OAgent does not access plaintext kernel passwords.

Configure the database execution user

Before enabling this feature, you must configure the database execution user. We recommend using the default configuration oagent_ro:

  • OAgent always uses this user when calling the OCP SQL query interface.

  • This user must match the OCP allowlist and the registered database credentials of the target tenant. For detailed configuration methods, see OCP Configuration Tips on the page.

Enable status and effective capabilities

When the feature is in the Enabled state, the Agent can perform the following operations:

  • Query kernel data using the ob_sql_query tool.

  • Generate parameter change recommendations using ob_parameter_change_advisor.

The currently used database execution user is displayed along with the feature status, for example, "Execution user is oagent_ro".

What to do next

  • For information about viewing and starting/stopping tools, see Tools.

  • For information about usage and statistics, see Usage statistics.

Previous topic

Product management
Last

Next topic

Perform a cluster health inspection
Next
on this page
Kernel read-only SQL query (Experimental)
Configure the database execution user
Enable status and effective capabilities
What to do next