oracle (Oracle Database Monitoring) Release Notes

The Oracle Database Monitoring (oracle) probe allows you to monitor your Oracle databases to detect, diagnose, and resolve Oracle performance issues when they occur. This information is presented to a database administrator as reports, and as alarms when database performance crosses a specified threshold.
uimpga-ga
oracle_RN
The Oracle Database Monitoring (oracle) probe allows you to monitor your Oracle databases to detect, diagnose, and resolve Oracle performance issues when they occur. This information is presented to a database administrator as reports, and 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 do capacity planning.
The Oracle client or server is mandatory for oracle probe to work.
The probe monitors local and remote Oracle database instances, periodically scans through monitoring profiles, and applies checks to the instances. The probe successfully monitors:
  • 32-bit Oracle client on a 32-bit OS
  • 64-bit Oracle client on a 64-bit OS
The probe supports Real Application Cluster (RAC) only through Admin Console.
From version 4.8, the probe introduced multi-tenancy support, which allows you to monitor Oracle 12c container database (CDB) and pluggable database (PDB).
Contents
Revision History
This section describes the history of the revisions for the oracle probe.
Support case(s) may not be viewable to all customers.
Version
Description
State
Date
5.45
What's New:
  • Added support for Oracle 18C RAC and 19c NON-RAC and RAC databases.
Fixed Defects:
  • Fixed an issue where Oracle probe configuration error for custom check points using Admin console.
    Support Case Number: 01337227
  • Fixed an issue where Oracle probe sent timeout error for custom query when the query takes more than 30 seconds using IM.
    Support Case Number: 01176220
  • Fixed an issue where Oracle Probe 5.41 don't clear alerts after probe reboot.
    Support Case Number: 01351957
GA
February 2020
5.41
What's New:
  • Added support for Oracle 12c R2 and 18c databases.
  • Added support for the use of stored procedures in creating custom checkpoints. For more information, see Custom Checkpoints.
  • New MCS template (oracle_mcs_template 5.33). Added an option allowing you to use the same value as specified in “Alarm Source” for the “Source” field of QoS messages. For more information, see Oracle MCS Profile Type Configuration.
  • (April 2019) The Oracle MCS (version 5.25 onwards) has been updated to address the common vulnerabilities and exposures by updating the jackson-databind libraries. For more information and CVE numbers, see Addressing Jackson Vulnerabilities.
Fixed Defects:
  • Fixed an issue where not all activated RAC checkpoints collect QoS event though this option is enabled in the RAC template.
    Support Case Number: 01169941
  • Fixed and issue where the probe was not able to monitor Oracle ASM diskgroups and other services.
    Support Case Number:
    00985582
GA
February 2019
5.30
What's New:
  • New MCS template (oracle_mcs_template 5.31) with:
    • Enhanced profiles that enable you to configure metrics, baselines, alarm thresholds, alarms - including Time Over Threshold alarms - and custom alarm and close alarm messages, all within a single MCS profile. For more information, see Configuring Alarm Thresholds in MCS.
GA
June 2018
5.30
What's New:
  • AES-128 encryption that is required for FIPS compliance, through the Administration Console. For more information on how to enable FIPS encryption, see Enable FIPS Encryption.
  • Added support to generate alarms based on the Severity instead of the ID.
  • Added support to enable or disable alarms for a checkpoint.
Fixed Defects:
The settings updated in the checkpoints sections of Oracle did not reflect in the profile when configured from the Administration Console.
Support case number: 650309
GA
October 2017
5.20
What's New:
  • (Admin Console only)
    Added support to create custom checkpoints for RAC connections.
  • Added support to map checkpoint alarms to database instance name. For more information, see
    Map Alarms to Database Instance Name
    section.
Fixed Defects:
  • For the RAC common
    tablespace_free
    checkpoint, the probe displayed multiple grids for both QoS and thresholds.
    Support case number 686906
  • On Linux systems, the probe crashed after you enabled all checkpoints and QoS for an ASM profile and saved the configuration.
    Support case number 621689
