Please try this:
1. open the oracle probe in raw configure mode
2. go to connections
3. on the affected connections () add a key/value as below
4. timeout = 20 secs
(an example of this key is visible in sample_conn connection)
5. Increase loglevel to 5 and logsize to 30000
6. Please monitor this issue until you can see a new occurrence.
oracle Preconfiguration Requirementshttps://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/it-operations-management/ca-unified-infrastructure-management-probes/GA/alphabetical-probe-articles/oracle-oracle-database-monitoring/oracle-preconfiguration-requirements.html
If you're monitoring Oracle instances, we require the local tnsnames.ora file for the oracle client the probe is using have the entries for the instances that need to be monitored.
Check the section on controller environment variables, add and configure them.
PATH (should include the ORACLE bin directory.)
AIX requires the LIBPATH as well. oracle probe version 4.71 does not support AIX 6 and 7. You need 4.90 or higher.
Check which version of Oracle you are monitoring, if its Oracle 12c,
There is a known memory leak issue in Oracle libraries that occurs on Oracle 12c. This information is documented in probe release notes:https://docops.ca.com/ca-unified-infrastructure-management-probes/ga/en/alphabetical-probe-articles/oracle-oracle-database-monitoring/oracle-oracle-database-monitoring-release-notes
Unfortunately, there is nothing we can do at probe level to fix this. The solution we always recommend is to use the Oracle client 11g.
See also-> https://knowledge.broadcom.com/external/article?articleId=4263
Note that we do not support 32-bit oracle clients on a 64-bit OS.
The oracle client we use must MATCH the OS bit level.The oracle probe for AIX is tested and supported on AIX v7.1 but not 7.2.