Chat now with support
Chat with Support

Foglight for DB2 (Cartridge) 5.7.5.1 - 5.7.5.37 Hotfix Release Notes

Foglight for DB2 LUW 5.7.5.37 Hotfix Release Notes

Foglightâ„¢ for DB2 LUW Hotfix 5.7.5.37

Developed for Foglight Management Server 5.6.11

Hotfix Release Notes

July 14, 2017


Release 5.7.5.37 is a hotfix of Foglight for DB2 LUW 5.7.5.1, and includes the changes listed in the following sections. Quest may generate additional hotfixes for future releases of the product.

 

Topics:

 


About this hotfix

About this hotfix

This hotfix addresses issues listed in Resolved issues. The minimum version required for installing this hotfix is 5.7.5.1.

 

This hotfix may receive additional testing. If you are not severely affected by the issues that this hotfix addresses, it is recommended that you install the next full release of Foglight for DB2 LUW that includes this hotfix.

For complete product information, refer to the Foglight for DB2 LUW 5.7.5.1 product documentation.

Note: This hotfix also includes the bug fixes addressed by the previous Foglight for DB2 LUW hotfixes:

  • Foglight for DB2 LUW 5.7.5.36

 


Resolved issues

Resolved issues

The following is a list of issues resolved in this hotfix.

Defect ID

Resolved Issue

DB2FOG-57

Fix the installation failure occurred when the Foglight Management Server (which installs Foglight for DB2 LUW 5.7.5.36) is upgraded from version 5.7.5.7 to version 5.7.5.8.

Issues also resolved in the Foglight for DB2 LUW 5.7.5.36 hotfix

The following is a list of issues resolved in this hotfix.

Defect ID

Resolved Issue

FOGDG-98

The SPM installer fails to run on Windows 2016 and Windows 10.

Known issues

Known issues

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

Cartridge-related issues

Defect ID

Known Issue

FOGDG-160

[SPM installer] The Foglight for Infrastructure cartridge cannot be enabled automatically after the Foglight Management Server starts up.

GVFOG-41

Fail to create new agents, if HostAgent and Infrastructure are disabled.

Workaround: Install and enable HostAgent and Infrastructure manually.

GVFOG-38

The global view 5.7.5.5 cannot be installed, if user upgrades the Foglight for DB2 LUW 5.7.5.35 (installed on the Management Server 5.7.5.7) to version 5.7.5.37 by using the SPM installer.

Note: This issue does not impact your existing deployment.

GVFOG-37

The Databases dashboard is missing, if user uses Foglight-5.7.5.7-FoglightForDatabases_<platform>.exe to upgrade Foglight for DB2 LUW to version 5.7.5.37 on the Management Server (which does not install the Foglight for DB2 LUW before).

Workaround: Restart the Foglight Management Server.

DB2FOG-62

The "Error executing script id=xxx" error message shows in the Management Server log, after clicking What's New.

Note: This issue does not impact your existing deployment.

DB2FOG-49

All videos related to the Foglight for DB2 LUW have been removed from YouTube.

Note: This issue does not impact your existing deployment.

DB2FOG-35

The unit in the Pool Breakdown chart under the Databases > History > Memory > Memory Summary dashboard is incorrect.

DB2FOG-33

Error message shows in the log file after clicking Whole Instance on the Databases > Overview dashboard. 

DB2FOG-28

The changes are saved automatically, even if user does not confirm the changes.

DB2FOG-45 Fails to show the Upgrade Wizard dashboard, after upgrading from the previous releases.
Workaround: Click the Upgrade Required button, and then follow on-screen instructions to complete the agent upgrade.
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.
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-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-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.
Workaround:
1. On the navigation panel, navigate to Administration > Cartridges > Cartridge Inventory.
2. Select the check box next to the DB2_OnlineHelp cartridge.
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-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-1767 Monitoring a pureScale environment does not display locks when they are performed between two members (for example, one member is locking another member).

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

Monitored environments with tablespace that have Korean characters in their name, will not be displayed correctly in the tablespaces dashboard graph.

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.

 

Foglight-related issues

Defect ID

Known Issue

FGL-19291

If the Foglight for DB2 LUW 5.7.5.36 has been installed on the Management Server 5.7.5.7, the StackOverFlow exception occurs when upgrading the Management Server to version 5.7.5.8.

FGL-19282

The Foglight Management Server fails to re-enable the cartridges that have been enabled by the Foglight for DB2 LUW.

 

Third party known issues

Defect ID

Known Issue

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:

  1. Open TCP port: 135.
    WMI by default uses the port range 1024 to 5000.

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

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

N/A

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

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

  2. Implement the instructions provided in solution SOL65870.

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.

 


Self Service Tools
Knowledge Base
Notifications & Alerts
Product Support
Software Downloads
Technical Documentation
User Forums
Video Tutorials
RSS Feed
Contact Us
Licensing Assistance
Technical Support
View All
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating