oracle probe - possible memory leak - probe consumes 100 MB/hr without release.
search cancel

oracle probe - possible memory leak - probe consumes 100 MB/hr without release.


Article ID: 4263


Updated On:


DX Unified Infrastructure Management (Nimsoft / UIM) CA Unified Infrastructure Management On-Premise (Nimsoft / UIM) CA Unified Infrastructure Management SaaS (Nimsoft / UIM)


The oracle probe appears to have a memory leak. The oracle probe is monitoring database instances remotely (not on the local database server). The memory is continuously increasing.


  • DX UIM v8.31
  • oracle probe v5.01 GA
  • OS the probe is running on: RHEL 6, 2.6.32-573.22.1.el6.x86_64
  • hub v7.80
  • robot v7.80, where oracle probe sits
  • 12 G of RAM available on the robot where the oracle probe is running
  • profiles: > 51 on the Linux machine, 55+ connections
  • size of the oracle.cfg on the Linux machine is ~11MB
  • Oracle 11g and/or 12c database instances are being monitored
  • Oracle cluster and/or single instances (probe running on single instance RHEL)




Oracle 12c client has a known memory leak as per Oracle Support.

Memory leak is between 110-120k per Oracle client session (connection) when using the oracle probe.

1. Install Oracle client (11g libraries are installed as part of the client install.) The 12c libs were still in place.

2. The Robot environment had to be configured for the 11g client.

For example: 

variable name               variable value

LD_LIBRARY_PATH  /orah4/product/ 
ORACLE_BASE         /orabase 
ORACLE_HOME        /orah4/product/ 
PATH                          /orah4/product/$PATH

3. Cold start the oracle probe (Deactivate-Activate)

The memory leak issue should be averted.

Additional Information

The Oracle SR number is:


Please also refer to the oracle probe Help doc:


1558699828863000004263_sktwi1f5rjvs16ou4.jpeg get_app