DB_PERFORMANCE_PROFILE

DB_PERFORMANCE_PROFILE is used by Resource Manager and Exadata I/O Resource Management (IORM) to provide easier resource management for CDBs and PDBs.

Property	Description
Parameter type	String
Syntax	DB_PERFORMANCE_PROFILE = string
Default value	There is no default value.
Modifiable	ALTER SYSTEM
Modifiable in a PDB	Yes
Basic	No
Oracle RAC	The same value should be set on all instances.

On non-Exadata systems, this parameter can be set at the PDB level for use by Resource Manager. On Exadata systems, this parameter can be set at the PDB level for use by Resource Manager, and at the CDB level for use by IORM.

• On non-Exadata systems:

  • You can set this parameter at the PDB level to specify a performance profile for Resource Manager. In this case, a CDB resource plan specifies different resource controls for a performance profile using the DBMS_RESOURCE_MANAGER.CREATE_CDB_PROFILE_DIRECTIVE procedure, and a PDB with a matching performance profile will use the specified controls.

  • There is no practical use for setting this parameter at the CDB level on a non-Exadata system.

• On Exadata systems:

  • Similar to non-Exadata systems, you can set this parameter at the PDB level to specify a performance profile for Resource Manager.

  • You can also set this parameter at the CDB level to specify an IORM profile. This profile is pushed down to the Exadata storage cells, where it is used by IORM to manage I/O allocation.

  • Note that setting this parameter at the CDB level identifies the entire database to IORM and has no effect on how Exadata Smart Flash Cache is divided among PDBs. To control flash cache allocation between PDBs, you must use Resource Manager, that is, you must either create a CDB resource plan and enable that plan, or, if using profile directives, specify a performance profile for each PDB. This instructs Resource Manager to enforce per-PDB flash cache minimums and limits, while IORM continues to manage I/O resources at the CDB level.

The value of this parameter can be up to 30 characters and is not case sensitive.

See Also:

• Oracle AI Database Administrator’s Guide to learn more about how Resource Manager uses this parameter

• Oracle Exadata System Software User’s Guide to learn more about how IORM uses this parameter