5.2.8 Using IORM Profiles

I/O Resource Management (IORM) interdatabase plans support profiles to ease management, and configuration of interdatabase plans for hundreds of databases.

Profiles introduce a way to allocate I/O resources for groups of databases. Profiles are specified as directives for the interdatabase plan, and are configured using the CellCLI utility. A profile directive consists of an identifier (name), and a set of attributes. To differentiate between a database directive and a profile directive, a qualifier attribute called type is used. The type attribute can be set to either database or profile. The following is an example of the type attribute syntax:

CellCLI> ALTER IORMPLAN DBPLAN=((name=gold, share=10, type=profile),  -
                                (name=silver, share=5, type=profile), -
                                (name=bronze, share=1, type=profile))

The preceding example contains three directives for profiles, GOLD, SILVER and BRONZE. All databases with db_performance_profile set to GOLD would automatically get 10 shares of cell I/O resources. Likewise, in the example above, databases with the SILVER profile would get 5 shares, and databases with the BRONZE profile would get 1 share.

After your create your profiles, you then map new and existing databases to one of the profiles defined in the interdatabase plan. This is done by setting the db_performance_profile initialization parameter for each database to the name of the desired profile. You must then restart the database. As with Oracle Database Resource Manager plans, the IORM profile information is automatically pushed to all the storage servers (cells). The following SQL command displays how the initialization parameter can be set for a database:

SQL> ALTER SYSTEM SET db_performance_profile=gold SCOPE=spfile;

SQL> SHUTDOWN IMMEDIATE

SQL> STARTUP

When adding a new database, you can set the db_performance_profile parameter and restart the database. The database automatically inherits the profile attributes without having to modify the interdatabase plan. You can also create interdatabase plans with a mix of profile directives, and database directives.

You can view existing profiles using the LIST IORMPROFILE command.

Note the following when managing interdatabase profile plans:

• The db_performance_profile parameter is not a dynamic parameter, so profile updates require a database restart.
• If the type attribute is not specified, then the directive defaults to the database directive.
• An interdatabase plan can specify only 8 profile directives, and 1024 database directives.
• Level, allocation, and role cannot be specified with a profile directive.
• The words OTHER, and DEFAULT are reserved words. A profile name cannot be OTHER or DEFAULT.
• The type attribute cannot be specified with category plans.
• Profiles cannot be specified in conjunction with category plans.
• If multiple databases are mapped to the OTHER directive, then Oracle Exadata Storage Server does not use Oracle Database Resource Manager for these databases. All of the I/O requests are treated the same.