| Architecture | DISTRIBUTED SQL: One logical database distributes data and processing across nodes with their own storage and transaction engines, supporting growth without a shared database disk volume. | SINGLE INSTANCE OR RAC: RAC lets multiple instances access the same database on cluster-aware shared storage, coordinating cached data across instances. |
|---|
| SQL Compatibility | MYSQL AND ORACLE COMPATIBILITY: Tenant modes support familiar SQL and stored logic. Oracle-compatible mode includes PL procedures, packages, and triggers, but differences such as unsupported PL conditional compilation require application review. | NATIVE ORACLE ENVIRONMENT: Oracle SQL, PL/SQL, packages, and database-side programming preserve the native execution environment for existing Oracle applications. |
|---|
| Scalability | DISTRIBUTED CAPACITY: Additional nodes provide capacity for data partitions and their write processing. Partition placement spreads work across nodes; contention on a single hot record remains. | INSTANCE AND CLUSTER GROWTH: Single-instance deployments scale through server capacity; RAC adds active instances over shared storage. RAC scaling retains shared-storage and inter-instance coordination requirements. |
|---|
| Transactions & Consistency | DISTRIBUTED ACID TRANSACTIONS: Updates across tables and database nodes commit or roll back together, supporting operations such as creating an order and updating inventory in one transaction. | ACID TRANSACTIONS: Related updates commit or roll back together. RAC coordinates access to one database across instances while preserving transactional consistency. |
|---|
| Data Integrity | DATABASE-ENFORCED RULES: Oracle-compatible tenants support primary keys, foreign keys, unique, check, and not-null constraints, plus triggers for database-side business rules. | RELATIONAL INTEGRITY: Primary keys, foreign keys, unique, check, and not-null constraints enforce data rules; triggers support additional database-side logic. |
|---|
| Availability & Recovery | - SERVICE CONTINUITY: Multi-Paxos replication supports automatic failover with RPO = 0 and RTO < 8 seconds when a minority of nodes fail.
- RECOVERY: Tenant-level data backups and log archiving support restoration.
| CLUSTER AND STANDBY PROTECTION: RAC supports service availability across instances; Data Guard maintains standby databases for disaster recovery. RMAN supports backup and recovery. |
|---|
| Storage Engine | ENCODED, COMPRESSED STORAGE: Column-aware encoding and configurable compression reduce redundancy. Oracle-compatible tenants support LZ4 and Zstandard, providing storage-footprint controls within the database. | COMPRESSION CHOICES: Enterprise Edition includes Basic Table Compression; Advanced Row Compression requires the Advanced Compression option. This makes compression type and licensing relevant to storage planning. |
|---|
| Multi-Tenancy | TENANT RESOURCE ALLOCATION: Multiple tenants share a cluster with separate CPU and memory resource units, supporting consolidation and capacity adjustments for individual application databases. | PLUGGABLE DATABASE CONSOLIDATION: PDBs share a container database; Resource Manager controls allocations among PDBs and workloads. PDB count entitlements depend on licensing. |
|---|
| Workload Support | TRANSACTIONS AND ANALYTICS: Rowstore, columnstore, and hybrid row/column table formats support transactional access and analytical queries within the same database. | TRANSACTIONS AND ANALYTICS: Relational SQL and parallel execution support mixed workloads. Database In-Memory adds a transaction-consistent columnar representation in memory alongside row-based storage, subject to applicable entitlements. |
|---|
| Deployment Options | SELF-MANAGED CONTROL: Operate database nodes on your infrastructure, with control over placement, capacity, maintenance, backups, and recovery configuration. | SELF-MANAGED CONTROL: Operate single-instance or RAC deployments on supported infrastructure, managing database maintenance, storage, backups, and recovery. RAC also requires Clusterware and supported shared storage. |
|---|
| Multi-Cloud Deployment | INFRASTRUCTURE CHOICE: Supports public-cloud (including AWS, GCP, and Azure), private-cloud, and on-premises deployments, enabling provider choice and hybrid-cloud strategies. | DEPLOYMENT FLEXIBILITY: Enterprise Edition supports on-premises, OCI, and authorized cloud environments. Infrastructure support and license terms govern the available configurations. |
|---|
| Multi-model & Hybrid Search | STRUCTURED AND SIMILARITY RETRIEVAL: MySQL-compatible tenants support JSON and vector search, combining relational data access with vector-distance queries and filtering. These capabilities do not imply identical support in Oracle-compatible tenants. | INTEGRATED RETRIEVAL: AI Vector Search and Oracle Text support hybrid keyword and semantic search, with configurable fusion of text and vector rankings. |
|---|
| Open Source | LICENSING OPTIONS: OceanBase offers a commercially licensed Enterprise Edition and an open-source edition under the Apache License 2.0. The open-source edition does not provide Oracle-compatible mode. | COMMERCIAL AND FREE EDITIONS: Enterprise Edition uses commercial licensing, with additional options where applicable. A separate resource-limited Free edition is available under Oracle's Free Use Terms. |
|---|