Foglight ® for DB2 LUW

Release Notes

Developed and tested for Foglight Management Server 6.0.0

February 2022

These release notes provide information about the Foglight ® for DB2 LUW release.


Welcome to Foglight for DB2 LUW

Foglight ® for DB2 LUW utilizes a lightweight agent that provides real-time monitoring of all layers of an enterprise application (systems, networks, Internet, and databases) and captures pertinent infrastructure application usage, service, and availability level data used to continually assess the state of an DB2® LUW installation. Using this collected data, Foglight Management Server provides a multi-dimensional view of resource utilization for capacity planning, problem determination, and trend analysis, both real-time and historically.

These Release Notes cover the resolved issues, known issues, workarounds, and other important information about the release of Foglight for DB2 LUW. Review all sections before starting the installation.

New in this release

Version does not contain any new feature or update.

See also:

Resolved issues and enhancements

The following is a list of issues addressed and enhancements implemented in this release.

Resolved issues

Issue ID

Resolved issue


upgrade log4j libraries to 2.17.1

Issues also resolved in version, and 6.0.0

Issues resolved in version, and 6.0.0

Issue ID

Resolved issue


Fixed issue where the number of Top SQL collections was not being limited by the maximum value.


Fixed an issue where customer cannot query “DB2 general Activity” in script console.


Supported code page setting to solve the error in db2diag log raised by mismatch code page.


Fixed an issue where DB2 alarm function “set alarm configuration on selected agent” might fail due to calling a nonexistent function.


Fixed an issue when the customers have hundreds agents, the table records grow very fast. And 'registry_registry_value' and 'registry_registry_variable' take more than 1TB.


Fixed an issue where the DB agent log might print password information as Pa$$word , even if the value has been encrypted.


Fixed an issue where on-demand data connections might fail unless more TCP ports are opened.


Fixed an issue where DB2 Top Tables collection might not submit with the maximum rows defined in ASP.

Known issues

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

General Issues

General issues

Issue ID

Known issue


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.
  1. Search for “DB2_Is_Fglams_Required_Upgrade”.
  2. Change its value to “ -1 ”.


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.
  1. Select the check box next to the DB2_OnlineHelp cartridge.
  2. Click Disable to disable the cartridge.
  3. 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:

  • DB2 Host - the Physical Host the DB2 instance resides on
  • Port - DB2 port
  • User and Password for the DB2 instance
  • Monitored DB's - the associated Databases **The monitored databases secondary properties should be cloned first.
  • Monitored members - the associated partitions\members **The monitored members secondary properties should be cloned first.
  • DB2 home - DB2 home of the monitored instance

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

  • The agent will fail to detect standby (HADR) databases, so our collections will fail for those databases.
  • DB2_Log_File_Size collection will fail.
  • The agent will fail to detect number of active databases, so the metric 'con_local_dbases' in the instance activity will not be set.


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):

  • Creating agents
  • Administering agents
  • Viewing a monitored instance from the federation master which is defined under two or more federation child server.


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:

  • <installation directory>:\Quest\<FoglightAgentManager>


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.

Cartridge-related issues


Cartridge-related issues

Issue ID

Known issue


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.


When importing license into installer, change license file name to XXX.license.
  1. Install xxx.lic after login FMS.
  2. Change license file name to XXX.license and put it into license folder before FMS start up.


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:

Open TCP port: 135.

WMI by default uses the port range 1024 to 5000.

  1. Open up a range of ports above port 5000.

Port numbers below 5000 may already be in use by other applications and could cause conflicts with your DCOM applications.

It is recommended to have at least 100 ports opened, as several system services rely on these RPC ports to communicate with each other.

  1. Add the registry key, including additional ports.
  2. Use the RPCCfg.exe (Windows Resource Kits) by running: rpccfg.exe -pe 5009-5009 -d 0
  3. 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:

  • Configure the firewalls to allow traffic between servers in the dynamic port range of 49152 through 65535 (less secure).
  • Limit the port range that is used in each monitored server.


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:

Browse to and log in.
  1. Implement the instructions provided in solution SOL65870.

Windows-related issues

Windows-related known issues

Issue ID

Known issue


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

To upgrade Foglight for DB2 LUW, follow the instructions in the Managing DB2 Database Systems User and Reference Guide.

A direct upgrade to Foglight for DB2 LUW 6.0.x is only available from version 5.7.5.x or later. Customers that are running 5.7.x of the product must first upgrade to version 5.7.5.x and then upgrade to version 6.0.x. A direct upgrade to Foglight for DB2 5.7.x is only available from version 5.5.8 or later. Customers that are running earlier versions of the product must first upgrade to version 5.5.8 and then upgrade to version 5.7.x.

