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

Interpret execution plans

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

When to use
Prerequisites
Procedure
Usage suggestions
What to do next

If you have an execution plan and want to understand the meaning and cost composition of each operator, you can submit the execution plan to the Agent for interpretation operator by operator.

When to use

  • You have obtained an execution plan from OCP, OAS, or a client, but are unclear about the specific meaning of each operator.

  • You need to determine which part of the execution plan is a performance bottleneck.

  • You want to compare two execution plans before and after optimization to confirm whether the optimization took effect.

Prerequisites

  • You have obtained the execution plan content (exported from the OCP or OAS console, or copied from the client).

  • If you need to upload the execution plan file as an attachment, please understand the upload operation. For details, see Upload an attachment.

Procedure

  1. Paste the execution plan content into the session, or upload the execution plan file as an attachment.

  2. Describe your interpretation request, for example:

    Help me interpret this execution plan and identify the bottleneck.
    
  3. Press Enter to send it, and wait for the Agent to complete the interpretation.

  4. View the interpretation result.

    The Agent will explain the following content operator by operator and identify potential performance bottleneck parts in the plan:

    Interpretation dimension
    Description
    Scan method Whether the operator uses full table scan, index scan, or primary key scan.
    Join method The algorithm used for table joins (such as Nested Loop Join, Hash Join, Merge Join) and the selection of the driving table.
    Cost estimation The estimated number of rows and cost for each operator, and the deviation between the estimated and actual values.

Usage suggestions

  • When pasting the execution plan, retain the complete operator tree and cost columns. Missing columns will affect the accuracy of the interpretation.

What to do next

  • If the estimated number of rows deviates significantly from the actual number of rows, it usually indicates that the statistics are outdated. You can proceed with statistics diagnostics. For details, see Statistics diagnostics.

  • To assess the execution plan risk of a new SQL statement or obtain tuning suggestions, see SQL pre-analysis and tuning suggestions.

  • To export the interpretation results to a report, see Export a report.

Previous topic

SQL pre-analysis and tuning recommendations
Last

Next topic

Diagnostic information statistics
Next
on this page
When to use
Prerequisites
Procedure
Usage suggestions
What to do next