Chat now with support
Chat with Support

Foglight for DB2 (Cartridge) 7.1.0 - Release Notes

Known issues

General Issues


Setting User Defined Collection Credentials for DB2 will fail, when the DB2 agent name contains the character @.


DB instance is still synchronized and displayed in FMS federation master even though it is stopped for some reason and not displayed in the FMS federation child.


Popup message is not clear enough when installing cartridge on FMS version lower than 5.9.2.

Workaround: Click “Info” icon on the right corner of the page and see the warning message.


The Management Server 5.7.1 stops responding when clicking charts on the Tablespaces dashboard.

Workaround: Upgrade the Management Server to 5.7.5 or later.


If your DB2 version is 10.1, granting user permission may fail due to inconsistent parameter().


If you select either of DB_DB2, DB_DB2_UI, DB_Global_View_UI cartridges then click Reset on the Cartridge Inventory dashboard, the upgrade wizard will prompt again.


Do the following:

Navigate to the Administration > Rules & Notifications > Manage Registry Variables dashboard.
Search for “DB2_Is_Fglams_Required_Upgrade”.


DB2 SQL Performance doesn't support DB2 version lower than v9.7.0.10 (excluding


DB2 UnixAgentPlus needs to be deleted before adding new DB2 UnixAgent when upgrading DB2 cartridge to


The popup message is not clear enough to tell the reason when it fails to install cartridge on FMS version lower than 5.9.2.

Workaround: See the warning message on the right corner of the page.


If the monitored DB2 server is v9.7.0.10 or v9.7.0.11, the following metrics are not available: Memory Wait, Memory Wait Rate, pureScale Wait, pureScale Wait Rate, Total CPU Wait, Memory Wait (seconds), and pureScale Wait (seconds).


In Upgrade Wizard, when upgrade finishes (click the Finish button), there will be low chance that the page will navigate back to the beginning of the Wizard.


In fact the upgrade has already been finished after the first upgrade process. We can directly cancel the second upgrade process. Then, we can validate:

In Database GlobalView, there should be no “Upgrade Required” displayed.
In Agent Status, the agents' version should be updated.


When monitoring an instance running on Windows using a Foglight Agent Manager that is running on a non-Windows platform, open file descriptors are not closed correctly.

Workaround: On the Foglight Agent Manager machine, the “description” limit is configured to “1024”. This value should be defined as “unlimited” or to a larger number, for example “65535”.


For DB2 version below 9.7, the CPU collected and displayed for a monitored instance is the CPU for only the monitored databases under that instance. The instance CPU does not include the CPU for any databases that are under the instance and are not monitored.


When the legacy Cartridge for DB2 LUW and Foglight for DB2 LUW 5.5.x are installed on the same Foglight Management Server and you upgrade the latter to Foglight for DB2 LUW 5.6.4 or later, the online help for the legacy version is no longer available.


On the navigation panel, navigate to Administration > Cartridges > Cartridge Inventory.
Click Disable to disable the cartridge.
Click Enable to enable the cartridge.

When you are finished, both online help versions are displayed in the action panel.


If you have a Foglight for DB2 LUW agent that has never been used to collect data and you upgrade to Foglight for DB2 LUW 5.6.4 or later, you will not be able to activate and use the agent seamlessly. To activate and use the Foglight for DB2 LUW agent seamlessly, you must first create an Infrastructure agent and then manually set up resource mapping for that agent. For information on how to create an Infrastructure agent, see the Infrastructure Cartridge documentation. For information on how to set up resource mapping, see the Foglight Administration and Configuration Help.


The Memory Summary panel and the corresponding alarm display "null" when there are no child pools under a memory pool.


An Agent Manager that is installed on a Windows fail-over cluster as a service that runs on the active node cannot monitor databases that are located on the same cluster. This is an Agent Manager limitation.


The Foglight for DB2 LUW Upgrade Wizard does not support the upgrade of external agents if the Agent Manager is not version 5.6.2 or later.

Workaround: Upgrade to Foglight Management Server 5.6.4 or later.


The DB2 installer does not support foreign languages on Windows machine.

The DB2 agent should be created manually through Foglight Administration > Agent Status.

The fields that needs to be modified are:

Once the agent was activated, the following errors may be occurred:


