Before you can use Oracle Database Quality of Service (QoS) Management, you must configure the databases.
8.1.1 Configuring the Databases
When configuring the Oracle RAC databases to work with Oracle Database QoS Management, the server pool configuration tasks are not required for administrator-managed databases.
- For policy-managed databases, the database administrator (DBA) requests access to a server pool to be used for the database. The cluster administrator creates a server pool for the DBA and grants access to this server pool to the DBA. If the cluster administrator user is the same as the DBA user, then the server pool can be created at the time DBCA is run by selecting the Policy-managed option within DBCA. The server pool can also be created after installation by using Server Control (SRVCTL).
The minimum size of this server pool is the number of database instances. If the maximum size of the server pool is greater than the minimum size, then new instances can be added to the database to handle peak workloads or to accommodate growth.
For administrator-managed databases, the databases are automatically configured to run in the Generic server pool.
- For policy-managed databases, the DBA creates an Oracle RAC database in the allocated server pool by selecting the Policy-managed option within DBCA.
- The DBA creates database services that are managed by Oracle Clusterware. The application users connect to the database using these services.
- The DBA enables the database for Oracle Database QoS Management using Enterprise Manager Cloud Control.
The initial configuration tasks for the Oracle Database QoS Management administrator are covered in more detail in the following sections.
For Oracle Solaris platforms, there is an additional consideration.
8.1.2 Installing and Configuring Oracle Grid Infrastructure for a Cluster
The installation and configuration of Oracle Grid Infrastructure for a cluster is not covered in this book.
8.1.3 Creating and Configuring Server Pools
By default, a server pool called the Free pool is created during Oracle Grid Infrastructure installation.
To create server pools for your Oracle RAC database, you can use SRVCTL or Oracle Enterprise Manager.
When you use DBCA to create an Oracle RAC database, Oracle recommends that you select policy-managed for the database, and choose the server pools which the database instances should run in. If you choose the create an administrator-managed Oracle RAC database, then the database runs exclusively in the Generic server pool, which is created during the installation of Oracle Grid Infrastructure.
If you use a cluster administrator that is separate from the database administrator, then only the cluster administrator user can create server pools. The cluster administrator then grants privileges on the server pools to the operating system user that owns the Oracle RAC installation.
Note:When creating a server pool for use with Oracle Database QoS Management, do not configure the
srvctl add svrpoolor
srvctl modify svrpoolcommands) for the server pool. Full resource management is not supported in such a configuration because Oracle Database QoS Management cannot change server pool sizes. This is the same limitation that exists for resource management of administrator-managed databases.
Oracle Clusterware Administration and Deployment Guide for information about server pools
Oracle Real Application Clusters Administration and Deployment Guide for information about using SRVCTL to create a server pool
Oracle Real Application Clusters Installation Guide for Linux and UNIX for information about using DBCA to create an Oracle RAC database
Oracle Clusterware Administration and Deployment Guide for more information about the cluster administrator user.
8.1.4 Creating and Configuring an Oracle RAC Database
The steps for creating and configuring an Oracle RAC database are not covered in this book.
When creating a database, Oracle recommends that you choose to create a policy-managed Oracle RAC database and specify the server pools in which it should run. If you create an administrator-managed Oracle RAC database, then it runs exclusively in the Generic server pool.
After you have created the databases, perform the following steps to configure the databases for use with Oracle Database QoS Management:
220.127.116.11 Modifying Database Initialization Parameters
CPU_COUNT parameter for each database instance that runs in a server pool must be set to the same value if the database is managed by Oracle Database QoS Management.
On each server, the sum of the values for
CPU_COUNT for all database instances running on that server must be less than or equal to the physical CPU count. For example, if you have a server with eight CPUs, and there are two database instances running on this server, then, for the databases to be managed by Oracle Database QoS Management, the
CPU_COUNT parameter for each database instance must be set so that the values of the
CPU_COUNT parameters for all instances on the server add up to eight or less. For example, you could have
CPU_COUNT=3 on one instance and
CPU_COUNT=4 on the other instance, or
CPU_COUNT=6 on one instance and
CPU_COUNT=2 on the other instance.
By default, the CPU count of each database that is started on a server is set to the number of physical CPUs installed for that server.
If you are running more than one database in a server pool, then using the default settings for
CPU_COUNT will cause Oracle Database QoS Management to report a violation. To avoid this error, manually configure the
CPU_COUNT value in the SPFILE using either Oracle Enterprise Manager or SQL*Plus.
- Use SQL*Plus to modify the
CPU_COUNTdatabase initialization parameter for all instances of your Oracle RAC database:
ALTER SYSTEM SET cpu_count=n SCOPE=BOTH SID='*';
In the previous command, n is the number of CPUs that should be used by the database instances.
CPU_COUNTis a dynamic parameter that is not set by default. It should be set to the maximum number of CPUs that the database instance should utilize at any time. The sum of the values of
CPU_COUNTfor all instances on a server should not exceed the number of physical CPUs for that server. As a best practice, Oracle recommends using a minimum value of 2 for
18.104.22.168 Creating Database Services
Applications and users connect to the database using services.
Details about creating database services are not included in this guide.
8.1.5 Creating Oracle Database QoS Management Administrator Accounts
Before logging in to the Oracle Database QoS Management Dashboard (the Dashboard), you must create an Oracle Database QoS Management administrative user. The operating system user associated with this account must be a cluster administrator user to initially set this up.
The administrative user for the Oracle Database QoS Management server is referred to as the QoS Admin user. This user has access to all the features of the Oracle Database QoS Management server, including checking and changing the account password for the QoS Admin user. You can have multiple QoS Admin users.
- As the cluster administrator user, log in to the node that is hosting the Oracle Database QoS Management server. This can be determined by using the following command from the Oracle Grid Infrastructure home:
srvctl status qosmserver
- Stop the Oracle Database QoS Management server resource.
srvctl stop qosmserver
- Log on as a CRS Administrator user and enter the following command:
qosctl qosadmin -setpasswd qosadmin
After you enter this command, you are prompted to enter the password of the default QoS Admin user one or more times.
If you want to use a different user name, then you would enter the following command:
qosctl qosadmin -adduser username
In this example:
qosadminis the name of the default QoS Admin user.
usernameis the name of the QoS Admin user you are creating. You are prompted to enter a password for this user
- Restart the Oracle Database QoS Management server resource.
srvctl start qosmserver
8.1.6 Enabling Oracle Database QoS Management
If you have multiple databases running on the same cluster, you can specify which databases are managed by Oracle QoS Management.
You enable Oracle Database QoS Management in a hierarchical manner:
Measuring, monitoring, or managing the cluster
Measuring, monitoring, or managing individual databases that run on the cluster
To manage a database, all the databases that use the same user-defined server pool must be enabled for Oracle Database QoS Management if:
One or more Performance Classes in that user-defined server pool are not marked "Measure-Only" in the active policy
There are Performance Classes that include a service hosted by that database
If you do not enable all the databases in the same user-defined server pool for Oracle Database QoS Management and any of the above conditions exist, then a violation is signaled when you try to access the Dashboard for the database. If all of the Performance Classes in the user-defined server pool are in measure–only or monitor mode and none of the Performance Classes specify a hosted service, then there is no violation reported when accessing the Dashboard for the database.
Note:If you enable Oracle QoS Management to monitor or manage a container database (CDB), then all contained pluggable databases (PDBs) are monitored or managed as well. You cannot configure Oracle QoS Management to monitor or manage individual PDBs.
To enable Oracle QoS Management for your system, perform the following steps:
22.214.171.124 Enable Oracle QoS Management at the Database Level
- Log in to Oracle Enterprise Manager Cloud Control as the database administrator.
- From the Database targets page, select the database you want to modify.
- Select Availability, then Enable / Disable Quality of Service Management.
- Enter the Cluster and Database credentials, then click Login.
To complete this step, you must specify the login information for both a SYSDBA and a cluster administrator account.
The Enable/Disable QoS Management screen is displayed.
- You are prompted to enter a password for the APPQOSSYS user. Choose a password and enter it in the Password and Confirm Password fields, then click OK.
When you provide a password, the following actions take place:
The APPQOSSYS account, which enables the Oracle Database QoS Management server to connect to the database, is unlocked and the new password is set.
The credentials are written to an Oracle Wallet stored in the Oracle Cluster Registry to enable Oracle Database QoS Management to log in to the database.
APPQOS_PLANis set as the active Oracle Database Resource Manager plan for all actively managed databases, so that Oracle Database QoS Management can adjust CPU access for Performance Classes. The APPQOS_PLAN is not required for databases where all their Performance Classes are checked Measure-Only.
126.96.36.199 Create an Initial Policy Set
- On the Oracle Enterprise Manager Cloud Control All Targets page, select the cluster on which your cluster database that has Oracle Database QoS Management enabled runs.
- Select Administration, then Quality of Service Management, then Create Policy Set.
- Log in to the Oracle Database QoS Management Server using the QoS Management administrator password (default user name is
- On the first page of the Create Policy Set wizard, check the Manage box next to the server pools that represent your database. For example,
backoffice. Click Next.
- To get started with Oracle Database QoS Management, accept the defaults for your initial configuration and click Next on each page of the wizard to use the Default Policy Settings. On the fifth step, click Set Policy to set the DefaultPolicy as the Chosen Active Policy, then click Next.
On the last step of the Create Policy Set Wizard, click Submit Policy Set.
188.8.131.52 Enable Oracle QoS Management at the Cluster Level
- Using Oracle Enterprise Manager Cloud Control, on the All Targets page, select the cluster on which your cluster database that has Oracle Database QoS Management enabled runs.
- Select Administration, then Quality of Service Management, then Dashboard.
- Log in as the Oracle Database QoS Management user (for example,
- On the Dashboard page, the General section shows the current status of Oracle Database QoS Management. On a new system, the status is Disabled. Click the link Disabled next to the status to enable Oracle Database QoS Management for this cluster.
8.1.7 About Multi-CPU Binding on Solaris and Quality of Service Management
Using Multi-CPU Binding (MCB) and Oracle Database Quality of Service (QoS) Management together requires close communication between the system administrator and the database administrator (DBA).
Multi-CPU binding (MCB) is an Oracle Solaris projects resource management functionality that is used to bind a project to a specific set of CPUs, but not bind the CPUs exclusively. MCB allows other processes also to use these CPUs and allows overlapping of partitions. MCB is supported on Oracle Solaris 11.3. Control groups (CGroups) on Linux systems is another system administrator methods of managing server resources by allocating CPU and server resources to specific applications.
MCB has no impact on the use of Oracle Database Quality of Service (QoS) Management when used in measure and monitor mode. When you use Oracle Database Quality of Service (QoS) Management in management mode for a group of servers, there are four resource controls that Oracle QoS Management currently supports:
Consumer Group Mappings: CPU shares between competing workloads within a Non-CDB or PDB.
Container Database (CDB) Resource Plans: CPU Shares between competing PDBs within a CDB
Instance Caging: CPUs/Threads between co-hosted database instances
Server Pool Cardinality: number of servers in a server pool offering the database
MCB becomes a problem with regards to instance caging because it is possible for Oracle Database Quality of Service (QoS) Management to recommend a change in
CPU_COUNT that would not be honored by the operating system. If the recommended action is implemented in this situation, there would probably still be some improvement to the target workload because the donor database would lose a CPU. This would cause Resource Manager to not schedule as many parallel sessions which would help out when hard partitioning is not used. However, the projected performance improvement would be overstated.