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

Root cause analysis of exceptions

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

When to use
Prerequisites
Procedure
What to do next

After an event such as instantaneous jitter or abnormal connection count occurs in the database, you can initiate a conversation to identify the possible root cause.

When to use

  • The cluster experiences short-term jitter and you need to retrospectively analyze the cause.

  • The number of connections or active sessions surges, and you need to confirm the trigger source.

  • You have received an exception notification and need to quickly assess the impact scope and root cause before handling it.

Prerequisites

You have configured the OCP and OAS connections for the product to which the target cluster belongs.

Procedure

  1. Type @ in the session to select the target cluster and tenant.

  2. Describe the exception phenomenon and the time it occurred, for example:

    The connection count for this cluster suddenly spiked around 15:20 yesterday. Please help me analyze the cause.
    

    You can also click the shortcut Root Cause Analysis of Exceptions on the Create Conversation page.

  3. Press Enter to send the request and wait for the Agent to complete the analysis.

    The Agent will make a comprehensive judgment based on information such as the exception details, root cause analysis results, and session snapshots at the time of the exception.

  4. View the root cause analysis conclusion.

    The Agent outputs a list of root causes ranked by likelihood and provides verification suggestions for each.

Note

The root cause analysis conclusion is inferred from monitoring and sampled session data and serves as an auxiliary judgment. Before taking any remedial action, verify the root cause according to the Agent's verification suggestions.

What to do next

  • Expand Tool Output to check the event and session snapshot data referenced in the conclusion. For more information, see View the tool invocation process.

  • If the root cause indicates execution plan degradation, you can proceed with statistics diagnostics. For more information, see Statistics diagnostics.

Previous topic

Alert query and troubleshooting guide
Last

Next topic

ASH diagnostic report
Next
on this page
When to use
Prerequisites
Procedure
What to do next