3.1.00 enhancements and patches

Review the PATROL for Oracle Enterprise Database enhancements and patches for features that will benefit your organization and to understand changes that might impact your users. For the list of issues resolved in this release, see Known-and-corrected-issues.

3.1.21: Service pack 3

Support added for Adoptium Eclipse Temurin 23.x and jdk 23.x.

For the list of issues resolved in this release, see Known-and-corrected-issues.

3.1.20: Service pack 2

Disable standby database monitoring

Users can disable the standby database monitoring according to their requirements. By default, standby database monitoring is active. If the standby database monitoring is disabled, the primary database will be monitored based on its current role.

For more information, see Oracle Data Guard Database.

Learn about new metrics

The Instance (KOE_INSTANCE) monitor type includes a password expiry metric as an additional parameter.

3.1.11: Patch 4

For the list of issues resolved in this release, see Known and corrected issues.

3.1.10: Service pack 1

The PATROL for Oracle Enterprise Database 3.1.10 service pack 1 provides new features. This topic includes information about new features and instructions for downloading the service pack.

Ability to monitor the wait time in PATROL for Oracle Enterprise Database

You can enable the monitoring for the Wait Time attributes in the Oracle database. This helps you identify the queries that take more time to execute and the issues in your database even before they occur.
For more information, see Enabling monitoring of wait time attributes.

3.1.03: Patch 3

Vault support in Oracle Enterprise Database

Access your secret credentials from the vault for the monitoring of the Oracle Enterprise Database.

Currently, Oracle Enterprise Database supports only the CYBERARK vault.

For more information, see Enabling vault access.

3.1.02: Patch 2

Issue

A detailed description of the vulnerability (CVSS v3 rating: 9.8) can be found here: Spring4Shell Vulnerability .

Follow the BMC Security Advisory Note on BMC Community for continuous updates and details about this issue.

If you have any questions about the problem, contact BMC Support.

We recommend that you immediately apply the fix as described in this topic.

Resolution

This patch removes the spring-jdbc-4.3.7.RELEASE.jar file from the KM.

For BMC Helix Operations Management:

Create a deployable package by using the 3.1.02 version.
Deploy the patch on the PATROL Agent.

No changes are required to the existing monitor policies. If you want to create new monitor policies, use the 3.1.02 version.

For more information, see Creating deployable packages .

3.1.01: Patch 1

For the list of issues resolved in this release, see Known and corrected issues.

3.1.00 features

This section contains information about the features in the version 3.1.00 of PATROL for Oracle Enterprise Database. For information about the issue corrected in this release, see Known and corrected issues.

New attributes added to the Standby Health application class

The following parameters are added to the Standby-Health-KOE_INST_STANDBY application class:

Archive log apply gap
Archive log transfer gap

New configurations to connect to Data Guard instances

The following configurations are added to the Data Guard monitoring configurations:

A new configuration field is added to the Data Guard monitor type to connect to Data Guard as SYSDBA, SYSDG, or NON SYS user.
For Data Guard instances with different SID names or services, configure SID or service for each Data Guard individually.

For more information, see Oracle-Data-Guard-Database.

Ability to categorize tablespaces as large or very large

Configure tablespaces that you are monitoring in Data Guard, Standby, and RAC instances as large or very large based on their size by using the LargeTableSpaceSize and VeryLargeTableSpaceSize configuration variables. Tablespaces that have sizes more than the values defined in these configuration variables are monitored under one of the following application classes:

For more information, see Oracle-Data-Guard-Database, Oracle-Standalone-Database, and Oracle-Real-Application-Cluster-or-Real-Application-Cluster-One-Node-Database.