2.1.1.1 OEDA Web User Interface Settings and Options for Exascale

The following list describes the Exascale-specific settings and options, which are spread across different pages in the OEDA Web user interface.

• Select Hardware page

  Exascale configuration commences on the OEDA Select Hardware page. For each individual Exadata Database Machine, you must click the check box to Enable Exascale. Otherwise, the following configuration options are not available.

• Exascale page

  After you select the option to Enable Exascale and apply the settings in the Select Hardware page, OEDA includes the Exascale page, which you use to define the Exascale clusters.

  Use the Exascale page to specify the following settings and options:

  • Cluster Name: Specify the name used to identify the Exascale cluster.

  • ERS IP Address: Specify an IP address for Exascale control services (also known as Exascale RESTful Services or ERS).

    The specified IP address should reside in the Exadata administration network (also known as the management network).

    The specified IP address is associated with a highly-available virtual IP (VIP) network interface, which provides a consistent network end point for Exascale control services. The VIP is hosted by one of the Exadata storage servers, which also runs front-end ERS processes. If the storage server or ERS instance becomes unavailable, then the VIP moves to another server containing front-end ERS processes.

  • ERS Host Name: Specify an host name for Exascale control services (also known as Exascale RESTful Services or ERS).

    The specified host name is associated with the ERS IP Address.

  • Available nodes/Selected nodes: Specify the Exadata storage servers that become members of the Exascale cluster.

    The specified cells must all be of the same Exadata storage server type. That is, they must all be High Capacity (HC) or Extreme Flash (EF).

  • Storage Pool Name: Specify the name for the storage pool.

    You can only define one storage pool for each Exascale cluster using the OEDA Web user interface.

    Note:

    The media type for the storage pool matches the underlying Exadata storage server type. For example, if the Exadata system uses High Capacity (HC) storage cells, then the storage pool media type will be HC.

  • Storage Pool Size (%/GB/TB): Specify the amount of storage space to provision in the storage pool.

    Specify a percentage of the available space or an amount of storage space in gigabytes (GB) or terabytes (TB).

  On the Exascale page, the following options are also available by clicking the Advanced button:

  • Disable ERS IP Address: This option configures Exascale without a highly-available VIP network interface that provides a consistent network end point for Exascale control services. If you select this option, then ERS IP Address and ERS Host Name are disabled.

    Note:

    Using this option is generally not recommended and it primarily exists to support Exascale configurations on existing Exadata systems that have no spare IP addresses to support the ERS VIP.

  • Enable ERS Network ID: This option adds a field to specify the ERS Network ID value associated with the Exascale cluster. The ERS Network ID is used to maintain the highly-available virtual IP (VIP) network interface that provides a consistent network end point for Exascale control services (ERS).

    Note:

    This option is not required when deploying only one Exascale cluster in the subnet supporting the ERS IP address.

    However, when multiple Exascale clusters have ERS IP addresses that share the same subnet, each Exascale cluster requires a unique ERS Network ID.

    By default, OEDA attempts to allocate a unique ERS Network ID to each Exascale cluster. However, this option enables users to provide a specific ERS Network ID value.

• Define Clusters page

  The Define Clusters page configures the Oracle Grid Infrastructure (GI) clusters on the Exadata Database Machine.

  To enable Exascale storage on a GI cluster, you must use the Exascale clusters list to select an Exascale cluster that you defined previously on the Exascale page. If you do not select an Exascale cluster, then Oracle Automatic Storage Management (ASM) is used for the GI cluster and all of the databases that it contains.

  Enabling Exascale storage on a GI cluster implicitly creates an Exascale vault, which is used to store the Oracle Cluster Registry (OCR) and voting files. Consequently, you must also specify:

  • Vault Name: Specify a name to identify the Exascale vault.

  • Vault Size: Specify the amount of storage to provision for the vault.

  Additionally, if the system is configured to use Virtual Machines (VMs) for the database servers, you are presented with the option to Use Exascale for VM file storage. If you select the check box to enable this option, Exascale is used to store the guest image files for Exadata database server VMs.

  Using Exascale to store VM images removes previous constraints imposed by the limited amount of local storage space available on each physical Exadata database server. Furthermore, VM images on Exascale are easily accessible from any VM host. This capability effectively decouples VM guests and hosts, providing the infrastructure to enable quick and easy migration of a VM guest to another host.

  All other settings and options on the Define Clusters page are unaffected by Exascale.

• Create Database page

  The Create Database page is used to create Oracle databases on the Exadata Database Machine.

  To enable Exascale storage for a database, you can:

  • Use the Available vaults for this database list to select a previously defined Exascale vault.

  • Click Add Vault, and specify the Vault Name and Vault Size.

  All other settings and options on the Create Database page are unaffected by Exascale.