Foglight for DB2 (Cartridge) 6.1.0.10

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:

Navigate to the Administration > Rules & Notifications > Manage Registry Variables dashboard.

Search for “DB2_Is_Fglams_Required_Upgrade”.

Change its value to “-1”.

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:

On the navigation panel, navigate to Administration > Cartridges > Cartridge Inventory.

Select the check box next to the DB2_OnlineHelp cartridge.

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.

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:

•

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.

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

•

Creating agents

•

Administering agents

•

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

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:

•

<installation directory>:\Quest\<FoglightAgentManager>

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.

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

Table 3. Cartridge-related issues

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

FGL-20596

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

Workaround:

When importing license into installer, change license file name to XXX.license.

Install xxx.lic after login FMS.

Change license file name to XXX.license and put it into license folder before FMS start up.

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:

Open TCP port: 135.

WMI by default uses the port range 1024 to 5000.

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.

Add the registry key, including additional ports.

•

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

•

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.

FAM-7722

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 5.9.7.1, FglAM will not check RSA/DSA key size < 2048, and the connection is non-FIPS compliant.

Workaround: Upgrade the FglAM version to 5.9.7.1 or later.

n/a

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

Browse to https://www.quest.com/support/ and log in.

Implement the instructions provided in solution SOL65870.

Windows-related issues

Table 4. Windows-related known issues
Issue 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 https://support.microsoft.com/kb/961435/en-us.

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.1.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.1.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.1.x, the upgrade path will be 5.5.8 > 5.7.x > 5.7.5.x (or later) > 5.9.7.20.

Foglight for DB2 LUW 6.1.x requires:

•

Management Server version 6.1.x

•

Agent Manager version 6.1.x

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


Product Name	Product Version	Platform
Foglight Management Server	6.1.0	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.	6.1.0	All platforms supported by this version of the Foglight Agent Manager

Please select your product:

To serve you better, please complete the Purpose of your Chat:

Recommended Solutions for Your Problem

Foglight for DB2 (Cartridge) 6.1.0.10 - Release Notes

Known issues

General Issues

Third party known issues

Upgrade and Compatibility