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

Upload an attachment

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

Procedure
Best practices

You can upload files as attachments in a session for the agent to analyze in context. Typical scenarios include: having the agent interpret an exported execution plan, analyze a segment of error logs, or answer questions based on internal company documentation.

Procedure

  1. In the lower-right corner of the session input box, click the attachment icon.

  2. In the file selection dialog box that appears, select a local file and click Open.

    After the upload is successful, an attachment card will be displayed above the input box, containing the file name, file type, and file size, for example, ocp-host-credential-api.html text/html · 8 KB. Click the close button in the upper-right corner of the card to remove the attachment.

  3. Enter your request for the attachment in the input box, for example, "Interpret the performance bottlenecks in this execution plan", and press Enter to send it.

Best practices

  • When uploading execution plans or SQL files, it is recommended to also specify the cluster, tenant, and database names. This helps the agent provide more accurate conclusions by considering the table structure and statistics.

  • When uploading log segments, it is recommended to capture content from before and after the time window when the issue occurred, and describe the symptom and occurrence time.

  • If you need to archive documents for long-term retrieval and reuse, please upload them as custom knowledge base files via Knowledge Base, rather than repeatedly uploading attachments in each session. For details, see Custom knowledge base.

Previous topic

View the tool invocation process
Last

Next topic

Data visualization
Next
on this page
Procedure
Best practices