The following is a list of issues addressed and enhancements implemented in this release.
Defect ID |
Resolved Issue |
DB2FOG-513 |
Fixed an issue that "Click Test connection" is broken in Privilege dashboard during upgrade process. |
FOGDG-1323 |
Fixed an issue that the potential email notification string combination is incorrect. |
FOGDG-1298 |
Fixed an issue that failed to load the SQL-Server-Rules.csv by "AbstractRuleManagment". |
The following is a list of issues known to exist at the time of this release.
Defect ID |
Known Issue |
FOGDG-858 |
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. |
FOGDG-1030 |
Popup message is not clear enough when installing cartridge 5.9.4.10 on FMS version lower than 5.9.2. |
DB2FOG-431 |
In Upgrade Wizard, when upgrade finishes (click "Finish" button), there will be low chance that the page will navigate back to the beginning of the Wizard. |
DB2FOG-428 |
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). |
DB2FOG-424 |
The popup message is not clear enough to tell the reason when it fails to install cartridge 5.9.4.10 on FMS version lower than 5.9.2. |
DB2FOG-406 |
DB2 UnixAgentPlus needs to be deleted before adding new DB2 UnixAgent when upgrading DB2 cartridge to 5.9.4.10. |
DB2FOG-345 |
DB2 SQL Performance doesn't support DB2 version lower than v9.7.0.10 (excluding 9.7.0.10). |
DB2FOG-175 |
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. Workaround: Do the following: 1. Navigate to the Administration > Rules & Notifications > Manage Registry Variables dashboard. 2. Search for "DB2_Is_Fglams_Required_Upgrade". 3. Change its value to "-1". |
DB2FOG-165 |
If your DB2 version is 10.1, granting user permission may fail due to inconsistent parameter(). |
DB2FOG-88 |
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. |
DDB-5387 |
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. |
DDB-5376 |
For DB2 version 9.7 and 10.1, some statistics information about db2 background processes is not collected due to DB2 limitation. |
DDB-5146 |
The DB2 installer does not support foreign languages on Windows machine.
Once the agent was activated, the following errors may be occurred:
|
DDB-3669 |
The Foglight for DB2 LUW 5.6.5.5 Upgrade Wizard does not support the upgrade of external agents if the Agent Manager is not version 5.6.2 or later. |
DDB-2860 |
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. |
DDB-2745 |
The Memory Summary panel and the corresponding alarm display "null" when there are no child pools under a memory pool. |
DDB-2706 |
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. |
DDB-2637 |
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. |
DDB-2073 |
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. |
DDB-1671 |
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". |
GVFOG-207 |
An error log showed in FMS log for loading heatmap component in FMS version before 5.9.3. |
GVFOG-60 |
The "Error executing script" error shows in the server log, if user clicks any tab or component on the Global View. |
GVFOG-37 |
The Databases dashboard does not appear after user upgrades the Foglight for DB2 LUW to 5.7.5.37 using SPM installer. |
n/a |
Need to wait for more than ten minutes between the upgrade of the Foglight Management Server and Foglight for DB2 LUW. |
n/a |
The tasks listed below cannot be accomplished from the central Foglight Management Server (the federation master):
|
n/a |
This release of Foglight for DB2 LUW supports adding databases to existing instances only using the Databases Management view in the Databases Administration dashboard. |
n/a |
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.
|
n/a |
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. |
The following is a list of third party issues known to exist at the time of this release.
Defect ID |
Known Issue |
FOGDG-650 |
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. |
DDB-1683 |
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:
For Windows Vista and Windows Server 2008: According to Microsoft (http://support.microsoft.com/kb/929851), 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:
|
n/a |
Monitoring a DB2 instance which resides on Windows Server 2008R2 or higher requires the following workaround:
|
Defect ID |
Known Issue |
n/a |
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 http://support.microsoft.com/kb/961435/en-us. |
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 5.9.5.20 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 5.9.5.20. 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 5.9.5.20, the upgrade path will be 5.5.8 > 5.7.x > 5.7.5.x (or later) > 5.9.5.20.
Foglight for DB2 LUW 5.9.5.20 requires:
The following Foglight product versions and platforms are compatible with this release.
Product Name |
Product Version |
Platform |
Foglight Management Server |
5.9.2 5.9.3 5.9.4 5.9.5 5.9.7 |
All platforms supported by these versions of the Foglight Management Server |
Foglight Agent Manager |
5.9.2 5.9.3 5.9.4 5.9.5 5.9.7 |
All platforms supported by these versions of the Foglight Agent Manager |
Note: Foglight for DB2 LUW 5.9.5.20 is compatible with Foglight 5.9.7, however, it cannot run on Foglight 5.9.7 with FIPS-compliant mode enabled.
Before installing Foglight for DB2, ensure your system meets the following minimum hardware and software requirements:
Before installing Foglight for DB2 LUW, ensure that your system meets the 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.
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:
For information on the required privileges, refer to the Foglight for DB2 LUW Getting Started Guide.
The operating system platforms and versions of DB2 that are supported for monitoring by Foglight for DB2 LUW are the following.
9.5, 9.7, 10.1, 10.5, 11.1, 11.5.
All operating systems supported by IBM.
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.
Note: IBM® DB2® pureScale is currently not supported for Linux on IBM System z.
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).
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.
Foglight for DB2 LUW supports monitoring a workgroup edition instance.
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.
Foglight for DB2 LUW supports monitoring a pureScale environment (except on Linux on IBM System z).
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Nutzungsbedingungen Datenschutz Cookie Preference Center