5.2 Using Resource Profiles with Exascale Volumes

This topic describes how to manage Exascale resources by associating resource profiles with Exascale volumes and volume groups.

Before Oracle Exadata System Software release 26.1.0, resource management for Exascale volumes and volume groups was limited to provisioning a number of I/Os per second (IOPS) for each volume or volume group using the iopsProvisioned attribute. Using this arrangement, access to other resources (such as cache space) was proportional to the iopsProvisioned setting.

Starting with Oracle Exadata System Software release 26.1.0, you also associate resource profiles with Exascale volumes and volume groups. This change aligns resource management across all clients that share an Exascale vault and enables consistent management of many Oracle databases, Exascale volumes, and volume groups.

To associate a resource profile with an Exascale volume or volume group, you must specify the resource profile name in the resourceProfile attribute. You can specify the resource profile setting when you create a new volume or volume group. For example:

@> mkvolume 100g --attributes vault=my-vols,resourceProfile=gold-resource-profile

@> mkvolumegroup vol-group1 --attributes resourceProfile=gold-resource-profile

You can also change the resource profile setting when you alter an existing volume or volume group. For example:

@> chvolume vol0125_79e1c93ccfd246be8fe14a8092f38991 --attributes resourceProfile=silver-resource-profile

@> chvolumegroup volgrp0025_ce7c459718d94a2ea8eaa066adf43db7 --attributes resourceProfile=silver-resource-profile

The following requirements and restrictions also apply:

• Each volume or volume group can be associated with only one resource profile at a time.

• A volume or volume group cannot be associated with a resource profile and at the same time have I/O bandwidth provisioned using the iopsProvisioned attribute.

  For existing volumes and volumes groups you must set the provisioned I/O bandwidth to zero (iopsProvisioned=0) before you can specify the resourceProfile attribute.

• If a volume is part of a volume group, the group's resource sharing policy (specified by the resourceSharing attribute setting) governs the behavior of resource management:

  • If the group is not enabled for resource sharing (resourceSharing=none), resource management is governed by the resource profile settings associated with each individual volume.

  • If the group uses specified resource sharing (resourceSharing=specified), resource management applies the resource profile associated with the volume group.

  • The aggregate group resource sharing policy (resourceSharing=aggregate) is not permitted in conjunction with resource profiles. An error is returned if you attempt to create an incompatible configuration.

• Unless explicitly specified otherwise, when a volume clone is created, the resourceProfile setting is copied from the parent volume. After creation, the clone is an independent entity and the resourceProfile setting can be changed independently.

• A volume snapshot inherits the resourceProfile setting from its parent volume. In this case, no change is permitted to the resourceProfile setting.