Changes in This Release for Oracle Database Quality of Service Management

This chapter lists changes in Oracle Database Quality of Service Management:

Changes in Oracle Database QoS Management 12c Release 2 (12.2.0.1)

The following are changes in Oracle Database Quality of Service Management User's Guide for Oracle Database 12c Release 2 (12.2.0.1):

New Features for Oracle Database Quality of Service Management 12c Release 2 (12.2.0.1)

New qosmserver to Replace OC4J J2EE Container

In earlier releases, Oracle Database Quality of Service Management Server was deployed in an OC4J J2EE container. OC4J J2EE is not supported on the latest versions of Java, and had a greater resource footprint than needed by Oracle Database Quality of Service Management. A profiled version of Tomcat, known as the qosmserver, replaces the OC4J J2EE container.
Full Support for Administrator-Managed and Multitenant Oracle RAC Databases

In Oracle Database 12c release 1 (12.1), Oracle Database Quality of Service Management supported administrator-managed Oracle RAC and Oracle RAC One Node databases in its Measure-Only and Monitor modes. In this release, you can use Oracle Database Quality of Service Management support in Management mode for administrator-managed Oracle RAC databases and Multitenant Oracle RAC Databases. However, Oracle Database Quality of Service Management cannot expand or shrink the number of instances by changing the server pool size for administrator-managed databases because administrator-managed databases do not run in server pools. Oracle Enterprise Manager Cloud Control supports this new feature in the Oracle Database Quality of Service Management pages.

Changes in Oracle Database QoS Management 12c Release 1 (12.1.0.2)

The following are changes in Oracle Database Quality of Service Management User's Guide for Oracle Database 12c release 1 (12.1.0.2):

New Features

Authorized Automatic Actions

This features enables you to specify authorized automatic actions that Oracle Quality of Management Service can perform on a per resource and per policy basis. Specifying an authorized automatic action eliminates the requirement for a human response to a recommended action, and thus improves response time to react to a demand surge or node failure that puts SLAs at risk.

See "Automatically Implementing Recommendations for a Performance Policy"
Memory Guard Does Not Require Oracle Database QoS Management to be Active

With this release, Memory Guard is enabled by default independent of whether you use Oracle Database QoS Management. Memory Guard detects memory stress on a node and causes new sessions to be directed to other instances until the existing workload drains and frees memory. When free memory increases on the node, then services are enabled again to automatically accept new connections.

See Oracle Real Application Clusters Administration and Deployment Guide for more information about Memory Guard.
Performance-Related Alerts Generated When Running Oracle Database QoS Management in Monitoring Mode

In the Enterprise Manager Policy Editor, you can now set a non-zero performance objective (PO) for a performance class and also check the Measure-Only box. In earlier releases, the PO value was ignored if Measure-Only was selected, preventing administrators from measuring how well their workload performed against a performance objective.

In this release, if a positive value is specified as a PO and the Measure-Only box is checked, then Oracle Database QoS Management calculates the Performance Satisfaction Metrics (PSMs); if the PO is violated, then Oracle Database QoS Management identifies the resource and generates an alert.

See "Overview of Metrics" for more information.
Rank Order of Databases in an Active Oracle Database QoS Management Performance Policy Determine Oracle RAC Database Start Order

When a user created Oracle Database QoS Management policy is active, then the ranked order of the performance classes determines which Oracle RAC databases start first or request real-time LMS process slots. Using the Max(Ranks) across all Performance Classes within a database provides a consistent expression of the expressed business criticality of each database.
Support for Administrator-Managed Databases in Measure-Only Mode

Oracle Quality of Management Service supports the measuring and monitoring of database workloads for administrator-managed databases. This significantly enhances real-time monitoring of performance and bottleneck identification without needing a thorough understanding of database schema or database internals.

Changes in Oracle Database QoS Management 12c Release 1 (12.1.0.1)

The following are changes in Oracle Database Quality of Service Management User's Guide for Oracle Database 12c release 1 (12.1.0.1):

New Features

MemoryGuard

MemoryGuard protects a node from eviction or reboot due to memory stress, improving the high availability of the cluster impacted by a high workload load or login storm.
Support for Server Pool Category definitions and integration with CRS Policy Sets

Oracle Quality of Management Service supports the use of server pool categorization. This allows you to manage servers dynamically using server pools by identifying servers distinguished by particular attributes which is especially beneficial to clusters made up of heterogeneous node.

See Oracle Clusterware Administration and Deployment Guide for more information about server categories and server pools.
Support for Monitoring CDBs and PDBS

Oracle QoS Management can be used with container databases (CDBs) and pluggable databases (PDBs) in measure-only mode.

See Oracle Database Concepts and Oracle Database Administrator’s Guide for more information about container databases and pluggable databases.
Custom Resource Plans Supported in Measure-Only Mode

You can now use custom Database Resource Manager plans with Oracle Quality of Service Management if the database is set for Measure-Only mode.
Grid Management Repository is a mandatory requirement for Oracle Quality of Service Management

Oracle Quality of Service Management for Oracle Database 12c requires the Grid Management Repository to be configured when installing or upgrading to Oracle Clusterware 12c.

Deprecated Features

The -checkpasswd option of the QOSCTL utility

Desupported Features

Some features previously described in this document are desupported in Oracle Database 12c release 1. See Oracle Database Upgrade Guide for a list of desupported features.

Other Changes

Oracle Enterprise Manager Database Control is not included in this release

In previous Oracle Database releases, Oracle Enterprise Manager Database Control was the primary database management tool described in this manual. Now, this book describes Oracle Enterprise Manager Cloud Control 12c as the primary interface.