[BESAdmin-Announcements] New Release: IBM Endpoint Manager for Software Use Analysis 2.2 patch 4 Now Available!

[Announcements for BES Administrators]

Software Use Analysis 2.2 patch 4

IBM is pleased to announce that patch 4 for IBM Endpoint Manager for 
Software Use Analysis 2.2 is available.
Site version updated:  48

This readme file provides information about patch 4 for Software Use 
Analysis version 2.2. Review this file thoroughly before you install or 
use the patch. 
Note: After you apply this patch, the version of Software Use Analysis 
that is displayed in the Help > About panel will be 2.2.105. 

APARs fixed
The following table lists the APARs that are fixed in this patch. 
APAR
Symptoms
Behavior after applying the patch
Available since
IV55652
Installation of Software Use Analysis fails and the following error is 
written in the logs: 
There is not enough storage available to process the statement. 
SQLCODE=-930, SQLSTATE=57011, DRIVER=3.64.104
The problem occurs only if Endpoint Manager runs on DB2. It is caused by 
exceptional memory consumption during the ETL import. After you install 
the patch, memory consumption is reduced and the installation succeeds. 
Patch 4
IV56631
Documentation states that it is required to install the RPM scanner on AIX 
and Linux computers. However, there is no fixlet for installing the 
scanner, only for running it.
Documentation is updated to state that it is required to run the RPM 
scanner, not to install it. 
Patch 4
IV58436
Scheduled import of data from Endpoint Manager fails and the following 
error is written in the logs:
Implicit conversion from data type nvarchar to binary is not allowed.
Use the CONVERT function to run this query.
After you install the patch, the import succeeds and no error is written 
in the logs.
Patch 4
IV58438
When the software scan fails or is stopped, incomplete scan results are 
uploaded to Software Use Analysis. It might cause that incorrect 
information is displayed on the reports. 
The Initiate Scan fixlet is updated so that only complete scan results are 
uploaded to Software Use Analysis.
Patch 4
IV58515
When you log in to Software Use Analysis with Web Reports credentials, you 
are asked to log in again. 
After you install the patch, you can log in to Software Use Analysis by 
using the Web Reports credentials without the necessity of logging in 
again.
Patch 4
IV59237
After you install patch 3, import of the data fails and the following 
error is written in the logs:
Violation of PRIMARY KEY constraint 'pk_computers_scd'. 
Cannot insert duplicate key in object 'dbo.computers_scd'
After you install the patch, the import succeeds and no error is written 
in the logs.
Patch 4


Internal defects fixed
The following table lists internal defects that are fixed in this patch.

Defect number
Symptoms
Behavior after applying the patch
Available since
100073
When you delete an entry from the custom catalog, and then search the 
catalog for the deleted item before you run an import, an error is 
displayed.
After you install the patch, the following warning is displayed: 
Some deleted catalog entries were found. 
An import is required to rebuild the search indices.
In the catalog search results, the item is marked as deleted. 
Patch 4

Installing the patch
To obtain the upgrade installer, log in to the Endpoint Manager console, 
and click Sites > External Sites > IBM Software Inventory > TEM SUA 
Upgrade (2.2 patch 4).
To obtain a fresh installer for Software Use Analysis that already 
contains the fixes that are introduced in the patch, log in to the 
Endpoint Manager console, and click Sites > External Sites > IBM Software 
Inventory > Dashboards > Software Use Analytics.
Software Use Analysis patches are cumulative. To see the list of APARs and 
internal defects that were fixed in patch 4, see the attached 
sua_2.2_patch_4.html readme file. 

IEM Software Use Analysis Team
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://bigmail.bigfix.com/pipermail/besadmin-announcements/attachments/20140512/04cfbff1/attachment.html>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://bigmail.bigfix.com/pipermail/besadmin-announcements/attachments/20140512/04cfbff1/attachment-0001.html>