Bare Metal and Virtual Machine DB Systems

Oracle Cloud Infrastructure offers 1-node and 2-node RAC DB Systems on either bare metal or on a virtual machine.

You can manage these systems by using the Console, API, Enterprise Manager, Enterprise Manager Express, SQL Developer, and the dbcli CLI.

Note

This documentation is intended for Oracle database administrators and assumes familiarity with Oracle databases and tools. If you need additional information, see the product documentation available at http://docs.oracle.com/en/database/.

Supported Database Editions and Versions

All 1- and 2-node RAC DB Systems (both Bare Metal and Virtual Machine) support the following Oracle Database editions:

  • Standard Edition
  • Enterprise Edition
  • Enterprise Edition - High Performance
  • Enterprise Edition - Extreme Performance (required for 2-node RAC DB Systems)

The supported database versions are:

  • Oracle Database 12c Release 2 (12.2)
  • Oracle Database 12c Release 1 (12.1)
  • Oracle Database 11g Release 2 (11.2)

Bare Metal DB Systems

There are two types of bare metal DB Systems:

  • 1-node DB Systems consist of a single bare metal server running Oracle Linux 6.8, with locally attached NVMe storage. If the node fails, you can simply launch another system and restore databases from current backups.
  • 2-node RAC DB Systems consist of two bare metal server running Oracle Linux 6.8, in a RAC configuration, with direct-attached shared storage. The cluster provides automatic failover. This system supports only Enterprise Edition - Extreme Performance and is recommended for production applications.

When you launch a Bare Metal DB System, you select a single Oracle Database Edition that applies to all the databases on that DB System. The selected edition cannot be changed. Each DB System can have multiple database homes, which can be different versions. Each database home can have only one database, which is the same version as the database home.

Shapes for 1- and 2-Node RAC DB Systems

When you launch a DB System, you choose a shape, which determines the resources allocated to the DB System. The available shapes for a Bare Metal DB System are: 

  • BM.HighIO1.36: Provides a 1-node DB System (one bare metal server), with up to 36 CPU cores, 512 GB memory, and four 3.2 TB locally attached NVMe drives (12.8 TB total) to the DB System.
  • BM.DenseIO1.36: Provides a 1-node DB System (one bare metal server), with up to 36 CPU cores, 512 GB memory, and nine 3.2 TB locally attached NVMe drives (28.8 TB total) to the DB System.
  • BM.RACLocalStorage1.72: Provides a 2-node RAC DB System (two bare metal servers), with up to 36 CPU cores on each node (72 total per cluster), 512 GB memory, direct attached shared storage with twenty 3.2 TB SSD drives (64 TB total).

    Note that the 64 TB storage for this shape is available only in the Phoenix (PHX) region and the Frankfurt (FRA) region. Storage for the Ashburn (IAD) region is twenty 1.2 TB SSD drives (24 TB total).

Storage Considerations

The shape you choose for a Bare Metal DB System determines its total raw storage, but other options, like 2- or 3-way mirroring and the space allocated for data files, affect the amount of usable storage on the system. The following table shows how various configurations affect the usable storage for 1- and 2-node RAC Bare Metal DB Systems.

Shape Raw Storage Usable Storage with Normal Redundancy (2-way Mirroring) Usable Storage with High Redundancy (3-way Mirroring)

BM.HighIO1.36

12.8 TB NVMe

DATA 3.5 TB

RECO 740 GB

DATA 2.3 TB

RECO 440 GB

BM.DenseIO1.36

28.8 TB NVMe

DATA 9.4 TB

RECO 1.7 TB

DATA 5.4 TB

RECO 1 TB

BM.RACLocalStorage1.72

64 TB SSD

DATA 22.1 TB

RECO 5.5 TB

DATA 14 TB

RECO 3.5 TB

Note that the storage information in the table for the 2-node RAC shape applies only to the Phoenix (PHX) region and the Frankfurt (FRA) region. Storage for the Ashburn (IAD) region is 24 TB SSD of raw storage with 2-way mirroring values of DATA 8.6 TB and RECO 1.6 TB, and 3-way mirroring values of DATA 5.4 TB and RECO 1 TB.

Virtual Machine DB Systems

There are two types of DB Systems on virtual machines:

  • 1-node Virtual Machine DB Systems consists of one virtual machine.
  • 2-node Virtual Machine DB Systems consists of two virtual machines.

When you launch a Virtual Machine DB System, you select the Oracle Database Edition that applies to the database on that DB System. The selected edition cannot be changed. Unlike a Bare Metal DB System, a Virtual Machine DB System can have only a single database home. The database home will have a single database, which will be the same version as the database home.

Virtual Machine DB Systems also differ from Bare Metal DB Systems in the following ways:

  • A Virtual Machine DB System database uses Oracle Cloud Infrastructure block storage instead of local storage. You specify a storage size when you launch the DB system, and you can scale up the storage as needed at any time.
  • The number of CPU cores on an existing Virtual Machine DB System cannot be changed.

Shapes for Virtual Machine DB Systems

When you launch a DB System, you choose a shape, which determines the resources allocated to the DB System. The following table shows the available shapes for a Virtual Machine DB System.

Shape CPU Cores Memory

VM.Standard1.1

1

7 GB

VM.Standard1.2

2

14 GB

VM.Standard1.4 4 28 GB
VM.Standard1.8 8 56 GB

VM.Standard1.16

16

112 GB

Storage Options for Virtual Machine DB Systems

Virtual Machine DB Systems use Oracle Cloud Infrastructure block storage. The following table shows details of the storage options for a Virtual Machine DB System. Total storage includes available storage plus recovery logs.

Available Storage (GB) Total Storage (GB)

256

712

512

968
1024 1480
2048 2656
4096 5116
6144 7572
8192 10032
10240 12488
12288 14944
14336 17404
16384 19860
18432 22320
20480 24776
22528 27232
24576 29692
26624 32148
28672 34608
30720 37064
32768 39520
34816 41980
36864 44436
38912 46896
40960 49352

For 2-node RAC Virtual Machine DB Systems, storage capacity is shared between the nodes.