GA
April 2017
5.10
What's New:
  • Added support to monitor Oracle Automatic Storage Management (ASM) on Oracle 11g and 12c databases for RAC and non-RAC systems.
    • ASM Disk Count
    • ASM Disk Bytes Read
    • ASM Disk Bytes Write
    • ASM Disk Group Count
    • ASM Disk Group Total Space
    • ASM Disk Group Used Space
    • ASM Disk Group Used Space Percentage
    • ASM Disk Read Request
    • ASM Disk Write Request
    • ASM Disk Total Space
    • ASM Disk Used Space
    • ASM Disk Used Space Percentage
  • Added Blocking Session information in the
    lock_waits_4
    alarm message.
  • Included Oracle error message in the
    check_dbalive
    checkpoint.
  • Ability to define another threshold for
    tablespace_free
    checkpoint. For more information, see AC or IM Configuration articles.
  • The probe supports monitoring within an IPv6 environment.
    As a prerequisite, the system where CA UIM is installed, must have IPv4-IPv6 dual stack configured.
GA
October 2016
5.01
Fixed Defects:
  • (For RAC checkpoint in Admin Console) The probe did not generate alarms for the second threshold if the first threshold did not breach.
    Support case number 427677
  • The probe displayed the
    resource_util
    checkpoint data under separate two nodes on Unified Service Management (USM). For more information, see
    Known Issues
    .
    Support case number 348882
  • When monitoring oracle 12c on an AIX operating system, the probe created a core when the Oracle database was down. For more information, see oracle Troubleshooting.
    Support case number 300723
  • The probe did not save the configuration on editing or deleting a threshold from any checkpoint.
    Support case number 261392
GA
July 2016
5.00
What's New:
  • Added support to use the alarm source as the identification method in QoS messages.
  • Added feature to rename the existing connections and profiles in the probe Infrastructure Manager. For more information, see Rename Connection or Profile.
Fixed Defects:
  • The probe crashed when upgrading on an RHEL environment.
    Support case number 246083
  • The probe displayed a profile in suspended state as green (resumed) when you launched the probe in another Infrastructure Manager.
    Support case number 246864
  • Updated the Admin Console documentation for the default checkpoints that are added as static to a profile in the probe Admin Console.
    Support case number 260900
  • When deleting the default threshold for the invalid_objects checkpoint, the probe did not generate the count alarms. The probe only generated the default alarms.
    Support case number 275647
  • The probe did not generate any QoS for the locked_user checkpoint.
    Support case number 320807
GA
March 2016
4.91
Fixed Defects:
  • When creating a profile from Admin Console, all the profile checkpoints are now inactive, by default.
    Salesforce case 00159509
  • When opening the probe in a deactivated state, the probe displayed incorrect upgrade message text.
    Salesforce case 00160547
  • The probe displayed incorrect status of the activated checkpoints in the Status tab.
    Salesforce case 00168455
  • On a non-Windows OS, the probe now displays the Device ID of the monitored Oracle database.
    Salesforce case 70002729
September 2015
4.90
What's New
:
  • Added support for AIX 6 and 7 platforms.
June 2015
4.81
What's New
:
  • Updated the probe Help link.
December 2014
4.80
What's New
:
  • Added support for Oracle 12c Container Database (CDB) and Oracle 12c Pluggable Database (PDB).
  • Added a checkpoint to monitor the number of PDBs in a specific CDB.
Fixed Defects
:
  • Fixed a defect where the Profile Timeout alarms were visible in Alarm Console even though the probe connection was successful. The alarms did not clear even if
    Clear Alarm on Restart
    check box is selected.
    Salesforce case 00144941
November 2014
4.71
Fixed a defect where the Oracle probe GUI flickered on clicking Profiles/Checkpoints in the
Status
tab.
Salesforce case 00143137
October 2014
4.70
  • Added support for Oracle 12c.
  • Removed support for the Oracle versions 9i and 10g.
September 2014
4.61
Fixed Defects:
  • TNS alarms were visible in Alarm Console even after the probe connection was successful. The alarms did not clear even if user changes the connection and
    Clear Alarm on Restart
    check box was selected.
    Salesforce cases: 00122633, 00132174, 00121391
  • SQL timeout alarms were getting generated irrespective of the checkpoint and had incorrect suppression key.
  • For the tablespace that has
    autoext
    as
    Y
    , probe was calculating wrong value of
    FREESP
    variable. Due to the wrong calculation, the messages displayed incorrect values.
    Salesforce case 00132777
  • The probe package of 32-bit was getting installed on 64-bit AIX system. (Salesforce Case: 00132673)
  • Instance name was not coming in the
    check_dbalive
    alarm message where the connection was unsuccessful.
    Salesforce case 00131416
July 2014
4.60
New Feature:
  • Implemented the Oracle RAC features including 20 new checkpoints for RAC.
Defects Fixed:
  • Fixed a defect where global cache checkpoints are not returning any value for oracle 11.