For DB2 version 9.7 and 10.1, some statistics information about db2 background processes is not collected due to DB2 limitation.


For DB2 version 9.7 and above, the following metrics are not available due to DB2 limitations: AGENT_USR_CPU_TIME_MS, AGENT_SYS_CPU_TIME_MS, LAST_RESET.


The Databases dashboard does not appear after user upgrades the Foglight for DB2 LUW to using SPM installer.


The “Error executing script” error shows in the server log, if user clicks any tab or component on the Global View.


An error log showed in FMS log for loading heatmap component in FMS version before 5.9.3.


Need to wait for more than ten minutes between the upgrade of the Foglight Management Server and Foglight for DB2 LUW.


The tasks listed below cannot be accomplished from the central Foglight Management Server (the federation master):


This release of Foglight for DB2 LUW supports adding databases to existing instances only using the Databases Management view in the Databases Administration dashboard.


The Windows System Center Endpoint Protection (SCEP) tool and Anti-Virus Protection tools installed on Windows® may negatively impact CPU and system performance of machines running Foglight, Foglight Agent Manager, and the SQL PI repository.

To reduce resource consumption, it is highly recommended that you exclude the following directory from being scanned by the protection tools:


Anti-virus software may negatively impact the CPU and system performance of machines running Foglight. To reduce resource consumption, it is highly recommended to exclude the relevant directory, processes, and executables from being scanned by the anti-virus software. For detailed information, refer to the “Configuring anti-virus exclusion settings” in Installing Foglight on Windows with an Embedded PostgreSQL Database.


When applying an alarm template to an agent, the Inconsistent Values indication may appear. This indication can be ignored.


When upgrading Foglight, if the FMS is upgraded to version 6.0.0 and the database cartridge is not, the dashboard will display “There is no data to display”.

Workaround: When upgrading Foglight to 6.0.0, first upgrade the FMS to 6.0.0, then directly upgrade the cartridges.

Third party known issues

The following is a list of third party issues known to exist at the time of this release.



The Foglight Agent Manager (FglAM) failed to restart when upgrading DB Cartridge, which is due to “Could not obtain a deployment lock” error.

Workaround: Perform the procedure described in the Knowledge Article 266110.


Cannot import license into installer with license file name XXX.lic.



WMI-related issue

Problem: WMI support is affected by the firewall on versions of Windows prior to Windows 7.

Workaround: For Windows versions prior to Windows Server 2008/Vista, use the following steps:

Use the RPCCfg.exe (Windows Resource Kits) by running: rpccfg.exe -pe 5009-5009 -d 0
Manually add the registry keys under: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\Internet

For Windows Vista and Windows Server 2008:

According to Microsoft (, the default dynamic port range for TCP/IP has changed in these versions. The new default start port is 49152 and end port is 65535. Subsequently, monitoring instances that run under these operation systems can be carried out by using either one of the following options:


In FIPS-compliant mode, it is required to use at least 2048 RSA and DSA key size to do OS monitoring via SSH connection in DB cartridge.

When FglAM version is lower than, FglAM will not check RSA/DSA key size < 2048, and the connection is non-FIPS compliant.

Workaround: Upgrade the FglAM version to or later.


Monitoring a DB2 instance which resides on Windows Server 2008R2 or higher requires the following workaround:


Some base values are not updated when using the Win32_PerfRawData_PerfDisk_LogicalDisk WMI class to calculate performance data in Windows Vista or in Windows Server 2008, because this class does not contain the PercentDiskTime_Base metric.

Workaround: A hotfix is available on Microsoft's Web site, at

Upgrade and Compatibility

A direct upgrade to Foglight for DB2 LUW 7.1.0.x is only available from version 6.1.0.x or later. Customers that are running 5.7.5.x of the product must first upgrade to version 6.1.x and then upgrade to version 7.1.0.x.


Foglight for DB2 LUW 7.1.0 requires:

The following Foglight product versions and platforms are compatible with this release:


Foglight Management Server


All platforms supported by this version of the Foglight Management Server

Foglight Agent Manager


Note: The monitoring agents available in this version of Foglight for DB2 LUW support the Agent Manager HA failover mode. For more information about this mode, see the Agent Manager Guide.


All platforms supported by this version of the Foglight Agent Manager


System requirements

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating