Glossary

This topic provides the definitions of terms that you may need to know when you use OAT.

• OAT: OceanBase Administrator Tool, which is used to install and manage OceanBase ecosystem products and components.

• OceanBase Database: A distributed relational database that supports MySQL and Oracle modes.

• Ecosystem products: OceanBase ecosystem products, including OceanBase Cloud Platform (OCP), OceanBase Developer Center (ODC), OceanBase Migration Service (OMS), OceanBase Autonomy Service (OAS), and OceanBase Access Proxy (OB Sharding).

  • OCP: OceanBase Cloud Platform, which is used to manage OceanBase clusters.
  • ODC: OceanBase Developer Center, which is used for database development.
  • OMS: OceanBase Migration Service, which is used for data interaction between homogeneous or heterogeneous data sources and OceanBase Database.
  • OAS: OceanBase Autonomy Service is an intelligent, one-stop diagnostic and autonomy service for developers, O&M engineers, and DBAs. It provides visual monitoring, performance optimization, fault diagnosis, security management, and capacity management capabilities, helping users use OceanBase Database more easily, at a lower cost, and with higher performance.
  • OB Sharding: An OceanBase Database-specific proxy service that receives SQL requests from users, forwards the SQL requests to the best target server, and returns the execution results to users.

• Components: OceanBase components, including MetaDB, InfluxDB, OBDNS, NLB, OpenSearch, SQLAuditStore, and arbitration service.

  • MetaDB: A container-based OceanBase Database service that is pre-installed with OceanBase Proxy for direct external access. It can store metadata for OCP, ODC, and OMS.
  • InfluxDB: A container-based time series database service that stores the monitoring data of data transmission links in OMS.
  • OBDNS: A container-based DNS + Tengine load balancing service. If you do not have an external load balancing device (such as F5), you can use it as a soft load balancer. However, you must configure the DNS server to the server where OBDNS is deployed. It can provide load balancing and high availability for OCP and other ecosystem products.
  • NLB: A load balancer based on OpenResty. It has the advantages of high availability, simple deployment, and low resource consumption. It can provide load balancing for OCP, ODC, and OMS.
  • OpenSearch: A distributed search and analysis engine based on Lucene. It supports real-time data storage, retrieval, and complex analysis. It has high scalability and can easily build clusters to handle massive data. It provides flexible queries through RESTful APIs. It is widely used in log analysis, full-text search, and real-time data monitoring. It can quickly process structured and unstructured data, helping enterprises gain insights and optimize decisions. OCP uses OpenSearch to retain logs for end-to-end tracing. O&M engineers can view the execution time of each transaction or each SQL statement in the entire chain of access on OCP, thereby identifying issues in the entire access chain.
  • SQLAuditStore: A V$SQL_AUDIT data persistence tool developed in Go. It periodically pulls V$SQL_AUDIT data from memory that may be lost due to the eviction mechanism and securely stores it to local files (supporting CSV format and allowing compression of historical files), Alibaba Cloud Simple Log Service (SLS), or an OpenSearch cluster.
  • Arbitration service: An independent, lightweight observer process deployed separately from OceanBase clusters. It starts in a special mode and plays the role of an arbitration member at the log stream level.

• Tools: Peripheral O&M tools that can be selected upon delivery, including OBLB, OBClient, OpsToolkit, SQL Diagnoser, Obdiag, OB-Loader-Dumper, Sysbench, and OBLENS.

  • OBLB: A load balancing service based on iptables. If you do not have an external load balancing device (such as F5) and the traffic is not heavy, you can use it as a soft load balancer for OceanBase clusters.

  • OBClient: A command-line client tool specifically designed for OceanBase Database. You can use OBClient to connect to MySQL and Oracle tenants of OceanBase Database.

  • OpsToolkit: An OceanBase O&M toolbox for customers and O&M engineers, containing obcli (a collection of debug SQL statements) and obtcl (a tool for cluster O&M management).

  • SQL Diagnoser: An agile SQL diagnostic tool that directly analyzes business clusters to identify common suspicious SQL statements and hidden performance issues.

  • Obdiag: A tool for collecting OceanBase-related logs and generating AWR reports. It provides data collection capabilities for frontline service personnel to troubleshoot faults, reducing the information exchange cost between front-end and back-end support personnel.

  • OB-Loader-Dumper: A client import and export tool that can import schema or data to OceanBase Database and export database objects to SQL or CSV files.

  • Sysbench: A multi-threaded benchmarking tool that can perform performance testing in terms of CPU, memory, threads, I/O, and databases. It is commonly used to evaluate database load under various system parameters.

    Notice

    The Sysbench in OAT is an OceanBase-modified version called ob-sysbench.

  • OBLENS: A performance analysis platform based on multiple data sources. It can be deployed in various flexible ways. Currently, it primarily runs by deploying a server and pushing data from the client side. OAT provides the client-side installation feature as a tool management option.