32-bit Oracle client on a 32-bit OS
64-bit Oracle client on a 64-bit OS

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.

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

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.

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.

TWOFISH
(default)
AES_128_COMPAT

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 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.

 
delete from s_qos_data where probe = 'oracle' and robot = '<robotname>'  

Deactivate the oracle probe.
Delete the alarms.cfg file located in the
CA UIM Installation Directory
> probes > Database > oracle folder.
Upgrade the probe to version 5.20 or later.
Navigate to your robot and open the probe Raw Configure interface.
Do not activate your probe now.
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
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
.
Acknowledge all alarms from the probe.
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%' 
Restart the
data_engine
,
nas
,
nis_server
,
discovery_server
, and
discovery_agent
probes.
Activate the oracle probe.