After adding the DB2 instance, it is not showing in the database dashboard.
And from the agent logs:
---
com.ibm.db2.jcc.am.DisconnectNonTransientConnectionException: [jcc][t4][2030][11211][4.12.55] A communication error occurred during operations on the connection's underlying socket, socket input stream, or socket output stream. Error location: Reply.fill() - socketInputStream.read (-1). Message: Read timed out. ERRORCODE=-4499, SQLSTATE=08001
---
or
---
YYYY-MM-DD HH:MM:SS.SSS VERBOSE [http-0.0.0.0-8080-51] system._dbwc.scripts.34 - Failed to create GV Data for DB2 instance agent name - HOST-INSTANCE
java.lang.Exception: collection null is null
YYYY-MM-DD HH:MM:SS.SSS VERBOSE [http-0.0.0.0-8080-51] system._dbwc.scripts.34 - Failed to create GV Data for DB2 database name: MYDB of DB2 agent with name - HOST-INSTANCE Exception: com.quest.wcf.publicapi.code.FunctionInvocationException: Function not found:system:dbwc.292
---
CAUSE 1
DB2 instance, FMS, embedded MySQL, and FglAM installation are all on one virtual machine (VM) causing insufficient resources.
CAUSE 2
Agents are missing key properties such as hostname, database name or proper credentials.
CAUSE 3
There are duplicate DB2_Intance objects in the topology.
RESOLUTION 1
Ensure that you have met the specifications stated in the System Requirements guide for Foglight. At the time of the issue, the CPU usage is hitting 100%. After some time, the CPU usage went down and the DB2 instance showed up in the database dashboard.
Workaround
RESOLUTION 2
Ensure the agents have the correct properties set to connect to the DB2 instance and collected expected data.
RESOLUTION 3
Remove the duplicate objects if the do not have a recent update time. These can be removed from the Data Management dashboard.
NOTE: There must be a successful connection indicated in the database agent log files for the agents to be displayed in the database dashboard.
At the time of the issue, the CPU usage is hitting 100%. After some time, the CPU usage went down and the DB2 instance showed up in the database dashboard.
© 2025 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center