Database agents appear as Active under Agent Status, but they are not displayed in the Global View Databases dashboard. The dashboard may show the message:
"There is no data to display."
No agents are listed, and the dashboard may appear blank. In some cases, screenshots will show an empty or incomplete database dashboard.
The FMS log may contain an error similar to:
dbwc.scripts.loadGVData - Failed to create MSSQL data for agent id [1444]. error: Cannot get property 'nt_version' on null object
Cause 1 (Most common) The agent has been created but has not collected any database workload metrics yet.
Cause 2: The agent has been deactivated for several days.
Cause 3: Topology duplication exists due to improper agent creation or deletion.
Cause 4: The agent is excluded due to filtering by database groups.
Cause 5: Dashboard severity filters (tiles) are hiding agents.
Cause 6: User-level access restrictions limit visibility.
Cause 7: Mixed or incompatible cartridge versions are enabled.
Cause 8: FMS restarted after license expiration, causing partial cartridge enablement.
Cause 9: The DBSS_Version_Info collection is not enabled (SQL Server only).
Cause 10: Oracle RAC nodes are not included in the dashboard agent count.
Cause 11: Database cartridge versions do not match the Global View cartridge.
Cause 12:: Corruption in Global View cartridge views.
Resolution 1:
Check the database agent log via Administration > Agents > Agent Status. Confirm whether the agent is collecting workload metrics. Once metrics are collected, the agent should appear on the dashboard.
Resolution 2:
Reactivate any inactive database agents. See KB 4229398 for details.
Resolution 3: (Most common when one or a few agents are missing)
This is likely caused by topology duplication—commonly due to creating and deleting an agent without fully removing it from the system.
Best practice is to create agents using the agent installer wizard only.
To resolve:
Go to Databases > Support Dashboard > Database Technical Support
Select the appropriate database type tab (DB2, Oracle, or SQL Server)
Use Clear Agent Data and Clear Agent Model Data for the missing agent
Do not delete the agent from Agent Status
After clearing, refresh the dashboard
Resolution 4:
In the Database Groups panel, select the All group to ensure no agents are excluded.
Resolution 5:
Severity filtering may be active.
Click on:
The All Instances tile to remove all filters
A specific database type tile to show only those agents
A severity tile (e.g., Normal) to show agents with that severity
Resolution 6:
Check user permissions. Refer to KB 4296032 on configuring access levels.
Resolution 7:
Ensure all related cartridges (e.g., DBSS_SQL_Server, DBSS_SQL_Server_UI, DB_Global_View_UI) are at the same version.
If a hotfix is involved, contact Support for a revised hotfix.
Resolution 8:
Apply a valid license and restart the FMS to re-enable all cartridge components.
Resolution 9:
Enable the DBSS_Version_Info collection for SQL Server agents.
Resolution 10:
Note that Oracle RAC nodes are not counted in the total number of agents shown on the dashboard.
Resolution 11:
Ensure cartridge versions across database technologies and Global View are consistent.
Enable the latest version of the DB_Global_View_UI cartridge.
Resolution 12:
Navigate to Administration > Cartridges > Cartridge Inventory, select the highest version of DB_Global_View_UI, and click Reset.