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

Database change ticket

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

When to use
Prerequisites
Procedure
Ticket status description
What to do next

Using the database change management capability of ODC (OceanBase Developer Center), OAgent supports creating database change tickets, querying approval progress, and viewing execution results directly within the dialogue. Change execution is handled by the ODC approval process, ensuring that changes are controllable and auditable.

When to use

  • After obtaining a solution through SQL diagnostics or parameter governance, directly create a change ticket in the dialogue for approval.
  • Need to trace the approval nodes, execution status, and failure reasons of a specific change ticket.
  • Parameter changes, data repairs, and more can all be managed through change tickets.

Prerequisites

  • A product connection to ODC has been configured for creating change tickets and querying progress. For details, see Create a product connection.

  • The target cluster and tenant have been selected with @ in the session.

Note

OAgent only creates tickets and queries progress; it does not bypass approval to directly execute changes. After approval, ODC executes the changes on the database.

Procedure

  1. In the session where the changed SQL has been identified, enter the request to create a ticket, for example:

    Help me create a change ticket for the parameter change SQL above.
    Create a database change ticket for this index DDL.
    
  2. Press Enter to send the request, and wait for the Agent to call ODC to create the ticket.

    The Agent submits information such as the change SQL, target tenant and database, and change type to ODC, and returns the ticket number and approval link.

  3. Track the progress in the approval process.

    • You can query the ticket progress at any time in the dialogue:

      Check the approval progress of the ticket I just created.
      What is the current status of ticket CHG2026090200001?
      
    • The Agent will return information such as the current approval node, approver, and execution status.

  4. Verify the result after the change is completed.

    • Repeat the verification steps from the previous solution to confirm the change takes effect. See Parameter check and change governance.

Ticket status description

Status
Meaning
Pending Approval The ticket has been submitted and is awaiting processing at the corresponding approval stage.
Approved Approval completed. Waiting for execution or already in progress.
Executing ODC is executing the change SQL statement.
Completed The change was executed successfully.
Rejected/Execution failed If the approval fails or an error occurs during execution, you can view the error details.

What to do next

  • If the ticket fails, you can paste the error details in the session for the agent to locate the cause.

  • To verify the effect of the change, you can check the metric trends. For more information, see Query resource metrics and task status.

Previous topic

Parameter check and change governance
Last

Next topic

Feature list
Next
on this page
When to use
Prerequisites
Procedure
Ticket status description
What to do next