For example, if your Foglight for DB2 LUW is version 5.5.8 and you are going to upgrade to version 6.0.x, the upgrade path will be 5.5.8 > 5.7.x > 5.7.5.x (or later) > 6.0.x.

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

Product Name

Product Version


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

Before installing or upgrading Foglight for DB2 LUW, ensure that your system meets the following minimum hardware and software requirements:

System requirements

Before installing Foglight for DB2 LUW, ensure that your system meets the following minimum hardware and software requirements detailed in Foglight System Requirements and Platform Support Guide.

Customers running large deployments (that is, with more than 20 agents) should consult the Foglight for DB2 LUW Hardware Sizing Guide.

UNIX server and programs

The following UNIX programs must be accessible to the user logged on to the UNIX and Linux computers:

In addition, the following platform-specific programs must be available:

Required privileges

For information on the required privileges, refer to the Foglight for DB2 LUW Getting Started Guide.

Supported platforms

The operating system platforms and versions of DB2 that are supported for monitoring by Foglight for DB2 LUW are the following.

Supported DB2 versions

9.5, 9.7, 10.1, 10.5, 11.1, 11.5.

Supported Operating Systems

All operating systems supported by IBM.

Linux on IBM System z support

Foglight for DB2 LUW supports the monitoring of instances that are installed on Linux on System z. The supported monitored instance versions are the same as specified in the list above for the Linux platform.

IBM® DB2® pureScale is currently not supported for Linux on IBM System z.

HADR support

Foglight for DB2 LUW supports monitoring an environment configured to use HADR by creating agents to monitor each one of the nodes separately (applies for both primary nodes and secondary).

Physical partition

Foglight for DB2 LUW supports a physical partition. When monitoring a physical partition, ensure you create the agent using the agent installer on the coordinator host.

Workgroup edition

Foglight for DB2 LUW supports monitoring a workgroup edition instance.

OS Cluster support

Foglight for DB2 LUW supports monitoring an instance that is installed in an OS cluster environment.

To enable monitoring, follow the instructions on “Host connectivity settings” screen in the installation wizard:

  • Mark the “instance residing on an OS cluster”.
  • Make sure the virtual host name point to the virtual host name. This name will be used to install the DB2 agent and the IC agent.

pureScale support

Foglight for DB2 LUW supports monitoring a pureScale environment (except on Linux on IBM System z).


This section provides a list of references which address the most commonly faced issues relating to remote connectivity, allowing for easy troubleshooting using the vendor's information knowledge base:

Product licensing

Foglight includes a licensing capability that restricts access to those features that are defined in the license. Any Management Server installation requires a license that grants access to server-specific parts of the browser interface and the features associated with them. Foglight cartridges are also license-protected. While some cartridges are covered by the base Foglight license (such as Foglight Agent Manager cartridges and the Foglight for Infrastructure), others may require an additional license.

Foglight for DB2 LUW is covered by the base Foglight license that allows cartridges to be installed. The SQL Performance Investigator extension requires a dedicated license.

To activate a trial or a purchased commercial license:

On the navigation panel, under Dashboards, click Administration > Setup > Manage Licenses.
  1. Click Install.
  2. In the Install License dialog box, click Browse.
  3. In the file browser that appears, specify the location of the license file.
  4. In the Install License dialog box, click Install License.

Getting started with Foglight for DB2 LUW

Contents of the release package

The Foglight for DB2 LUW release package contains the following:

Installation instructions

Refer to the Foglight for DB2 LUW Getting Started Guide for installation instructions and prerequisites.

Determine your environment hardware requirements using the Foglight for DB2 LUW Hardware Sizing Guide.

Additional resources

Additional information is available from the following:


This section contains information about installing and operating this product in non-English configurations, such as those needed by customers outside of North America. This section does not replace the materials about supported platforms and configurations found elsewhere in the product documentation.

This release is Unicode-enabled and supports any character set. In this release, all product components should be configured to use the same or compatible character encodings and should be installed to use the same locale and regional options. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America, Central and Eastern Europe, Far-East Asia, Japan.

This release has the following known capabilities or limitations: The server will be enabled for Global Operation, but not localized to any particular locale.

About us

Quest creates software solutions that make the benefits of new technology real in an increasingly complex IT landscape. From database and systems management, to Active Directory and Office 365 management, and cyber security resilience, Quest helps customers solve their next IT challenge now. Around the globe, more than 130,000 companies and 95% of the Fortune 500 count on Quest to deliver proactive management and monitoring for the next enterprise initiative, find the next solution for complex Microsoft challenges and stay ahead of the next threat. Quest Software. Where next meets now. For more information, visit .

