Oracle Database (Standalone & RAC) on OpenShift Virtualization (OCP-V)

Contents

• Overview
• Official Resources & References
• Supported Configuration Matrix
  • Oracle 19c
  • Oracle 26ai
• Detailed Implementation Guides
  • Oracle 19c Standalone
  • Oracle 19c RAC (Real Application Clusters)
• Known Issues and Limits

Overview

This document serves as a centralized index for tested and supported configurations, performance validations, and reference architectures for running Oracle Database workloads on OpenShift Virtualization.

1. Official Resources & References

• Red Hat Blog: Implementing Oracle Standalone and RAC on OCP-V

2. Supported Configuration Matrix

• Oracle 19c

  Instance Type	OS Version	Status
  Standalone	RHEL 8	[Validated]
  Standalone	OL 8	[Validated]
  RAC	RHEL 8	[Validated]
  RAC	OL 8	[Validated]

• Oracle 26ai

  Instance Type	OS Version	Status
  Standalone	RHEL 8	[Validated]
  Standalone	RHEL 9	[Validated]
  Standalone	OL 9	[Validated]
  Standalone	RHEL 10	[Validated]
  Standalone	OL 10	[Validated]
  RAC	RHEL 9	[Validated]
  RAC	OL 9	[Validated]
  RAC	RHEL 10	[Validated]
  RAC	OL 10	[Validated]

All tests performed on both Intel and AMD platforms, OCP 4.18 or above.
Testing is performed with different storage configurations, such as:

• ODF (Block)

3. Detailed Implementation Guides

Select the specific configuration below for deep-dive technical requirements (Networking, YAML snippets, and Tuning):

A. Oracle 19c Standalone

• Storage: ODF via RBD (Block mode)
• Key Tuning: HugePages (2MB), VirtIO-SCSI multiqueue.
• Additional Details: Oracle Database Workloads On OpenShift Virtualization Reference Architecture

B. Oracle 19c RAC (Real Application Clusters)

• Interconnect: Secondary Networks via Multus (SR-IOV recommended).
• Shared Storage: Requires ReadWriteMany (RWX) Block volumes.
• Additional Details: Oracle Database Workloads On OpenShift Virtualization Reference Architecture

D. Tuning Best Practices

• Production-compliant performance improvements derived from HammerDB benchmarking on standalone and RAC instances on OCP-V.
• Additional Details: Oracle Database Performance Tuning Best Practices for OCP-V

4. Known Issues and Limits

• MTU Settings: Ensure consistent MTU (9000 recommended) across the RAC private interconnect.
• IOPS Limits: Review default QEMU disk throttling if performance fluctuates.