Note:
RAC can be configured only through Admin Console GUI.
March 2014
4.56
New Feature:
  • Added a callback to determine whether dependencies are present on the system where probe is deployed so that the probe runs successfully.
Note:
This feature is only applicable for Admin Console GUI.
March 2014
4.55
Fixed Defects:
  • Defect fixed related to the Oracle probe not displaying metrics for all tablespaces. The UMP was not displaying QoS as a chart in the metric tree for all Oracle native checkpoints.
  • Defect fixed related to QOS_ORACLE_tablespace_alloc_free Pct and QOS_ORACLE_tablespace_free Percent checkpoints, generating alarms for each tablespace with almost identical values.
January 2014
4.52
Added Probe Defaults
February 2013
4.51
  • Fixed Profile showing template checkpoints if a group is used.
  • Fixed ORA-00923 and ORA-24333 error coming in
    locked_users
    and
    rollback_segments
    checkpoints for Oracle 11g profiles.
  • Fixed missing
    no_next_extents
    messages in the cfg file.
  • Fixed
    Status
    tab not showing current values of monitored checkpoints.
January 2013
4.50
  • Fixed Incorrect alarm message in database_size checkpoint.
  • Added support for AIX 5.
  • Fixed issue with improper functionality of Suspend/Resume profile.
  • Changed default alarm message of redo_logs checkpoint.
  • Fixed issue of oracle probe crashing in Solaris.
  • Added support to modify connection failure message.
  • Fixed the value of autoextend field in tablespace_alloc_free checkpoint.
  • Update the resource_util checkpoint query for the oracle bug "Incorrect (always increasing) values showed in v$resource_limit for the transactions field [ID 412314.1]".
  • Added support to skip DBA/SELECT_CATALOG_ROLE checking.
  • Fixed issue in checksum calculation during custom template creation.
  • Fixed issue of the checkpoint threshold in profile, if the checkpoint is marked as static into the profile.
  • Fixed exceptions in Exclude test.
June 2012
4.43
  • Modified the Query for the dataguard_gap checkpoint.
  • Suppression key (alarm key) & QoS key is changed for dataguard_gap checkpoint. When the probe upgrades from previous versions, the QoS series for this checkpoint break due to changes in the QoS target key.
  • Added new i18 tokens for the dataguard gap.
November 2011
4.42
  • Added support for oracle client 11.2 on Solaris Sparc.
  • Fixed an issue occurring on Unix platforms where multiple probe executable were getting spawned instead of a single executable.
August 2011
4.41
  • While creating a custom checkpoint $instance variable is visible in Variable Window.
  • Custom checkpoint can now be updates when opened through Status Tab.
  • Fixed the issue of sending null QoS for dict_cachehit_ratio
  • Supports Oracle client 11.2 for Linux 32-bit & 64-bit systems.
  • This version does not support oracle client 11.2 for Solaris Sparc system.
  • Fixed Memory Leak issue
  • Fixed an issue in tablespace_free checkpoint where the probe was incorrectly calculating free tablespace % for temp tablespaces.<\li>
  • Fixed one more issue in the tablespace_free checkpoint where the free tablespace calculation was incorrect.
  • Internationalization corrections.
June 2011
4.31
  • Added validation if custom query is blank.
  • Added code to fetch query from file in edit mode.
  • Fixed other minor GUI issues that are related to a custom checkpoint.
  • Added field in the custom query tab to select predefined connections.
  • Added support for the role-based login.
  • Added support for alarms.cfg.
  • Added functionality for delta calculation in custom checkpoint.
  • Added code to prohibit the use of whitespace in configurator.
  • Added support to confirm if the user has enough rights to run the query.
  • Removed validation of adding at least one threshold while creating a checkpoint.
  • Fixed GUI crash defects.
  • Fixed defect to return valid checksum after restart for Custom query.
  • Fixed defect for metric remaining_extents takes way too long to complete.
  • Fixed defect; so, correct binary is deployed in 64-bit Linux.
  • Fixed defects in v4 framework library.
September 2010
4.20
  • Added support for extended NIS database information.
  • Fixed an issue where the probe was reporting incorrect values in the GUI.
June 2010
4.11
  • Fixed a crash in the probe by applying fix to v4 helper library.
  • Fixed defect that is related to tablespace_free checkpoint.
March 2010
4.10
  • Added a checkpoint active_connection_ratio for monitoring percentage of active connections to total available connections.
March 2010
4.04
  • Fixed an issue in the database size checkpoint where total database size was reported incorrectly.