Technical support resources

Technical support is available to Quest customers with a valid maintenance contract and customers who have trial versions. You can access the Quest Support Portal at .

The Support Portal provides self-help tools you can use to solve problems quickly and independently, 24 hours a day, 365 days a year. The Support Portal enables you to:

© 2022 Quest Software Inc.


This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written permission of Quest Software Inc.

The information in this document is provided in connection with Quest Software products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest Software products. EXCEPT AS SET FORTH IN THE TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST SOFTWARE ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST SOFTWARE BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST SOFTWARE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest Software makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest Software does not make any commitment to update the information contained in this document.

If you have any questions regarding your potential use of this material, contact:

Quest Software Inc.
Attn: LEGAL Dept.
4 Polaris Way
Aliso Viejo, CA 92656

Refer to our website ( ) for regional and international office information.


Quest Software is proud of our advanced technology. Patents and pending patents may apply to this product. For the most current information about applicable patents for this product, please visit our website at .


Quest, the Quest logo, Foglight, and Where next meets now are trademarks and registered trademarks of Quest Software Inc. in the U.S.A. and other countries. For a complete list of Quest Software trademarks, please visit our website at Red Hat, JBoss, the JBoss logo, and Red Hat Enterprise Linux are registered trademarks of Red Hat, Inc. in the U.S. and other countries. CentOS is a trademark of Red Hat, Inc. in the U.S. and other countries. Fedora and the Infinity design logo are trademarks of Red Hat, Inc. Microsoft, .NET, Active Directory, Internet Explorer, Hyper-V, Office 365, SharePoint, Silverlight,SQL Server, Visual Basic, Windows, Windows Vista and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. AIX, IBM, PowerPC, PowerVM, and WebSphere are trademarks of International Business Machines Corporation, registered in many jurisdictions worldwide. Java, Oracle, Oracle Solaris, PeopleSoft, Siebel, Sun, WebLogic, and ZFS are trademarks or registered trademarks of Oracle and/or its affiliates in the United States and other countries. SPARC is a registered trademark of SPARC International, Inc. in the United States and other countries. Products bearing the SPARC trademarks are based on an architecture developed by Oracle Corporation. OpenLDAP is a registered trademark of the OpenLDAP Foundation. HP is a registered trademark that belongs to HewlettPackard Development Company, L.P. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. MySQL is a registered trademark of MySQL AB in the United States, the European Union and other countries. Novell and eDirectory are registered trademarks of Novell, Inc., in the United States and other countries. VMware, ESX, ESXi, vSphere, vCenter, vMotion, and vCloud Director are registered trademarks or trademarks of VMware, Inc. in the United States and/or other jurisdictions. Sybase is a registered trademark of Sybase, Inc. The X Window System and UNIX are registered trademarks of The Open Group. Mozilla and Firefox are registered trademarks of the Mozilla Foundation. IOS is a registered trademark or trademark of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries. Apple, iPad, iPhone, Mac OS, Safari, Swift, and Xcode are trademarks of Apple Inc., registered in the U.S. and other countries. Ubuntu is a registered trademark of Canonical Ltd. Symantec and Veritas are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. OpenSUSE, SUSE, and YAST are registered trademarks of SUSE LCC in the United States and other countries. Citrix, AppFlow, NetScaler, XenApp, and XenDesktop are trademarks of Citrix Systems, Inc. and/or one or more of its subsidiaries, and may be registered in the United States Patent and Trademark Office and in other countries. PostgreSQL is a registered trademark of the PostgreSQL Global Development Group. MariaDB is a trademark or registered trademark of MariaDB Corporation Ab in the European Union and United States of America and/or other countries. Intel, Itanium, Pentium, and Xeon are trademarks of Intel Corporation in the U.S. and/or other countries. Debian is a registered trademark of Software in the Public Interest, Inc. OpenStack is a trademark of the OpenStack Foundation. Amazon Web Services, the "Powered by Amazon Web Services" logo, and "Amazon RDS" are trademarks of, Inc. or its affiliates in the United States and/or other countries. Infobright, Infobright Community Edition and Infobright Enterprise Edition are trademarks of Infobright Inc. POLYCOM®, RealPresence® Collaboration Server, and RMX® are registered trademarks of Polycom, Inc. All other marks and names mentioned herein may be trademarks of their respective companies.




WARNING: A WARNING icon indicates a potential for property damage, personal injury, or death.




CAUTION: A CAUTION icon indicates potential damage to hardware or loss of data if instructions are not followed.




IMPORTANT NOTE , NOTE , TIP , MOBILE , or VIDEO: An information icon indicates supporting information.