ca unified infrastructure...

Probe Guide for Oracle Database Monitor

oracle v4.7 series

CA Unified Infrastructure Management

Copyright Notice

This online help system (the "System") is for your informational purposes only and is subject to change or withdrawal by CA at any time.

This System may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This System is confidential and proprietary information of CA and protected by the copyright laws of the United States and international treaties. This System may not be disclosed by you or used for any purpose other than as may be permitted in a separate agreement between you and CA governing your use of the CA software to which the System relates (the “CA Software”). Such agreement is not modified in any way by the terms of this notice.

Notwithstanding the foregoing, if you are a licensed user of the CA Software you may make one copy of the System for internal use by you and your employees, provided that all CA copyright notices and legends are affixed to the reproduced copy.

The right to make a copy of the System is limited to the period during which the license for the CA Software remains in full force and effect. Should the license terminate for any reason, it shall be your responsibility to certify in writing to CA that all copies and partial copies of the System have been destroyed.

TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS SYSTEM “AS IS” WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS SYSTEM, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE.

The manufacturer of this System is CA.

Provided with “Restricted Rights.” Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or their successors.

Copyright © 2014 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

Legal information on third-party and public domain software used in this product is documented in the Third-Party Licenses and Terms of Use (http://docs.nimsoft.com/prodhelp/en_US/Library/Legal.html).

http://docs.nimsoft.com/prodhelp/en_US/Library/Legal.html

Contact CA

Contact CA Support

For your convenience, CA Technologies provides one site where you can access the information that you need for your Home Office, Small Business, and Enterprise CA Technologies products. At http://ca.com/support, you can access the following resources:

■ Online and telephone contact information for technical assistance and customer services

■ Information about user communities and forums

■ Product and documentation downloads

■ CA Support policies and guidelines

■ Other helpful resources appropriate for your product

Providing Feedback about Product Documentation

Send comments or questions about CA Technologies product documentation to [email protected].

To provide feedback about general CA Technologies product documentation, complete our short customer survey which is available on the support website at http://ca.com/docs.

http://www.ca.com/support

mailto:[email protected]

http://ca.com/docs

Contents 5

Contents

Chapter 1: Overview 9

About This Guide ........................................................................................................................................................ 12

Related Documentation ............................................................................................................................................. 12

Preconfiguration Requirements ................................................................................................................................. 12

Prerequisites ....................................................................................................................................................... 12

Supported Platforms ........................................................................................................................................... 13

Probe Defaults..................................................................................................................................................... 13

Supported Oracle Versions and Clients ...................................................................................................................... 13

Installation notes ........................................................................................................................................................ 13

Chapter 2: Configuration Details 15

oracle Node ................................................................................................................................................................ 16

Checkpoints Node ............................................................................................................................................... 18

Connection-<Connection Name> Node .............................................................................................................. 20

RAC Common Checkpoints .................................................................................................................................. 25

RAC-<Specific Checkpoints> Node ...................................................................................................................... 26

Configure a Node ....................................................................................................................................................... 28

Create New Connection ............................................................................................................................................. 28

Delete Connection ...................................................................................................................................................... 28

Add Checkpoint .......................................................................................................................................................... 29

Delete Checkpoint ...................................................................................................................................................... 29

How to Configure Alarm Thresholds .......................................................................................................................... 29

Manage Profiles ......................................................................................................................................................... 30

Delete Profile.............................................................................................................................................................. 30

Add Exclude Pattern ................................................................................................................................................... 31

Delete Exclude Pattern ............................................................................................................................................... 31

Add Profile Checkpoint ............................................................................................................................................... 32

Delete Profile Checkpoint .......................................................................................................................................... 32

Monitor RAC Connection ........................................................................................................................................... 32

Chapter 3: QoS Threshold Metrics 33

oracle QoS Metrics ..................................................................................................................................................... 33

oracle Alert Metrics Default Settings ......................................................................................................................... 40

6 Probe Guide for Oracle Database Monitor

Chapter 4: Known Issues 49

Documentation Changes 7

Documentation Changes

This table describes the version history for this document.

Version Date What's New?

4.7 October 2014 ■ Updated the Overview topic.

4.7 September 2014

■ Updated the document for Oracle 12c support.

■ Removed support for the Oracle versions 9i and 10g.

4.6 March 2014 ■ Updated the document for Oracle RAC support.

■ Updated the oracle QoS Metrics and oracle Alert Metrics Default Settings topics.

4.5 December 2013 Documentation on the initial web-based GUI version of the Oracle Database Monitor probe. (Previous versions of this probe are configured using Infrastructure Manager).


Chapter 1: Overview

About This Guide


The Oracle Database Monitoring (oracle) probe allows you to monitor your Oracle databases so you can detect, diagnose, and resolve Oracle performance issues as soon as they occur. This information is presented to a database administrator as reports, and also as alarms when database performance crosses a specified threshold.

You can set up multiple configurable monitoring profiles to extract vital information about your database servers at specified intervals. Database administrators can use this information to tune and optimize database performance, and perform capacity planning.

Note: The oracle probe also provides monitoring support for Real Application Cluster (RAC).

The following information can be monitored on either local or remote database instances:

■ Database uptime

■ Tablespace growth

■ Database growth

■ Tablespace status

■ Index status

■ Data-file status

■ Rollback segment status

■ Fragmented segments

■ The extents that can't extend

■ The data dictionary cache-hit ratio

■ The data buffer cache-hit ratio

■ The Redo copy latch-hit ratio

■ The library cache-hit ratio

■ The sort-hit ratio

■ PGA resource consumption (monitor memory consumption of Oracle users)

■ The rollback segment contention

■ The number of invalid objects

■ The number of chained rows

■ The number of users currently logged onto the server

■ The MTS response time

■ The number of MTS waits

■ The enqueue resources

About This Guide


■ The UGA memory usage

■ User locks and locked users

■ Lock waits event time

■ The user buffer cache-hit ratio

■ System waits and user waits

■ Datafile i/o

■ System statistics

■ Global cache service utilization for RAC

■ Global cache fusion ratio for RAC

■ Global cache lock get time for RAC

■ Global cache lock conversion timeouts for RAC

■ Global cache average lock get time for RAC

■ Global cache corrupt blocks count for RAC

■ Global cache lost blocks count for RAC

■ Number of Long running queries

■ Tablespace size

■ Database size

■ Resource utilization %

■ Dataguard status

■ Dataguard gap

■ Dataguard timegap

■ Tablespace temp free

■ Active users

■ Flash recovery area memory free

■ Active connection ratio

This section contains the following topics:

About This Guide (see page 12) Related Documentation (see page 12) Preconfiguration Requirements (see page 12) Supported Oracle Versions and Clients (see page 13) Installation notes (see page 13)

About This Guide


About This Guide

This guide provides information about how the oracle probe is configured for CA UIM. This guide contains the following information:

■ Overview of the Oracle Database Monitor probe and related documentation for previous probe versions.

■ Configuration details of the probe.

■ Field information and common procedures required to configure the probe.

Important! Description for intuitive GUI fields is not included in the document.

Related Documentation Related Documentation

Documentation for other versions of the oracle probe

The Release Notes for the oracle probe

User documentation for the Admin Console

Monitor Metrics Reference Information for CA Unified Infrastructure Management Probes (http://docs.nimsoft.com/prodhelp/en_US/Probes/ProbeReference/index.htm)

Preconfiguration Requirements

This section contains the preconfiguration requirements for the Oracle Database Monitor probe.

Prerequisites

This section contains the prerequisites for the Oracle Database Monitor probe:

■ Set the ORACLE_HOME path in the environment variables. For example, C:\app\Username\product\11.2.0\client1.

Important! Setting the ORACLE_HOME path is mandatory for getting the correct Device ID, routing the QoS messages/ alarms to the correct device, and viewing data on UMP.

■ Check that the PATH variable contains oracle path up to the oracle bin folder. For example, C:\app\Username\product\11.2.0\bin\client1\bin.

■ Navigate to Run > Services.msc after setting the ORACLE_HOME and PATH and restart the CA UIM Robot Watcher service.

http://docs.nimsoft.com/prodhelp/en_US/Probes/AdminConsole/oracle/ReleaseNotes/index.htm

http://docs.nimsoft.com/prodhelp/en_US/AdminConsole/6.5/index.htm

http://docs.nimsoft.com/prodhelp/en_US/Probes/ProbeReference/index.htm

Supported Oracle Versions and Clients


Supported Platforms

Refer to the CA UIM Compatibility Support Matrix for the latest information about supported platforms. See also the Support Matrix for CA UIM Probes for more information about the Oracle Database Monitor probe.

Probe Defaults

At the time of deploying a probe, some default configuration will be deployed. These probe defaults could be Alarms, QoS, Profiles and so on which save time to configure the default settings. When you create a connection and a profile, the default checkpoints are automatically added in that profile and the alarms and QoS are enabled for some checkpoints.

Supported Oracle Versions and Clients

The following matrix summarizes client and server combinations that are supported by the Oracle Database Monitor probe.

Server Version

Client Version 12.1.0 11.2.0 11.1.0

12.1.0 Yes Yes Yes

11.2.0 Yes Yes Yes

11.1.0 Yes Yes Yes

Key

Yes Supported

No Not Supported

Installation notes

Add the Oracle libraries in the system PATH environment variable and configure the Oracle client appropriately before installing the Oracle monitoring probe.

http://support.nimsoft.com/downloads/doc/NMSCompatibility_SupportMatrix_current.pdf

http://support.nimsoft.com/downloads/doc/Platform_Support_Availability_current.pdf

Installation notes


Follow these steps for deploying the Oracle monitoring probe:

1. Obtain the latest version of the oracle.zip package from Internet Updates.

2. Install oracle.zip on the computer that has the Oracle client (drag from the Nimbus Archive).

3. Configure the oracle probe according to your requirements.

4. Update the following environment variables by using the controller GUI or by editing the nimbus script, which is at /etc/init.d.

5. Restart the robot after updating the nimbus script.

Windows platform:

1. Set the ORACLE_HOME path to the directory where the client is installed. For example, C:\oracle\product\11.2.0\client_1.

UNIX or Linux platform:

1. Set the ORACLE_HOME path to the directory where the client is installed. For example, /u01/app/oracle/product/11.2.0/client_1.

2. Set the ORACLE_SID path to the service identifier name that you configured by using the Oracle client.

3. Set the LD_LIBRARY_PATH path to the Oracle library directory. For example, /u01/app/oracle/product/11.2.0/client_1/lib.

Important: The Current Enforcing Mode must be Permissive on Linux Platform.

Note: Security-Enhanced Linux (SELinux) is a mandatory access control (MAC) security mechanism implemented in the Linux kernel. SELinux has three basic modes of operation: Enforcing, Permissive and Disabled. In Permissive mode, SELinux is enabled but does not enforces the security policy, only warn and log actions.

Follow these steps for setting the Current Enforcing Mode to Permissive:

1. Open SELinux Management.

The SELinux Administration window appears.

Note: The SELinux mode can be viewed and changed using the SELinux Management.

2. In the Current Enforcing Mode list, click Permissive.

3. Close the SELinux Administration window.


Chapter 2: Configuration Details

The Oracle Database Monitor probe is configured by defining connections and profiles for monitoring Oracle instances. Each monitoring profile runs in its own thread, which keeps the monitoring profile in isolation.

Important: The Oracle client or server is mandatory for oracle probe to work.


oracle Node (see page 16) Configure a Node (see page 28) Create New Connection (see page 28) Delete Connection (see page 28) Add Checkpoint (see page 29) Delete Checkpoint (see page 29) How to Configure Alarm Thresholds (see page 29) Manage Profiles (see page 30) Delete Profile (see page 30) Add Exclude Pattern (see page 31) Delete Exclude Pattern (see page 31) Add Profile Checkpoint (see page 32) Delete Profile Checkpoint (see page 32) Monitor RAC Connection (see page 32)

oracle Node


oracle Node

The oracle node contains the configuration details specific to the Oracle Database Monitor probe. This node lets you view the probe information and configure the setup properties of the Oracle Database Monitor probe. You can also view a list of all alarm messages available in the Oracle Database Monitor probe.

Navigation: oracle

Set or modify the following values as required:

oracle > Probe Information

This section provides information about the probe name, probe version, start time of the probe, and the probe vendor.

oracle > General Config

This section lets you configure the setup properties of the Oracle Database Monitor probe.

■ Clear Alarm on Restart: clears all alarms when the Oracle Database Monitor probe is restarted.

Default: Selected

■ Alarm Severity Filter: specifies a filter on severity level of an event for considering an event as an alarm. Events matching the selected severity level and higher, generates alarms. If major is selected, then only the messages with severity level as major and above are considered as alarms.

Default: information

■ Log Size: sets the size of the log file where the internal log messages of the probe are saved.

Default: 1000

■ Log Level: specifies the detail level of the log file.

Default: 0 - Normal

■ QoS V2 Compatibility: selects the inserted data in the QoS database.

Default: Not selected

oracle > Message pool

This section displays a list of alarm messages available in the Oracle Database Monitor probe.

■ Text: identifies the message text.

■ i18n_Token: identifies the predefined alarms fetched from the database.

Note: This section is read-only.

oracle > Options icon > Create New Connection

oracle Node


This section lets you create various connections corresponding to instances that the Oracle Database Monitor probe monitors. You can specify the user ID, password, and service name you want to use to connect to the instance.

■ User ID: defines the user ID with authorization for reading views.

■ Service Name: specifies the service name defined in the tnsnames.ora file.

■ Retry Attempts: specifies the number of attempts the Oracle Database Monitor probe repeats for a connection when there is a failure.

Default: 0

■ Retry delay: specifies the time the Oracle Database Monitor probe waits between two connection attempts.

Default: 0

■ Retry Delay Unit: defines the unit used for measuring the value of retry delay.

Default: sec

■ Skip Privilege Check: lets you create custom checkpoints for users who do not have DBA and the Select Catalog Role privileges.


Note: On selecting this check box, Version and Instance fields are enabled.

■ Instance: specifies the instance name where the connection is established.

■ Is RAC: activates the RAC (Real Application Cluster) connection.

Note: On selecting Is RAC, you are able to create a RAC connection.

oracle Node


Checkpoints Node

The Checkpoints node enables you to create a checkpoint for monitoring the Oracle database. The default checkpoints are visible whereas custom checkpoints can be created.

Navigation: oracle > Checkpoints


Checkpoints > Options icon > Create New Checkpoint

This section lets you create a checkpoint.

■ Connection Name: specifies the name of the connection.

■ Query File: defines the query file name where you want the query to be stored.

■ Query: defines the query for creating the checkpoint.

■ Interval Modus: subtracts the variable value from the value generated at the end of the interval.


<Checkpoints Name> Node

The checkpoint name node is used to configure Checkpoint config, Message Variable, General Config, Threshold, Row Identifier, Custom Checkpoints and Advance Database Settings.

Note: This node is called checkpoint name in the document and is user-configurable.

Navigation: oracle > Checkpoints > checkpoint name


checkpoint name > General Config

This section lets you configure the general setup parameters of the checkpoint of Oracle Database Monitor probe.

■ Check Interval: specifies the default value of the check interval in the checkpoint. This value bypasses the interval given in the profile.

■ Check Interval unit: specifies the check interval unit.

■ Samples: specifies the number of samples for calculating the average value.

Default: 1

■ Clear Severity: specifies the severity level of the clear message.

Default: clear

■ Clear Message: specifies the clear message name.

oracle Node


■ Use Exclude: lets you define objects that you do not want to monitor on the checkpoint.


checkpoint name > Exclude

This section lets you add an exclude pattern, which lets you define objects that you do not want to monitor on the checkpoint.

■ Exclude Pattern: lets you define a regular expression for executing the exclude functionality works.

checkpoint name > Checkpoint Config

This section lets you configure a checkpoint.

■ Checked Value: specifies the column name for which the reporting of alarms has to be done.

■ Condition: specifies the operator for evaluating threshold values.

■ Query File: defines the query file name.

■ Query: defines the query for creating the checkpoint.

■ Interval Modus: lets the Oracle Database Monitor probe subtract the variable value from the value that is generated at the end of the interval.

Note: This section appears only in custom checkpoints.

checkpoint name > Row Identifier

This section lets you pick the rows as variables to set an alarm message and suppression key. If the query returns more than one row, the Oracle Database Monitor probe needs a unique identification for each row.

Note: This section appears only in custom checkpoints.

checkpoint name > Message Variable

This section lets you pick the columns as variables that are used in creating QoS.

Note: This section appears only for the custom checkpoints.

■ Data Type: specifies the data type of the variable of the new alarm.

■ Column Use: specifies the column use of the variable.

oracle Node


Monitors Node

The Monitors node lets you view and define the QoS and thresholds for monitoring the checkpoint.

Navigation: oracle > Checkpoints > checkpoint name > Monitors


Monitors > Quality of Service

This section lets you configure the QoS for the checkpoint.

■ Unit: defines the unit of the QoS.

■ Abbreviation: defines the abbreviation for the QoS.

■ Max Value: specifies the max value for the QoS.

■ Object: defines the object for the QoS.

Note: The Object field appears only if there is a message variable defined with data type as character and column use as row key.

■ Metric: defines the column that is fetched from the query.

Note: The values are displayed in the Metric field only if there is a message variable defined with data type as numeric.

Monitors > Threshold

This section lets you configure threshold values for a checkpoint.

■ Threshold Object Name: defines the name of the threshold object.

■ Threshold Value: defines the threshold values of the column that was specified in the Checked Value field.

■ Severity: specifies the threshold breach level.

■ Message: defines the message name used.

■ Message Text: specifies the content of the message issued.

Note: The content of the message is displayed only when the message is saved.

Connection-<Connection Name> Node

The Connection-connection name node displays properties of the connection setup. This node also lets you delete the connection setup.

Note: This node is called Connection-connection name in the document as it is user-configurable.

oracle Node


Navigation: oracle > Connection-connection name


Connection-connection name > Connection Setup

This section lets you display the properties of the connection setup.

Note: The field descriptions are the same as described in Create New Connection section in the oracle node.

<Connection Name> Node

The connection name node lets you view and modify the connection setup properties.

Note: This node is called connection name in the document as it is user-configurable.

Navigation: oracle > Connection-connection name > connection name


connection name > Connection Setup

This section lets you modify the connection setup properties.

Note: The field descriptions are the same as described in the Create New Connection section in the oracle node.

connection name > Options icon > Create new profile

This section lets you create a profile, which enables to execute the checkpoints for a specific connection.

<Profile Name> Node

The profile name node lets you modify the profile parameters.

Note: This node is called profile name in the document as it is user-configurable.

Navigation: oracle > Connection-connection name > profile name


profile name > Profile

This section lets you modify the parameters of the profile.

■ Heartbeat: specifies the interval at which all profile checkpoints schedules are tested and an eventual checkpoint execution is triggered.

Note: This number is a common denominator to all used check interval values. The higher the value of heartbeat, the lower is the profile overhead.

Default: 5

oracle Node


■ Heartbeat Unit: specifies the heartbeat unit.

Default: sec

■ Connection: specifies the connection used in the profile.

■ Check Interval: specifies the check interval default value.

Default: For a sample profile, the value is 15 and for a new the profile value is 5.

■ Check Interval Unit: specifies the unit for the check interval.

Default: sec

■ Clear Message: specifies the message for the timeout clear alarm.

Default: p_timeout_1

■ SQL Timeout: specifies if the query reaches the SQL timeout, the checkpoint processing is terminated. The next checkpoint is started and an alarm is issued.

Default: 60

Note: On every check interval the SQL timeout alert is first cleared on the basis of query for a particular checkpoint.The SQL timeout alert is thrown again if the issue remains.

■ SQL Timeout Unit: specifies the unit for the SQL Timeout.

Default: sec

■ SQL Timeout Message: specifies the message name for the profile timeout alarm.

Default: Sql_timeout_1

■ Profile Timeout: defines the maximum processing time for all checkpoints in the profile.

Default: 120

■ Profile Timeout Unit: specifies the profile timeout unit.

Default: sec

■ Profile Timeout Message: specifies the profile timeout message.

Default: P_timeout_1

■ Timeout Severity: defines the severity for timeout messages.

Default: major

■ Alarm Source: defines the custom alarm source.

■ Connection Failure Message: specifies the message to be displayed when there are some connection-related issues.

Default: Connect_failure_1

oracle Node


oracle RAC Monitoring

The Oracle RAC lets multiple computers run the Oracle RDBMS software simultaneously while accessing a single database, thus providing clustering. The Oracle Database Monitor probe supports the monitoring of RAC.

This section contains the information on how you can monitor the Oracle RAC with the help of checkpoints.

Note: From NMS 7.5 and PPM version 2.31 onwards, RAC is configured only through the Admin Console GUI.

<Connection Name> Node

The connection name node lets you view and modify the setup properties of an RAC connection.

Note: This node is called connection name in the document and is not user-configurable.

Navigation: oracle > Connection-connection name > connection name


RAC-connection name > Connection Setup

This section lets you modify the setup properties of an RAC connection.

Note: The field descriptions are the same as described in Create New Connection section in the oracle node.

Important! Select Is RAC in the Create New Connection dialog if you want to perform Oracle RAC monitoring. Once an RAC connection is formed then, it cannot be converted to a non-RAC connection.

connection name > Options icon > Create new profile

This section lets you create an RAC profile, which is enabled to execute the checkpoints for a specific RAC connection.

On profile creation, all the active/running nodes are automatically added under the profile. One of the nodes is displayed as primary. This node denotes that the data for an RAC common checkpoint is routed to this node when viewed from UMP. Even when the node is down, the data is still routed to this node (to avoid any data loss).

Note: When you bind a profile to the RAC connection, all the RAC common and node-specific checkpoints are automatically loaded in the RAC profile. The common checkpoints are added directly under profile and the node-specific checkpoints are added directly under the nodes.

oracle Node


<Profile Name> Node

The profile name node lets you modify the profile parameters. You can add profile checkpoints that are made static as per profile settings.

Note: This node is called profile name in the document and is user-configurable. On creating a normal profile, the default checkpoints automatically get added in the profile.

Navigation: oracle > Connection-connection name > connection name > profile name


profile name > Profile

This section lets you modify the profile parameters.

Note: The field descriptions are the same as described in the Profile section in the profile name node.

<Checkpoints Name> Node

The checkpoint name node is used to configure general configuration parameters of the Oracle Database Monitor probe.

Note: This node is called checkpoint name in the document and is not user-configurable.

Navigation: oracle > Connection-connection name > connection name > profile name > checkpoints name


checkpoints name > General Config

This section lets you configure the general setup parameters of the checkpoints of Oracle Database Monitor probe.

Note: The field descriptions are the same as described in the General Config section in the checkpoints name node.


This section lets you add an exclude pattern, which lets you define objects that you do not want to monitor on the checkpoint.

■ Exclude Pattern: defines a regular expression for executing the exclude functionality works. Click Test in the Action drop-down list. The Response dialog opens displaying the objects that are excluded.

Note: The excluded objects have their Exclude value set to 1.

Monitors Node

The Monitors node lets you view and define the QoS and thresholds for monitoring the checkpoint.

oracle Node


Navigation: oracle > Connection-connection name > connection name > profile name > checkpoints name > Monitors



This section lets you configure the QoS for the checkpoint.

Note: The field descriptions are the same as described in Quality of Service section in the Monitors node.


This section lets you configure threshold values for a checkpoint.

Note: The field descriptions are the same as described in Threshold section in the Monitors node.

RAC Common Checkpoints

The RAC Common Checkpoints node enables you to view the details of the common checkpoints.

Note: This node is called RAC common checkpoints in the document and is not user-configurable. The RAC common and node-specific checkpoints are displayed in alphabetical order in the navigation pane of the Oracle Database Monitor probe GUI. The nodes are also displayed in alphabetical order.

Navigation: oracle > RAC common checkpoints

RAC-<Common Checkpoints Name> Node

The RAC common checkpoint name node is used to configure general configuration of the RAC common checkpoints.

Note: This node is called RAC common checkpoint name in the document and is user-configurable.

Navigation: oracle > RAC common checkpoint > RAC common checkpoint name


checkpoint name > General Config

This section lets you configure the general setup parameters of the RAC common checkpoint of the Oracle Database Monitor probe.


oracle Node



This section lets you add an exclude pattern, which lets you define objects that you do not want to monitor on the RAC common checkpoint.

■ Exclude Pattern: lets you define a regular expression for executing the exclude functionality.

Monitors Node

The Monitors node lets you view and define the QoS and thresholds for monitoring an RAC common checkpoint.

Navigation: oracle > RAC common checkpoint > RAC common checkpoint name > Monitors



This section lets you configure the QoS for an RAC common checkpoint.

Note: The field descriptions are the same as described in the Quality of Service section in the Monitors node.


This section lets you configure threshold values for am RAC common checkpoint.

Note: The field descriptions are the same as described in the Threshold section in the Monitors node.

RAC-<Specific Checkpoints> Node

The RAC-specific checkpoints node enables you to view the details of the node-specific checkpoints.

Note: This node is called RAC-specific checkpoints in the document and is not user-configurable.

Navigation: oracle > RAC-specific checkpoints

oracle Node


RAC-<Specific Checkpoints Name> Node

The RAC-specific checkpoint name node is used to configure general configuration of the RAC-specific checkpoints.

Note: This node is called RAC-specific checkpoint name in the document and is not user-configurable.

Navigation: oracle > RAC-specific checkpoints > RAC-specifc checkpoint name


RAC-specific checkpoint name > General Config

This section lets you configure the general setup parameters of the RAC-specific checkpoint of the Oracle Database Monitor probe.


Monitors Node

The Monitors node lets you view and define the QoS and thresholds for monitoring an RAC-specific checkpoint.

Navigation: oracle > RAC-common checkpoint > RAC-common checkpoint name > Monitors



This section lets you configure the QoS for an RAC-specific checkpoint.

Note: The field descriptions are the same as described in the Quality of Service section in the Monitors node.


This section lets you configure threshold values for an RAC-specific checkpoint.

Note: The field descriptions are the same as described in the Threshold section in the Monitors node.

Configure a Node


Configure a Node

This procedure provides the information to configure a section within a node.

Each section within a node enables you to configure the properties of the Oracle Database Monitor probe for monitoring the response of user-defined queries.

Follow these steps:

1. Select the appropriate navigation path.

2. Update the field information and click Save.

The specified section of the Oracle Database Monitor probe is configured. You can now define connections and profiles for the monitored instance.

Create New Connection

You can configure the probe to create a connection.

Follow these steps:

1. Click the Options icon next to the oracle node in the navigation pane.

2. Click Create new connection.

3. Update the field information and click Submit.

The new connection is saved under the Connections node in the navigation pane.

Delete Connection

You can delete a database connection when you do not want the probe to monitor it.

Follow these steps:

1. Click the Options icon beside the Connection-connection name node that you want to delete.

2. Click Delete connection and then click Save.

The connection is deleted.

Note: You can delete a profile at the profile level also.

Add Checkpoint


Add Checkpoint

You can define a custom checkpoint for monitoring the Oracle database instance. However, you can delete both default and custom checkpoints at individual profile level.

Follow these steps:

1. Click the Options icon next to the Checkpoints node in the navigation pane.

2. Click Add New Checkpoint.


The new checkpoint is saved under the Checkpoints node in the navigation pane.

Note: Ensure that you define custom checkpoints with unique targets for the object field in the QoS section so that separate nodes are created on USM. Otherwise, the data on USM will be reflected under one node. Hence, there could be significant loss of data.

Delete Checkpoint

You can delete only custom checkpoints from the Oracle Database Monitor probe.

Follow these steps:

1. Click the Options icon next to the checkpoint name node that you want to delete.

2. Click Delete Checkpoint.

The selected checkpoint is deleted.

How to Configure Alarm Thresholds

Some Quality of Service measurement probes allow you to set different types of alarm thresholds. These threshold options allow you to more broadly control when alarm messages are sent for each QoS probe.

For more information about the different alarm thresholds and their configuration requirements, refer to the General Probe Configuration section of the Admin Console Help.

Manage Profiles


Manage Profiles

You can configure the Oracle Database Monitor probe to create a profile on various checkpoints for monitoring the Oracle Server connection. You can then configure the profile to send the QoS messages and generate alarms on response time.

Follow these steps:

1. Click the Options icon next to the connection name node in the navigation pane.

2. Click the Create new profile option.


The profile is saved.

Delete Profile

You can delete an existing profile when you no longer want the Oracle Database Monitor probe to monitor.

Follow these steps:

1. Click the Options icon beside the profile name node that you want to delete.

2. Click Delete Profile and then click Save.

The profile is deleted.

Add Exclude Pattern


Add Exclude Pattern

You can add an exclude pattern in the Oracle Database Monitor probe. The exclude pattern allows you to define objects that you do not want to monitor on the checkpoint.

Follow these steps:

1. Click the checkpoints name node in the navigation pane.

2. Select Use Exclude in the General Config section.

3. Go to the Exclude section and then click New.

4. Enter a regular expression in the Exclude Pattern field.

5. Click Test in the Action drop-down list.

Response dialog opens displaying the objects that are excluded. The excluded objects have their Exclude value set to 1.

Note: This test is possible only for running active profiles and checkpoints that you do not want to monitor on the checkpoint.

6. Click Save.

The exclude pattern is added.

Delete Exclude Pattern

You can delete an exclude pattern in the Oracle Database Monitor probe when you no longer need it.

Follow these steps:

1. Click the checkpoints name node in the navigation pane.

2. Go to the Exclude section and then select the exclude pattern that you want to delete.

3. Click Delete.

The exclude pattern is deleted.

Add Profile Checkpoint


Add Profile Checkpoint

The Add Profile Checkpoint option lets you add a checkpoint to the monitoring profile of the Oracle Database Monitor probe.

Follow these steps:

1. Click the Options icon beside the profile name node for which you want to add a checkpoint.

2. Click Add profile checkpoints.

3. Select the checkpoints to be added and click Submit.

The profile checkpoint is added.

Delete Profile Checkpoint

You can delete a profile checkpoint in the Oracle Database Monitor probe when you no longer need it.

Follow these steps:

1. Click the Options icon beside the checkpoint you want to delete.

2. Click Delete checkpoint and then click Save.

The selected profile checkpoint is deleted.

Monitor RAC Connection

You can monitor a RAC profile or connection using the Oracle Database Monitor probe.

Follow these steps:

1. Create a RAC connection by selecting the Is RAC option in the Create New Connection dialog. For more information, see the Create New Connection topic.

2. Create a profile corresponding to the RAC connection. For more information, see the Manage Profiles topic.

The nodes are auto-discovered and are displayed in the alphabetical order. All the RAC-specific checkpoints appear automatically under the nodes. All the common checkpoints fall under the profile at the same level as nodes.


Chapter 3: QoS Threshold Metrics

Many CA UIM probes ship with the default QoS threshold values set. The default threshold values give an idea of the type of values to enter in the metrics fields. To help in tuning thresholds and reducing false-positive alarms, this section describes the QoS metrics and provides the default QoS thresholds.


oracle QoS Metrics (see page 33) oracle Alert Metrics Default Settings (see page 40)

oracle QoS Metrics

This section contains the QoS Metrics for the oracle probe.

QoS Name Units Description

QOS_ORACLE_active_connection_ratio pct Calculated as: (active/total) * 100.

Monitors % of active connections to total allowed connections.

QOS_ORACLE_active_users count Checks for currently active Oracle users

QOS_ORACLE_buf_cachehit_ratio pct Calculated as:

(logical-reads - physical-reads)*100 / physical-reads

QOS_ORACLE_buf_cachehit_ratio_users pct Same as buf_cachehit_ratio, only per user. It helps to find a poor query or application.

QOS_ORACLE_check_dbalive State Connects to an instance. If the connection cannot be established, an alert is generated.

Note: The checkpoint cannot be deactivated.

QOS_ORACLE_database_size MB Monitors space size (in bytes) for each database, log, and data files.

QOS_ORACLE_datafile_status State Monitors the status of the data files.

QOS_ORACLE_dataguard_gap Archivefiles Monitors Dataguard Instance Gap

QOS_ORACLE_dataguard_status State Monitors Dataguard Instance Status

QOS_ORACLE_dataguard_timegap Seconds Monitors Dataguard Instance Timegap

oracle QoS Metrics



QOS_ORACLE_dbfile_io Percent Calculated as:

(Physical-reads / logical-reads) * 100

(Physical-writes / logical-writes) * 100

Helps to identify database files with higher I/O contention.

QOS_ORACLE_dict_cachehit_ratio Percent Calculated as:

(hits - misses) * 100 / hits

Measures the number of times that Oracle meta data are found in memory.

QOS_ORACLE_enqueue_timeouts Timeouts Measures the number of locks (acquired and converted) that did not get released within specified time.

QOS_ORACLE_extents Extents Reports tables that have more extents as threshold.

QOS_ORACLE_flash_recovery_area_memory_free

Bytes Monitors the available memory in the flash recovery area.

QOS_ORACLE_Gc_av_lock_get_time Milliseconds Measures the average time interval to release a global lock.

QOS_ORACLE_gc_blocks_corrupt Blocks Measures the number of blocks corrupted during transfer.

QOS_ORACLE_gc_blocks_lost Blocks Measures the number of blocks lost during transfer.

QOS_ORACLE_gc_convert_timeouts Timeouts Measures the number of time-outs of the lock converts in a global cache.

QOS_ORACLE_gc_cr_timeouts Timeouts Measures the number of times the process request for a consistent read block has timed out.

QOS_ORACLE_gc_fusion_wrt_rto Percent Calculated as:

Fusion writes / physical writes

A high number indicates insufficient cache size (SGA) or low checkpoint frequency.

QOS_ORACLE_gc_service_util Percent Calculated as:

Global cache service requests / logical reads

Measures global cache utilization.

oracle QoS Metrics



QOS_ORACLE_lib_cachehit_ratio Percent Calculated as:

(hits – misses)*100 / hits

Measures the percentage of times that the object meta data have been found in memory.

This value can be lower when a new application is started. If it is low for several intervals, the SHARED_POOL_SIZE must be increased.

QOS_ORACLE_lock_waits Seconds Measures the number of times a user session was waiting for a lock in the last interval.

QOS_ORACLE_locked_users Count Measures the number of locked users in an instance and displays their list.

QOS_ORACLE_login_count Users Measures the number of currently active user session except for user "SYS" and "SYSTEM".

QOS_ORACLE_long_queries Count Generates two kinds of alarms.

QOS_ORACLE_memory_usage Bytes Measures the total amount of memory (in bytes) user sessions consume (PGA).

QOS_ORACLE_mts_response Milliseconds Monitors the MTS server response in ms.

QOS_ORACLE_mts_uga_memory Bytes Monitors the MTS user memory consumption.

QOS_ORACLE_mts_wait Milliseconds Monitors the MTS server wait time in ms.

QOS_ORACLE_resource_utilization_count count Monitors the database utilization for resources.

QQOS_ORACLE_resource_utilization_percent

Pct Oracle resource utilization percentage.

QOS_ORACLE_rollback_seg_status Availability Monitors the status of the rollback segments.

QOS_ORACLE_session_waits Waits Measures the number of waits in interval.

QOS_ORACLE_sga_memory Bytes Measures the SGA memory usage in bytes by pool.

QOS_ORACLE_sga_memory_free Bytes Measures the SGA free memory usage in bytes.

oracle QoS Metrics



QOS_ORACLE_sort_ratio Percent Calculated as:

Memory sorts * 100 / total sorts

Too many disk sorts can cause performance degradation. Check parameter SORT_AREA_SIZE and SORT_AREA_RETAINED_SIZE.

QOS_ORACLE_system_statistics Count Displays available system statistics counters. These counters contain number of events since the instance start.

QOS_ORACLE_system_statistics_delta Count System statistics delta

QOS_ORACLE_system_waits Waits Measures the number of system waits by the event. This count is used to identify system bottlenecks. Use the table V$SYSTEM_EVENT to find the most "expensive" event.

QOS_ORACLE_tablespace_alloc_free Pct Measures the percentage of free space in already allocated files (not considering the AUTOEXTEND parameter).

Note: This checkpoint is set inactive per default.

QOS_ORACLE_tablespace_free Percent Measures the percentage of free space in a tablespace, considering the maximum possible tablespace size.

Note: Oracle Enterprise Manager Console does not consider maximum possible tablespace size on most of its screens (status 9i).

QOS_ORACLE_tablespace_size MB Measures the total tablespace size.

QOS_ORACLE_tablespace_status Availability Lists tablespaces that have a different status as ‘ONLINE’ or ‘SYSTEM’.

QOS_ORACLE_tablespace_temp_free Bytes Monitors temporary tablespaces for available space.

QOS_ORACLE_user_locks Locks Lists users holding a lock.

oracle QoS Metrics


This section contains the QoS Metrics for the RAC common checkpoints in the oracle probe.


QOS_ORACLE_check_db_alive Availability Monitors connectivity to the database instance.

QOS_ORACLE_tablespace_free Percent Monitors tablespaces for the available space.

QOS_ORACLE_tablespace_alloc_free Percent Monitors tablespaces for available space left in allocated files.

QOS_ORACLE_tablespace_temp_free Bytes Monitors temporary tablespaces for the available space.

QOS_ORACLE_flash_recovery_area_memory_free

Bytes Monitors the available memory in the flash recovery area.

QOS_ORACLE_tablespace_size MB Monitors tablespaces size in MB.

QOS_ORACLE_database_size MB Monitors space size (in bytes) for each database, log and data files together.

QOS_ORACLE_tablespace_status Availability Monitors the status of the tablespaces.

QOS_ORACLE_rollback_seg_status Availability Monitors the status of the rollback segments.

QOS_ORACLE_extents Extents Checks for data fragmented segments.

This section contains the QoS Metrics for the RAC node-specific checkpoints in the oracle probe.


QOS_ORACLE_instance_status Availability Monitors the state of the current instance.

QOS_ORACLE_active_services Count Checks for the currently running active services.

QOS_ORACLE_access_latency Milliseconds Monitors the overall latency.

QOS_ORACLE_gc_cr_blocks_served Count Monitors the total number of blocks constructed by the BSP process.

QOS_ORACLE_gc_cr_block_send_time Milliseconds Monitors the total time spent by the BSP process in sending constructed consistent read (CR) blocks.

QOS_ORACLE_gc_cr_blocks_received Count Monitors the total number of blocks received.

oracle QoS Metrics



QOS_ORACLE_gc_cr_block_receive_time Milliseconds Monitors the total amount of time foreground processes waited for a CR block to be sent through the interconnect.

QOS_ORACLE_RSRC_MGR_CPU_WAIT_TIME Milliseconds Monitors the total number of hundredths of a second that Oracle processes have been in a ready state.

QOS_ORACLE_AVG_BUSY_TIME Milliseconds Monitors the number of hundredths of a second that a processor has been busy executing user or kernel code.

QOS_ORACLE_buf_cachehit_ratio Percent Monitors the buffer cache-hit ratio.

QOS_ORACLE_dict_cachehit_ratio Percent Monitors the dictionary cache-hit ratio.

QOS_ORACLE_lib_cachehit_ratio Percent Monitors the ratio how often SQL queries are found in memory compared to disk.

QOS_ORACLE_memory_usage Bytes Monitors the memory consumption in bytes of Oracle users (PGA).

QOS_ORACLE_login_count Users Checks for the currently running Oracle users.

QOS_ORACLE_datafile_status Availability Monitors the status of the datafiles.

QOS_ORACLE_enqueue_timeouts Timeouts Monitors the number of table and row locks that timed out.

QOS_ORACLE_mts_response Milliseconds Monitors the redo log contention.

QOS_ORACLE_mts_wait Milliseconds Monitors the MTS server wait time in ms.

QOS_ORACLE_sga_memory Bytes Monitors the SGA memory usage.

QOS_ORACLE_sga_memory_free Bytes Monitors the free SGA memory.

QOS_ORACLE_sort_ratio Percent Monitors the sort ratio (disk, rows and memory)

QOS_ORACLE_mts_uga_memory Bytes Monitors the MTS UGA Memory.

QOS_ORACLE_user_locks Locks Monitors the number of active user locks.

QOS_ORACLE_locked_users Count Monitors the number of users suspended by locks within a timeout.

QOS_ORACLE_dataguard_status Avail Monitors the Dataguard Instance Status.

QOS_ORACLE_dataguard_gap Archivefiles Monitors the Dataguard Instance Gap.

QOS_ORACLE_dataguard_timegap Seconds Monitors the Dataguard Instance Timegap.

QOS_ORACLE_buf_cachehit_ratio_users Percent Monitors the user buffer cache-hit ratio.

oracle QoS Metrics



QOS_ORACLE_sessions_waits Waits Monitors the sessions wait counter.

QOS_ORACLE_system_statistics Count Monitors the various system statistical counters since start of the instance.

QOS_ORACLE_system_statistics_delta Count Monitors the delta of various system statistical counters since start of the instance.

QOS_ORACLE_dbfile_io Percent Monitors the database file I/O operations.

QOS_ORACLE_lock_waits Seconds Monitors time in seconds, sessions spent. waiting for a lock in interval.

QOS_ORACLE_gc_service_util Percent Monitors the global cache service utilization.

QOS_ORACLE_gc_cr_timeouts Timeouts Monitors the global cache consistent read timeouts.

QOS_ORACLE_gc_converts_timeouts Timeouts Monitors the global cache convert timeouts.

QOS_ORACLE_gc_blocks_lost Blocks Monitors the global cache blocks that are lost.

QOS_ORACLE_gc_blocks_corrupt Blocks Measures the number of blocks corrupted during transfer.

QOS_ORACLE_gc_av_lock_get_time Milliseconds Monitors the average global lock get time. (ms)

QOS_ORACLE_gc_fusion_wrt_rto Percent Monitors the ratio between fusion writes and physical writes.

QOS_ORACLE_long_queries Count Monitors the number of long running queries.

QOS_ORACLE_resource_utilization_count Count Monitors the database utilization for resources.

QOS_ORACLE_resource_utilization_percent Percent Monitors the database utilization for resources.

QOS_ORACLE_system_waits Waits Monitors the system wait counters.

QOS_ORACLE_active_users Users Checks for the currently active Oracle users.

QOS_ORACLE_active_connection_ratio Percent Monitors the active connection ratio.

oracle Alert Metrics Default Settings



This section contains the alert metrics default settings for the oracle probe.

Alarm Metric Warning Threshold

Warning Severity

Error Threshold Error Severity Description

Active connection ratio - - 75 Major

Monitors the number of users having an active transaction at the moment of a snapshot.

Active users - - 1 Information

Monitors the ratio of active connections to the total allowed connections.

Buff cache hit ratio 95 Warning 75 Major Monitors the buffer cache hit ratio.

Buff cache hit ratio users 95 Warning 75 Major

Monitors the user buffer cache hit ratio.

Chained rows - - 1 Major Check for chained rows in database.

Check db alive - - 1 Major Monitors connectivity to the database instance.

Database size 100 Information

Monitors space size (in bytes) for each database.

Datafile status - - ONLINE Major Monitors the status of the datafiles.

Dataguard gap - 10 Major Monitors dataguard instance gap.

Dataguard status - - 1 Major Monitors dataguard instance status.

Dataguard timegap - - 18000 Major Monitors dataguard instance timegap.

DB file IO - - 50 Major Monitors the database file I/O operations.

Dict cachehit ratio 90 Warning 75 Major Monitors the dictionary cache-hit ratio.

Enqueue timeouts - - 1 Major Monitors the number of table and row locks that timed out.

Extents - - 10 Major Checks for data fragmented segments.




Warning Severity


Flash recovery area - - 322122547 Major

Monitors the available memory in the flash recovery area.

Avg global lock get time - - 30 Major Monitors the average global lock get time (ms).

Global block corrupt - - 1 Major Monitors the corrupt global cache blocks.

Global blocks lost - - 1 Major Monitors the lost global cache blocks.

Global convert timeouts - - 1 Major Monitors the global cache convert timeouts.

Global consistent read timeouts - - 1 Major

Monitors the global cache consistent read timeouts.

Global fusion writes ratio - - 30 Major

Monitors the ratio between fusion writes and physical writes.

Global service utilization - - 85 Major

Monitors the global cache service utilization.

Index status - - VALID Major Monitors the index status.

Invalid objects 0

Information- default

1

0

Major- count

Major- count_interval

Checks for invalid objects in database.

Lib cachehit ratio 95 Warning 75 Major

Monitors ratio, how often SQL's are found in memory compared to disk.

Lock waits - -

1

1

Information

Major

Monitors time in seconds, sessions spent waiting for a lock in interval.

Locked users - -

1

300

Major

Information

Monitors the number of users suspended by locks within a timeout.

Login count - - 1 Information Checks for currently running login users.

Long queries - -

1

10

Major

Information Monitors the number of long running queries.

Memory usage - - 2000000 Major Monitors memory consumption in bytes of Oracle users (PGA).




Warning Severity


MTS response - - 10 Information Monitors the MTS server response in ms.

MTS UGA memory - - 1 Information Monitors the MTS UGA memory.

MTS wait - - 10 Information Monitors the MTS server wait time in ms.

No next extents 1

Information- Default

1

Major- Count Checks for objects that are unable to allocate next extents.

Redo logs - - 1 Major Monitors redo log contention.

Remaining extents - - 10 Major Checks the remaining number of extents.

Resource util - - 90 Major

Monitors database utilization for resources (Processes, Sessions, and Transactions).

Rollback seg status - - ONLINE Major Monitors the status of the rollback segments.

Roll back segments - -

95- Default

1- Count Major Checks for sufficient number of rollback segments.

Session waits - - 1 Information Monitors the sessions wait counter.

SGA memory - - 1 Information Monitors the SGA memory usage.

SGA memory free - - 4096 Information Monitors free SGA memory.

Sort ratio - - 99 Major Monitors the sort ratio (disk, rows, and memory).

System statistics - - 1 Information

Monitors various system statistical counters since last start of instance.

System statistics delta - - 1 Information

Monitors delta of various system statistical counters since last start of instance.

System waits - - 1 Information Monitors the system wait counters.

Tablespace alloc free - - 10 Major Monitors for available space in allocated files.




Warning Severity


Tablespace deficit 1

Information-Default

1

Major-Count Checks if next extent is bigger than available space.

Tablespace free - - 10 Major Monitors tablespaces for available space.

Tablespace size - - 1000 Major Monitors tablespaces size in MB.

Tablespace status - - ONLINE Major Monitors the status of the tablespaces.

Tablespace temp free - - 10000 Major Monitors temporary tablespaces for available space.

User locks - -

1

1

Information

Major Monitors the number of active user locks.

This section contains the alert metrics default settings for the RAC-common checkpoints in the oracle probe.

Metric Name Warning Threshold

Warning Severity

Error Threshold

Error Severity

Description

Check dbalive - - 1 Major Monitors connectivity to the database instance.

Tablespace Free - - 10 Major Monitors tablespaces for available space.

Tablespace Alloc Free

- -

10 Major Monitors tablespaces for available space in allocated files.

Tablespace Temp Free

- - 10000 Major Monitors temporary tablespaces for available space.

Flash Recovery area Memory Free

- - 322122547

Major Monitors flash recovery area.

Tablespace Size - 1000 Major Monitors tablespaces size in MB

Database Size - 100 Information

Monitors space size (in bytes) for each database.




Warning Severity

Error Threshold

Error Severity

Description

Tablespace Status - Online Major Monitors the status of the tablespaces.

Index Status - - Valid Major Monitors the index status.

Rollback Segments

- - 95 Major Monitors the status of the rollback segments.

Rollback Segments

- - 1 Major Monitors the status of the rollback segments.

Tablespace Deficit - - 10 Major Checks if next_extent is bigger than available space.

Tablespace Deficit - - 1 Information

Checks if next_extent is bigger than available space.

Remaining Extents - - 10 Major Checks the remaining number of extents.

No Next Extents - - 1 Information

Checks for objects that are unable to allocate next extent.

No Next Extents - - 1 Major Checks for objects that are unable to allocate next extent.

Invalid Objects - - 0 Information

Checks for invalid objects in database.

Invalid Objects - - 1 Major Checks for invalid objects in database.

Invalid Objects - - 0 Major Checks for invalid objects in database.

Chained Rows 1 Major Checks for chained rows in database.

Extents - - 10 Major Checks for data fragmented segments.



This section contains the alert metrics default settings for the RAC-specific checkpoints in the oracle probe.


Warning Severity

Error Threshold

Error Severity

Description

Instance Status - - 1 Major Monitors the state of the current instance.

Gc cr blocks served

- - 1 Major Monitors the total number of blocks constructed by the BSP process.

Gc cr block log send time

- - 1 Major Monitors total time spent by the BSP process in sending constructed consistent read (CR) blocks.

Gc cr blocks received

- - 1 Major Monitors total number of blocks received.

Gc cr block receive time

- - 1 Major Monitors total amount of time foreground processes waited for a CR block to be sent through the interconnect.

Buf cachehit ratio 95 Warning

75 Major Monitors the buffer cache-hit ratio.

Dict cachehit ratio

90 Warning

75 Major Monitors the dictionary cache-hit ratio.

Lib cachehit ratio 95 Warning

75 Major Monitors ratio, how often SQL's are found in memory compared to disk.

Memory usage - - 2000000

Major Monitors memory consumption in bytes of Oracle users (PGA).

Login count 1 Information

- - Check for currently running Oracle users.

Datafile status - - ONLINE Major Monitors the status of the datafiles.




Warning Severity

Error Threshold

Error Severity

Description

Enqueue timeouts

- - 1 Major Monitors number of table and row locks that timed out.

Redo logs - - 1 Major Monitors redo log contention.

Mts response 10 Information

- - Monitors the MTS server response in ms.

Mts wait 10 Information

- - Monitors the MTS server wait time in ms.

SGA memory 1 Information

- - Monitors the SGA Memory usage.

SGA Memory free 4096 Information

- - Monitors the free SGA Memory.

MTS UGA Memory

1 Information

- - Monitors the MTS UGA Memory.

User locks 1 Information

1 Major Monitors the number of active user locks.

Locked users 300

Information

1 Major Monitors the number of users suspended by locks within a timeout.

Dataguard status - - 1 Major Monitors Dataguard Instance Status.

Dataguard gap - - 10 Major Monitors Dataguard Instance Gap.

Dataguard timegap

- - 18000 Major Monitors Dataguard Instance Timegap.

Buf cachehit ratio users

- - 75 Major Monitors the user buffer cache-hit ratio.

Buf cachehit ratio users

- - 95 Warning Monitors the user buffer cache-hit ratio.

Sessions waits 1 Information

- - Monitors the sessions wait counter.

System statistics 1 Information

- - Monitors various system statistical counters since start of the instance.




Warning Severity

Error Threshold

Error Severity

Description

System statistics delta 1

Information

- - Monitors delta of various system statistical counters since start of the instance.

System Waits 1 Information

- - Monitors the system wait counters.

Dbfile io - - 50 Major Monitors the database file I/O operations.

Lock waits 1 Information

1 Major Monitors time in seconds, sessions spent. waiting for a lock in interval.

Gc service util - - 85 Major Monitors the global cache service utilization.

Gc cr timeouts - - 1 Major Monitors the global cache consistent read timeouts.

Gc converts timeouts

- - 1 Major Monitors the global cache convert timeouts.

Gc blocks lost - - 1 Major Monitors the global cache blocks lost.

Gc_blocks_corrupt

- - 1 Major Measures the number of blocks corrupted during transfer.

Gc av lock get time

- - 30 Major Monitors the average global lock get time. (ms)

Gc fusion wrt rto - - 30 Major Monitors the ratio between fusion writes and physical writes.

Long queries - - 1 Major Monitors the number of long running queries.

Long queries 10 Information

- - Monitors the number of long running queries.

Resource utilization

- - 90 Major Monitors database utilization for resources (Processes,Sessions and Transactions).




Warning Severity

Error Threshold

Error Severity

Description

Active users 1 Information

- - Check for currently active Oracle users.

Active Connection Ratio

- - 75 Major Monitors active connection ratio.

Gc cr block send time

- - 1 Major Monitors Total time spent by the BSP process in sending constructed consistent-read (CR) blocks.

Session Waits 1 Information

- - Monitors the sessions wait counter.

Sort Ratio - - 99 Major Monitors the sort ratio (disk, rows and memory).

Chapter 4: Known Issues 49

Chapter 4: Known Issues

The known issues of the probe are:

■ While upgrading the oracle probe from version 4.56 and earlier to version 4.60 or later, ensure that the PPM, service_host, and MPSE are restarted for the RAC functionality to become usable.

■ The users cannot create custom alarm messages. Hence, they need to select an existing alarm message.

■ The oracle probe must not be configured on both the Infrastructure Manager(IM) GUI and Admin Console(AC) GUI.

■ The probe configuration for both the IM GUI and AC GUI is separate. For example, any profile that is created in the IM GUI is not available on the AC GUI and must be recreated.

■ Custom checkpoints may fail sometimes and may give errors. In such situations, delete the custom checkpoints from raw configuration.

■ Dynamic Population of Message Text field with the corresponding Message field selected in the drop-down list at runtime is a limitation of the PPM. On creating a checkpoint with a new threshold, first select message and save it. After the reload operation, the message text field gets updated with the corresponding message text.

■ If you see PPM-023 error and Unable to Retrieve Configuration issues, click Retry or reopen the AC GUI.

■ In Oracle RAC, from Oracle 11.1 onwards, in all checkpoints, the term global cache is replaced by gc. Therefore, if any custom query in Oracle 11g or 12c includes the term global cache, then no value is returned.

■ On Windows 64bit platform, the probe cannot be installed into the default directory - "Program Files (x86)". A bug in Oracle Client is causing connection errors, if the application home directory names includes special characters, like "(" (Oracle Bug 3807408).

■ Error ORA-12705 together with log entry "OCIEnvCreate failed with rc = -1" can happen, if environmental variable NLS_LANG is set. Solution is to set this variable to empty space in the controller environment.

■ On 64 bit Linux, user may get a warning message of insufficient access rights when connection test is performed, even if all the required access rights are provided. The connection can still be used to schedule the profile. Please make sure all the required access rights are provided to the user.

■ In custom checkpoints, if query tries to fetch data from a table with more than 32 columns, probe will limit the number of columns to 32.

ca unified infrastructure...

Documents