January 2010
4.03
  • Fixed defects in few checkpoint variables and alarms.
  • Added fix for memory leak.
  • Added fix for a SQL query timeout.
January 2010
4.02
  • Fixed defect in GUI.
  • Fixed defects in few checkpoint variables.
  • Probe now sends NULL QoS for all the QoS defined in the QoS list when no data is received.
December 2009
3.91
  • Configuration for no_next_extent, invalid_objects, and tablespace_deficit corrected.
  • Known issue
    : The Oracle RAC system statistics that are used for 'gc_' checkpoints, starting with Oracle 10.1, are no longer available. Therefore these checkpoints return no value when activated.
September 2008
3.90
  • Added Support for Solaris.
  • Added numbers of objects alarm for these checkpoints:
    • no_next_extent
    • invalid objects
    • tablespace deficits
  • Hotfix for Locking users
Note
: Profiles with these checkpoints must be removed and recreated, because of new functionality.
July 2008
3.75
Hotfix for Checkpoint Invalid Objects
Note
: While the package contains Solaris binaries, Solaris is not a supported platform now. CA does not recommend installation of the probe on Solaris.
March 2008
3.74
Memory leak corrected.
February 2008
3.73
Added new NimBUS libraries.
January 2008
3.71
Removed support for Oracle 8.0.x.
December 2007
3.70
  • Corrected minor problems with filters
  • Added support for Oracle 11g
November 2007
3.64
  • Crash in some checkpoints if instance not available fixed
  • QoS error with session_waits fixed
  • Error with profiles containing "." fixed
  • Problem with sga_memory_free - objects containing ":" fixed
  • Queries for Oracle 10g do not try to use rules based optimizer any more
November 2007
3.62
  • QoS errors fixed
  • Problem in period setting (scheduling) corrected
  • One-time run error (scheduling) fixed
  • Profile timeout suppression key corrected
  • Calculation of free space for temporary and undo-tablespaces corrected
  • buf_cachehit_ratio problem fixed
July 2007
3.60
  • Multiple QoS per checkpoint
  • exclude lists
  • # of samples for alarming
  • new checkpoint long_queries
  • auto-update (GUI)
  • new checkpoint tablespace_size
  • new checkpoint database_size
  • new parameter log-size
  • new parameter "Alarm Source"
  • buf_cache_hit_ratio query adjusted for Oracle 10.2
June 2007
3.53
A clear is only issued if an alarm has been sent.
January 2007
3.52
  • High CPU load for gc_ checkpoints in Oracle 8 solved
  • Negative values in sort_ratio problem solved
  • datafile_status problem with SYSTEM tablespaces solved (v$datafile_header now used instead of v$datafile)
  • datafile_status and dbfile_io object threshold saving on UNIX systems problem solved
  • tablespace_alloc_free - query changed
December 2006
3.50
  • Internal - Config file template added
  • LINUX built with Oracle 10 libraries
August 2006
3.05
"tablespace_free" calculation for multi-file tablespaces corrected.
July 2006
3.04
  • Linux enabled
  • Remaining_extents - problem with 'UNKNOWN' values fixed
  • QoS time corrected
  • buf_cache_hitratio fixed
  • checkpoint execution time report
  • Interval value calculation corrected
  • QoS source name corrected to robot name
  • 'invalid_objects' suppression key corrected
  • new 'buf_cachehit_ratio' formula
  • Multi-threading - every profile runs in a separate thread
  • Scheduling - every checkpoint can have its own schedule
  • Multiple thresholds - every checkpoint can have more than one threshold
  • Message pool - messages can be customized and reused among checkpoints
  • Connection retry - for every connection there can be number of attempts defined, before the probe raises an alarm
  • Resizable GUI windows - all windows with lists are resizeable
June 2006
2.17
  • Instance name at "locked_users" checkpoint message
  • Added Linux support for package.
March 2006
2.16
  • Instance name at "locked_users" checkpoint message
  • Linux support fix
November 2005
2.12
  • 10g tolerancy
  • new checkpoint lock_waits
  • user_locks and locked_users changed
  • error in buf_cachehit_ratio_users fixed
  • check for % in password removed
  • start parameter -n to change probes name
  • keeping time_cnt through restart (24hour cycle)
  • GUI - new button "info" to display GUI and executable version numbers
March 2005
Probe Specific Hardware Requirements
The oracle probe must be installed on systems with the following minimum resources:
  • Memory: 2-4 GB of RAM. Probe OOB configuration requires 256 MB of RAM.
  • CPU: 3 GHz dual-core processor, 32-bit or 64-bit.
