9.7.00 enhancements

The PATROL for Oracle Database 9.7.00 has been enhanced with the following changes and new features.

Oracle KM now supports RAC one node on Standby

PATROL for Oracle Database on Clustered (R1N) server with contingency instance supports both standby (DataGuard) and ReadOnly (Active Dataguard) modes.

PCM has full control over Oracle instances

Version 9.7.00 of PATROL for Oracle Database provides full control for PCM over ORACLE_RAC, ORACLE_DATAGUARD, ORACLE_ASM, ORACLE_STANDBY_DG.

Supports batch configuration for the RAC KM

PATROL for Oracle Database 9.7.00 now supports batch configuration for the RAC KM.

Copying the Oracle-related pconfig after discovery for ORACLE_R1N.km

PATROL for Oracle Database 9.7.00 allows ORACLE_R1N.km to proactively copy the Oracle-related pconfig after discovery is done instead of during failover process.

Reporting warning and alarm tablespaces when alarmed

Version 9.7.00 of PATROL for Oracle Database now provides FreeSpace annotation report to show both warning and alarm tablespaces when in alarm.

Supports Listeners Services Monitoring

Version 9.7.00 of PATROL for Oracle Database now supports Listeners Services Monitoring with an option to filter Services (Exclucde/Include, regular expression)

Compatibility of ORACLE_CAPACITY with Oracle 11g 

In version 9.7.00 of PATROL for Oracle Database, ORACLE_CAPACITY application class is compatible with Oracle 11g .

Excluding Disabled jobs while calculating FailedJobs

PATROL for Oracle Database now allows you to exclude Disabled Jobs while doing calculations for FailedJobs.

Usage of wildcards for monitoring listener INCLUSIONS or EXCLUSIONS

PATROL for Oracle Database now has a feature to use wildcards for monitoring listener INCLUSIONS or EXCLUSIONS.

Excluding certain FailedJobs from monitoring using Extended TableSpace Monitoring (ETSM)

The version 9.7.00 of PATROL for Oracle Database now has a feature to exclude certain FailedJobs from being monitored by using ETSM.

Menu command to sort the ETSM_REGULAR tablespaces into ETSM_LARGE and ETSM_VERY_LARGE containers

In version 9.7.00 of PATROL for Oracle Database, you can sort the ETSM regular tablespaces into ETSM_LARGE and ETSM_VERY_LARGE containers using a menu command.

Supports Regular Expression in User Monitoring

The version 9.7.00 of PATROL for Oracle Database now supports Regular Expression in User Monitoring so that users are automatically monitored when created and stopped monitoring, when deleted or excluded manually.

Monitoring is not required in the filesystems for the ETSM parameters

In version 9.7.00 of PATROL for Oracle Database, there is no need of having OS KM installed and configured in order to have filesystem parameters (ETSM params, availability and Capacity filesystem related params.

Monitoring the PATROL Database Monitoring user for its password expiry

Version 9.7.00 of PATROL for Oracle Database can monitor the PATROL Database Monitoring user for its password expiry.

Monitoring callout listener

Version 9.7.00 of PATROL for Oracle Database monitors the callout listener.

Monitoring Dataguard real time

Version 9.7.00 of the PATROL for Oracle Database monitors the Dataguard realtime.

Detecting the version of Oracle home and Oracle database after upgrading

The PATROL for Oracle Database detects the new oracle home and new oracle database versions after upgrading oracle database to newer version on Windows..

Supports ANYINST for all instances while monitoring

Version 9.7.00 of the PATROL for Oracle Database supports ANYINST for all instances being monitored to enable ETSM history storage in the agent configuration variable .

Monitoring the +ASM instance using only ASM 

The PATROL for Oracle Database now monitors the +ASM instance using ASM without requiring to be a member of DBA group.

Monitoring the RAC services in RAC environment

The PATROL for Oracle Database now also monitors RAC services in the RAC environment.

Support for SQL Custom Query

The PATROL for Oracle Database now supports SQL Custom queries, you can configure custom queries to be executed for monitoring different params.

Configuring Oracle through CMA without using the SYS password

User can use the CMA instance configuration without the need for SYS or any privileged user. PATROL monitoring user need to be created before configuration.

Monitoring Oracle 12c Management Listener

The PATROL for Oracle Database is now monitoring the management listener at the host were it actually runs.

Monitoring Oracle 12c Management Database

The PATROL for Oracle Database is now monitoring the management instance automatically on Oracle 12c cluster setup.

Added a pconfig variable with version of the Oracle km

A new Pconfig entry exist with the KM version.

Reducing duplication of events under availability

In case Instance status is in alarm, then the ConnectDB will not run. So no second event will be generated for the same alert.

Including full path and file name for all Oracle KM log monitoring for each alert

Now in the PATROL for Oracle Database, the user can be able to see at the annotation of alerts parameter, the full path and file name of the log that generated the alarm. The log file name will be in the annotation.

Parameter reports are available online

The PATROL parameter information is now available online in the Parameter Reference Database. This database contains reports in the CSV file format that you can download and use to help you gather default settings and plan for installation
and customization. You can download parameter reports for up to three versions of a product. To access the Parameter Reference Database, visit the Customer Support website at http://www.bmc.com/support and click Product Documentation > Parameter Reference Database.

New pconfig variables

These are the new pconfig variables added to the PATROL for Oracle Database 9.7.00:

pconfig variables

/ORACLE_USERS.inst.UsersRegEx

/ORACLE_USERS.__ANYINST__.UsersRegEx

/ORACLE_JOBS.ORACLE_SID.FailedJobsExcludedList

/Oracle_JOBS.__ANYINST__.FailedJobsIDsExcludedList

/Oracle_JOBS.ORACLE_SID.LongRunningMaxDuration
/Oracle_JOBS.__ANYINST__.LongRunningMaxDuration
/OracleConfig.NoEventRequired
/OracleConfig.NoSameJobTrigger

/ORACLE_ETSM.ORACLE_SID.VeryLargeTablespaceSize 

/ORACLE_ETSM.__ANYINST__.VeryLargeTablespaceSize 

/ORACLE_ETSM.ORACLE_SID.LargeTablespaceSize 

/ORACLE_ETSM.__ANYINST__.LargeTablespaceSize
/ORACLE_ETSM.__ANYINST__.StoreTbspHistory
/OraNetConfig.MGMNTListenerList..host

/OracleConfig.__ANYINST__.exclude_dba_undo_extents

Was this page helpful? Yes No Submitting... Thank you

Comments