This readme file provides information about the 7.5-TIV-TAD4D-IF0004 interim fix for IBM® Tivoli® Asset Discovery for Distributed version 7.5. It contains the most current information for the interim fix and takes precedence over other documentation. Review this readme file thoroughly before you install or use the interim fix.
| APAR | Abstract | Description | Available since |
|---|---|---|---|
| IV27943 | AGENT INSTALLER FOR INTERIM FIX OFFERS LANGUAGE SELECTION | Interim fix can be only installed in English. Language selection is not supported in the wizard. | Interim fix 4 |
| IV28037 | DESCRIPTION FIELD IS SKIPPED DURING IMPORT | The view custom.signature_v has a field called Description. For every row in the table, the field is empty although it should not be. For more details, go to: https://www-304.ibm.com/support/entdocview.wss?uid=swg1IV28037. | Interim fix 4 |
| IV29120 | INCORRECT TRANSLATION ON VMMANAGERS PANEL | A label on the VM managers panel is incorrectly translated to French. For more details, go to: https://www-304.ibm.com/support/entdocview.wss?uid=swg1IV29120. | Interim fix 4 |
| IV29627 | ILMT 7.5 INSTALLS /ETC/IBM/TIVOLI/COMMON/CFG/LOG.PROPERTIES WITH PERMISSIN 700 (ON SOLARIS 10) | After installing Tivoli Asset Discovery for Distributed 7.5 on clean Solaris 10, the file /etc/ibm/tivoli/common/cfg/log.properties is installed with right permission 644. For more details, go to: https://www-304.ibm.com/support/entdocview.wss?uid=swg1IV29627. | Interim fix 4 |
| IV29921 | ILMT AGENT CANNOT BE INSTALLED ON HP-UX 11I V3 DUE TO 'HPVM-GUEST' CHANGE TO 'VIRTUALBASE' | Tivoli Asset Discovery for Distributed agent cannot be installed on HP-UX 11i v3 (September 2012). | Interim fix 4 |
| IV29984 | REVOKE PUBLIC GRANTS | One of steps during the installation of the interim fix grants public access to two tables that should not be granted this type of access. For more details, go to: https://www-304.ibm.com/support/entdocview.wss?uid=swg1IV29984. | Interim fix 4 |
| IV30409 | VMWARE AGENTS IN PENDING STATUS | If an invalid URL is defined or the VMware machine is incorrectly configured, the Tivoli Asset Discovery for Distributed server hangs when it attempts to connect to the machine, even though the timeout period was correctly configured. Such attempts of connection block the timer on which the VMware Connection task is running (Timer3). If the connection takes twice the amount of time that was defined as the timeout period, the connection thread is broken and the status of the VM manager is changed to Hard timeout - suspended. This status indicates that no further attempts of connection to the particular VM manager are made until its status is manually changed to Pending. | Interim fix 4 |
| IV31063 | INSTALLING TAD4D AGENTS VIA TCM WILL LEAVE 'YES' PROCESS COMMAND RUNNING EVEN AFTER THE AGENT IS INSTALLED SUCCESSFULLY | Installation of Tivoli Asset Discovery for Distributed agents by using Tivoli Configuration Manager leaves the yes process command running even after the agent is successfully installed and the process is manually ended after the installation. | Interim fix 4 |
| ID | Abstract | Description | Available since |
|---|---|---|---|
| 17909 | CPU limiter support for use scan and hardware scan | Starting from IF0004, CPU limiter support is now extended over use and hardware scans, in addition to the currently implemented support for software scan (provided in IF0001). | Interim fix 4 |
Tivoli Asset Discovery for Distributed agent contains Common Inventory Technology version 2.7.0.2021. For more details about the current changelog for Common Inventory Technology scanner, go to: https://www-304.ibm.com/support/entdocview.wss?uid=swg21612705.
Before you install the interim fix, make sure that fix pack 7.5-TIV-TAD4D-FP0001 is installed with Tivoli Asset Discovery for Distributed.
One of the steps of interim fix installation runs the SQL query that is related to granting the SYSCAT.ROLEAUTH authority. It was reported in APAR IV29154 that this step might fail when DB2® version 9.1 is used. To avoid the problem, upgrade DB2 at least to version 9.5.