Probe Specific Software Requirements
The oracle probe requires the following software environment:
  • CA Unified Infrastructure Management 8.1 or later
  • Robot 7.62 or later (recommended)
  • Probe Provisioning Manager (PPM) probe version 2.39 or later (required for Admin Console)
    The ppm version 3.30 is required to enable the new fields of the oracle probe version 5.0.
  • Java JRE 6 or later (required for Admin Console)
  • (From version 5.10)
    The probe requires the following additional probes:
    • ci_defn_pack 1.26 or later (required to view data on Unified Management Portal (UMP))
    • wasp_language_pack 8.46 or later (required to view data on UMP)
    • mps_language_pack 8.46 or later (required to view correct metric type on Admin Console)
      Restart
      service_host
      after you deploy the
      mps_language_pack
      .
  • Windows: Oracle Client (Net Services) 11.x or 12.x
  • Linux and Solaris: Oracle Client 11.x or 12.x
Oracle INSTANT CLIENT is not supported.
  • Role-based login is also supported, for example, sys as sysdba
  • From NMS 7.5, RAC is supported but can only be configured from Admin Console.
  • Ensure that the Probe Provisioning Manager (ppm) 3.47 or later is available for AES encryption from the Administration Console.
Upgrade Considerations
Consider the following upgrade scenarios:
  • When upgrading the probe to version 4.80 or later, the PDB_Count checkpoint is added as a template and is available in all the profiles. By default, the checkpoint is disabled. Enable the checkpoint to monitor the number of PDBs in a particular CDB. This checkpoint will work only for those profiles that are linked to a CDB connection. For other profiles, no result is displayed even if the checkpoint is enabled.
  • When upgrading the probe, any deleted default configurations, thresholds, or QoS are added back in the probe.
(Version 5.30) Probe Specific Changes After Upgrade
The probe supports AES-128 bit encryption and decryption. To enable this feature in your Administration Console (AC), set the
NIM_PROBE_CRYPTO_MODE
environment variable to one of the following values in the probe:
  • TWOFISH
    (default)
  • AES_128_COMPAT
  • If you do not set any value of the environment variable, then the probe uses
    TWOFISH
    encryption and decryption, by default.
  • Restart the
    Nimsoft Robot Watcher
    service after you set the environment variable.
  • The probe fails to start if you provide incorrect values for the environment variable. CA does not recommend you to change this value after you set it once.
Oracle Supported Versions and Clients
The following matrix summarizes client and server combinations that are supported by the oracle probe.
Server Version
Client Version
18.1.0
12.2.0
12.1.0
11.2.0
11.1.0
18.1.0
Yes
Yes
Yes
Yes
No
12.2.0
No
Yes
Yes
Yes
No
12.1.0
No
No
Yes
Yes
Yes
11.2.0
No
No
No
Yes
Yes
11.1.0
No
No
No
No
Yes
Known Issues and Workarounds
The known issues of the probe are as follows:
  • The probe does not support alarms for
    asm_disk_total_space
    and
    asm_disk_group_total_space
    checkpoints.
  • For the resource_util checkpoint (with two default QoS), the probe creates a
    Custom
    node on USM and displays one QoS data under it. The second QoS data displays under
    Connection Name
    node.
  • (Applicable from version 5.01)
    Create a
    set_resource_util_qos
    key with
    yes
    value in the Raw Configure interface >
    setup
    section. When you enable this key, the probe displays both the default QoS data under
    Connection Name
    node. If you do not define this key, or set it as
    no
    , the probe displays the checkpoint data under two separate nodes.
    Setting the
    set_resource_util_qos
    key as
    yes
    changes the metric ID of the QoS and the USM view for the metric in the existing profiles. CA recommends you to clear the database before you enable the key.
  • A memory leak is observed when the probe connects to the Oracle 12c client or the server. This is a known issue with the Oracle 12 databases.
  • The probe may not connect to the database after you install or upgrade the Oracle client. Restart the probe after installing the client for a successful connection.
  • 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 neither available on the AC GUI nor can be migrated. It must be created again.
  • 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.
  • In Oracle RAC, from Oracle 11.1 and above, the term
    global cache
    is replaced by
    gc
    in all checkpoints. Therefore, if any custom query in Oracle 11g or 12c includes the term
    global cache
    , then no value is returned. The RAC functionality is supported and configured through Admin Console GUI only.
  • On Windows 64-bit 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 name 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. Ensure 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.
  • If a custom QoS is added to an existing monitoring profile, the Unified Management Portal (UMP) creates a separate node, Custom, in the Metric section. It does not display the user-defined description and unit.
  • If a custom checkpoint is added to an existing monitoring profile, the UMP creates a separate node, Dynamic, in the Metric section. It does not display the user-defined description and unit.
