Chat now with support
Chat mit Support

Foglight for DB2 (Cartridge) 6.3.0 - Release Notes

Foglight ® for DB2 LUW 6.3.0

Foglight ® for DB2 LUW 6.3.0

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 6.3.0 release of Foglight for DB2 LUW. Review all sections before starting the installation.

Resolved issues and enhancements

Resolved issues and Enhancements have been published in the Foglight for Databases 6.3 Release Notes document. Please review that for more specific information.

 

Known issues

General Issues

FOM-1008

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

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.

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

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.

DB2FOG-165

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

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”.

DB2FOG-345

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

DB2FOG-406

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

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.

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

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-431

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.

Workaround:

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.

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”.

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-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.

Workaround:

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

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

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-2745

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

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-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.

Workaround: Upgrade to Foglight Management Server 5.6.4 or later.

DDB-5146

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:

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-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.

GVFOG-37

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

GVFOG-60

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

GVFOG-207

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

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.

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

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.

FOG-1758

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

n/a

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.

Self-Service-Tools
Knowledge Base
Benachrichtigungen und Warnmeldungen
Produkt-Support
Software-Downloads
Technische Dokumentationen
Benutzerforen
Videoanleitungen
RSS Feed
Kontakt
Unterstützung bei der Lizenzierung
Technische Support
Alle anzeigen
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen