APMIA Oracle Database extension is not reporting correct database name in the investigator

Products

• CA Application Performance Management Agent (APM / Wily / Introscope)
• CA Application Performance Management (APM / Wily / Introscope)
• INTROSCOPE
• DX Application Performance Management

Issue/Introduction

We have configured the  Oracle Database Database Plugin in the Infrastructure agent.

However the metric nodes for the database are reporting as null.

Environment

Release : 20.x

Component : APM Agents

Cause

The agent log also showed the following exceptions

10/19/20 01:14:42 PM BST [ERROR] [IntroscopeAgent.DBMonitor] 
java.lang.NullPointerException
 at java.lang.String.replace(String.java:2240)
 at com.ca.agent.extensions.dbmon.DBMonMetricsContext.initializeConnection(DBMonMetricsContext.java:224)
 at com.ca.agent.extensions.dbmon.commands.DBMonCheckDBAvailabilityCommand.execute(DBMonCheckDBAvailabilityCommand.java:46)
 at com.ca.agent.extensions.dbmon.DBMonChain.run(DBMonChain.java:66)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 at java.lang.Thread.run(Thread.java:748)

 

The problem was due to incorrect configuration in the bundle.properties file for the Oracle Database Extension. The profile name was defined with one value MYDATABASE

introscope.agent.dbmonitor.oracle.profiles=MYDATABASE

but the profile properties were all using the default key of db1 e.g.

introscope.agent.dbmonitor.oracle.profiles.db1.instanceName=MYDATABASE

 

Resolution

Modify the bundle.properties file and either change the profile keys to match the profile name specified or change the profile name to db1

i.e.

introscope.agent.dbmonitor.oracle.profiles=db1

or

introscope.agent.dbmonitor.oracle.profiles.MYDATABASE.instanceName=MYDATABASE

introscope.agent.dbmonitor.oracle.profiles.MYDATABASE.hostName=myhost.mydomain.com

introscope.agent.dbmonitor.oracle.profiles.MYDATABASE.port=1557

etc