The Admin Console GUI of the probe has the following additional limitations:
  • The probe does not support alarms for
    asm_disk_total_space
    and
    asm_disk_group_total_space
    checkpoints. A user can add thresholds for these checkpoints, however they are not saved.
  • The probe does not support renaming connections and profiles.
  • On version 4.90 of the probe, custom QoS in a checkpoint do not generate alarms if the default QoS of the checkpoint is deleted. This is applicable for AIX 6 and AIX 7 platforms.
  • 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 IM GUI and 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.
  • 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, the term
    global cache
    is replaced by
    gc
    in all checkpoints. Therefore, if any custom query in Oracle 11g or 12c includes the term
    global cache
    , then no value is returned.
  • To discover RAC-specific nodes, the ppm probe should be deployed on the same subnet as the oracle probe.
  • On Windows 64-bit 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 name 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. Ensure all the required access rights are provided to the user.
  • If the oracle probe is deployed on a non-Windows OS, the UMP displays the metrics and alarms on the robot and not on the Oracle server.
  • In custom checkpoints, if your query tries to fetch data from a table with more than 32 columns, the probe limits the number of columns to 32.
  • If a custom QoS is added to an existing monitoring profile, the UMP creates a separate node, Custom, in the Metric section. It does not display the user-defined description and unit.
  • If a custom checkpoint is added to an existing monitoring profile, the UMP creates a separate node, Dynamic, in the Metric section. It does not display the user-defined description and unit.
  • If a checkpoint has multiple QoS and you activate or deactivate one QoS, the other QoS of the checkpoint are also activated or deactivated.
  • If a checkpoint has multiple alarms and you activate or deactivate one alarm, the other alarms of the checkpoint are also activated or deactivated.
  • If you enable a checkpoint in the
    Checkpoints
    node, the checkpoint is enabled for all the monitoring profiles and all alarms are generated.
  • In custom checkpoints, if you edit a message variable, it adds a new message variable in the Message Variable table. To edit a message variable in custom checkpoint, delete and create a new message variable.
  • The probe generates alarms for a threshold of an active checkpoint even if you clear the
    Publish Alarms
    field of the checkpoint.
  • If you change any default checkpoint in the Template, the changes are available in the new profiles only. Existing profiles are not impacted with these changes.
(From Version 5.20) Map Alarms to Database Instance Name
You can configure the probe to change the Configuration Item (CI) name to map individual alerts of the profile checkpoints to come under one Database Instance Name.
On a test environment:
Before you change the probe configuration on your production environment, CA recommends that you perform these steps on a test environment. Run the following query on your database:
delete from s_qos_data where probe = 'oracle' and robot = '<robotname>'
Repeat the query for all robots, if the oracle probe is deployed on multiple robots.
On a production environment:
Follow these steps to map alarms to database instance name:
  1. Deactivate the oracle probe.
  2. Delete the alarms.cfg file located in the
    CA UIM Installation Directory
    > probes > Database > oracle folder.
  3. Upgrade the probe to version 5.20 or later.
  4. Navigate to your robot and open the probe Raw Configure interface.
    Do not activate your probe now.
  5. Navigate to the
    setup
    section, and set the
    usm_display_db_level
    key to 1. When you enable this key, the CI name is appended with “
    ##<Database Instance Name>
    .” If there is no database name mentioned in the CI for a profile checkpoint, the probe adds the master database name in the defined format.
    Default: 0
  6. Clear the
    niscache
    folder of all the robots in your environment that have the oracle probe. The folder is located in the
    CA UIM Installation Directory
    .
  7. Acknowledge all alarms from the probe.
  8. Run the following queries on your UIM database to delete the QoS data from the probe:
    delete from s_qos_data where probe = 'oracle'
    delete from s_qos_definition where qos_group = 'QOS_ORACLE'
    delete from nas_alarms where prid = 'oracle'
    delete from cm_configuration_item_metric where ci_metric_type like '4.1%'
    delete from cm_configuration_item where ci_type like '4.1%'
  9. Restart the
    data_engine
    ,
    nas
    ,
    nis_server
    ,
    discovery_server
    , and
    discovery_agent
    probes.
  10. Activate the oracle probe.