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. | |
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. | |
The following is a list of third party issues known to exist at the time of this release.
Workaround: Perform the procedure described in the Knowledge Article 266110. | |||||
Cannot import license into installer with license file name XXX.lic. | |||||
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: | |||||
Workaround: Upgrade the FglAM version to 5.9.7.1 or later. | |||||
|
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. |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback 이용 약관 개인정보 보호정책 Cookie Preference Center