This readme file provides information about the 7.5.0-TIV-ILMT-IF0024 interim fix for License Metric Tool 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 | Symptoms | Behavior after applying the interim fix | Package that contains the fix | Available since |
---|---|---|---|---|
IV67411 | When the stand-alone scan detects that the tlmstandalone.ini file exists, it attempts to read configuration information from this file. However, if the file is corrupted or incomplete, the following scanner errors are displayed.
|
When the tlmstandalone.ini file exists, but it does not contain valid information, it is automatically overwritten with new information. | Self-update | Interim fix 24 |
IV69566 | When the number of files in the upload folder is higher than the predefined static buffer, the License Metric Tool agent crashes or copies only some of the files. | The agent copies all files from the upload folder and does not crash. | Agent | Interim fix 24 |
IV70177 | Documentation states that ESX version 5.0, 5.1, and 5.5 is supported. However, the correct name is ESXi. | Documentation is corrected to state that the supported hypervisor is ESXi version 5.0, 5.1, and 5.5. | Online Documentation | Interim fix 24 |
IV70428 | When you use REST API to retrieve data about scan groups, the mechanism does not work for groups whose names contain underscores. | Retrieval of data works for scan groups whose names contain underscores. | Server | Interim fix 24 |
IV71207 | On IBM i, jobs that are run the by the License Metric Tool agent have a higher priority than system jobs. As a result, the agent consumes the majority of processor resources. | Priority of agent jobs is lowered. The agent does not consume that much of processor resources. | Agent | Interim fix 24 |
IV71500 | During the reassignment of software instance, shared instances are incorrectly detected which prevents you from selecting valid bundling options. | Shared instances are correctly detected. | Server | Interim fix 24 |
APAR | Symptoms | Behavior after applying the interim fix | Package that contains the fix | Available since |
---|---|---|---|---|
IV65422 | During the merge of data from stand-alone VM managers, duplicated relations between agents and computers are loaded to the database. As a result, subcapacity values are incorrectly calculated and wrong data is displayed on the Manage Software Inventory panel. | Duplicated relations are not created. Subcapacity values are correctly calculated. | Server | Interim fix 23 |
IV65929 | When you exclude an agent from the list of systems without agents, the number of unmonitored systems is not updated on the Home page. | The number of unmonitored systems is properly reported on the Home page. | Server | Interim fix 23 |
IV65966 | Automatic bundling fails due to the violation of database constraints and the following error is written in the logs. |
Automatic bundling does not fail. | Server | Interim fix 23 |
IV65983 | The ADM.RVU_PRD_AGGR_NODE_REL_V database view is missing from License Metric Tool. | The view is added. | Server | Interim fix 23 |
IV66166 | When the aggregation is not running for a long period of time, the size of the ADM.MEASURE_RAW table grows rapidly because agents repeatedly submit the same data to the server. It might influence the application performance. | If the data is not changed, it is sent to the server, but duplicates are removed and are not processed during the aggregation. The application performance is improved. | Server | Interim fix 23 |
IV66178 | Installation of the interim fix fails on computers with Turkish locale. | The installation succeeds. | Server | Interim fix 23 |
IV66770 | The Agents panel takes a lot of time to load. | The problem occurs when more than 1000 rows are displayed per page. Documentation topic Viewing agent details is updated to contain information that to avoid problems with the performance of the panel, no more than 1000 rows should be displayed at a time. | Online Documentation | Interim fix 23 |
IV67233 | DB2 that is provided with License Metric Tool uses Materialized Query Tables and query parallelism. These features should not be available under the restricted DB2 license. | To ensure that the features are not used, run the following command in the DB2 command line processor: |
Server | Interim fix 23 |
IV67352 | If a component is discovered by more than one signature, the discovery path is not displayed on the Manage Software Inventory panel. | The path is displayed on condition that the component is found in the same location by all signatures. | Server | Interim fix 23 |
IV67411 | When the stand-alone scan detects that the tlmstandalone.ini file exists, it attempts to read configuration information from this file. However, if the file is corrupted or incomplete, the following scanner errors are displayed.
|
When the tlmstandalone.ini file exists, but it does not contain valid information, it is automatically overwritten with new information. | Self-update | Interim fix 23 |
IV67418 | After the password of the NodeDefaultTrustStore of WebSphere Application Server is changed, the License Metric Tool command-line interface cannot be accessed. | Documentation topic Accessing the command-line interface is updated to contain information that when you change the password for NodeDefaultTrustStore, you must open the INSTALL_DIR/cli/config/cli.properties file, and set the value of the trustStorePassword parameter to the new password that you defined. | Online Documentation | Interim fix 23 |
IV67446 | Inventory builder fails with the out of memory error when a new software catalog is not imported regularly. | Inventory builder does not fail. | Server | Interim fix 23 |
IV67573 | After you run the command to stop the agent on a UNIX operating system, the agent is not stopped in fact. | The agent is properly stopped. | Agent | Interim fix 23 |
IV67688 | When the software signature contains a NON-ASCII character, the catalog is not downloaded by the agent and the software scan cannot be performed. | Signatures with NON-ASCII characters are properly handled. | Server | Interim fix 23 |
IV68201 | Documentation dose not provide sufficient requirements for the size and number of the DB2 transaction logs. | Documentation topic Configuring the transaction log size is updated to contain information that the following values should be used for small and medium-sized environments of up to 20000 agents:
|
Online Documentation | Interim fix 23 |
IV68455 | Documentation provides incorrect instructions for moving the TLMA database to a separate server. | Documentation topic Moving the TLMA database to a separate server is updated with a script that can be used for moving the database to a separate server. | Online Documentation | Interim fix 23 |
IV68578 | Documentation provides insufficient information about privileges that are necessary to run the License Metric Tool command-line interface. | Documentation topic Accessing the command-line interface is updated to contain information that the command-line interface must be started by using the Run as Administrator option on Windows. | Online Documentation | Interim fix 23 |
IV68699 | Installation of the agent requires administrative privileges. However, when you are installing the agent silently as a standard user, you are not prompted to provide credentials of the user with administrative privileges. As a result, when the agent is installed, it might not work properly. | When you are installing the agent in silent mode as a standard user, you are prompted to provide credentials of the user with administrative privileges. | Agent | Interim fix 23 |
IV53771 | Products are duplicated on the Components and Products panels. Some components are assigned to more than one product. | Products are not duplicated, and each component is assigned to only one product. | Server | Interim fix 22 |
IV61293 | Screen captures that are used in the procedure for migrating from proof-of-concept to production environment suggest that the migration can be performed on License Metric Tool 7.5 fix pack 1. In fact, the procedure is only applicable to the GA version of the application. | Documentation is updated to state that migrating from the proof-of-concept installation is possible only from the GA version of the application. | Online Documentation | Interim fix 22 |
IV62101 | IBM Tivoli Integration Composer fails because the AMD.NODEVM_V view is inoperative. | The view is operative and IBM Tivoli Integration Composer does not fail. | Server | Interim fix 22 |
IV62195 | Mail notifications are sent in English when the option to receive mail in a different language is enabled. | Mail notifications are sent in the specified language. | Server | Interim fix 22 |
IV62333 | Import of the software catalog fails due to the lack of disk space on a system that fulfils hardware requirements that are specified in the documentation. | Documentation is updated to contain more accurate information about the current hardware requirements. | Online Documentation | Interim fix 22 |
IV62563 | Corrupted characters are displayed on the agent installer in languages other than English. | Corrupted characters are not displayed. | Agent | Interim fix 22 |
IV63055 | Paths that contain Japanese characters cannot be excluded from software scans by using the excludedir command. The problem occurs due to wrong encoding of the software scan configuration file. | Character encoding in the configuration file is set to UTF-8. Paths that contain Japanese characters can be excluded from software scans. | Server | Interim fix 22 |
IV63953 | If an action is scheduled for 28th February on an agent, the agent consumes 100% of CPU. | The problem is related to the daylight saving time. After you apply the fix, the agent does not consume 100% of CPU. | Agent | Interim fix 22 |
IV63974 | For some specific configurations, the aggregation algorithm incorrectly calculates 0 as the number of assigned cores. It causes that aggregation results are understated. | The number of assigned cores is correctly assigned | Server | Interim fix 22 |
IV64316 | RVU products are reported both on the PVU and RVU report. | RVU products are not reported on the PVU report. | Server | Interim fix 22 |
IV64519 | Results of the initial bundling differ between various instances of License Metric Tool. | Results of the initial bundling are consistent across all instances of License Metric Tool. | Server | Interim fix 22 |
IV64557 | For agents that communicate through a proxy, the IP address of the proxy is displayed on the Agent Details panel instead of the IP address of the agent. | Proper IP address of the agent is displayed. | Server | Interim fix 22 |
IV64998 | When you start the License Metric Tool server, the identifier of the server (ADMIN_ID) is not properly read from the database. The server starts but all agents that try to communicate with the server by using the improper server identifier constantly reset their cache. | When the server identifier is incorrectly read from the database, the server does not start and information about the problem is logged. | Server | Interim fix 22 |
IV65675 | Software instances cannot be reassigned to a different report group. | Software instances can be reassigned between report groups. | Server | Interim fix 22 |
IV56711 | After the update of the catalog, automated bundling fails. | Update of the software catalog does not cause the automated bundling to fail. | Server | Interim fix 21 |
IV58934 | Instructions for changing the Java heap size on the WebSphere Administration Server do not work on the embedded version. | Documentation is updated to contain a procedure for changing the Java heap size on the embedded version of the WebSphere Administration Server. | Online Documentation | Interim fix 21 |
IV59719 | VM managers remain in the Pending state and the following exception can be found in the server logs: |
The problem is related to an error that occurs when the server fails to merge data form VM managers due to an unexpected situation, for example a server shutdown. It causes that the entire VIRT schema in the TLMA database is corrupted. After you apply the interim fix, corrupted database tables are restored and VM managers do not remain in the Pending state. | Server | Interim fix 21 |
IV59836 | Version of License Metric Tool that is displayed in PDF reports does not show the interim fix number, only the fix pack number. | Version that is displayed in PDF reports shows the interim fix number. | Server | Interim fix 21 |
IV59918 | Documentation does not provide instructions for revoking the public access to the TLMA database from the tlmsrv user. | Documentation is updated to contain information that it is not possible to revoke any access rights from the tlmsrv user. | Online Documentation | Interim fix 21 |
IV60340 | Documentation states that when you use the -dbonly option to install an interim fix, you should switch to the user who was used to install DB2. In fact, you should switch to the DB2 instance owner. | Documentation is updated to state that the user should be switched to the DB2 instance owner. | Online Documentation | Interim fix 21 |
IV56169 | In the CSV report of failed agents, the error status of a failed agent is Undefined state. | The error status is changed from Undefined state to Missing software scan. | Server | Interim fix 20 |
IV57460 | When you try to add comments to a report and sign it, the panel does not load and the License Metric Tool server times out. It causes that the report cannot be signed. | The panel loads and it is possible to sign the report. | Server | Interim fix 20 |
IV58678 | The configuration file of the VM manager data collector and documentation lack information that user credentials must be specified in the user@domain format. | Both the configuration file and the documentation are updated to contain information about the accepted format of user credentials. | Server and Online Documentation | Interim fix 20 |
IV58889 | When you change the host ID on a Solaris local zone, the local zone status is Incomplete. | Documentation is updated to contain information that changing the host ID on a local zone is not supported. The host ID on the local zone must be the same as the host ID on the global zone. | Online Documentation | Interim fix 20 |
IV58689 | Multiple instances of the License Metric Tool agent are reported as simultaneously running on an IBM® i computer. The problem usually occurs after the system reboot. | Multiple instances of the agent are no longer reported. | Agent | Interim fix 19 |
IV58087 | Documentation does not contain information about a limitation of the service providers functionality which causes that reassigning software instances between report groups might result in incorrect PVU calculations. | Documentation is updated to contain information that if you exclude any software instances from the source report group, the exclusions are lost after you reassign the instances to a different report group. | Online Documentation | Interim fix 19 |
IV56646 | Upload of late data from agents causes recalculation to fail. | Upload of late data from agents does not cause recalculation problems. | Server | Interim fix 19 |
IV56555 | After you upgrade from IBM License Metric Tool version 7.2.2, aggregation is blocked in environments where the service providers functionality is enabled. | Aggregation is not blocked in the environments where the service providers functionality is enabled. | Server | Interim fix 19 |
IV56440 | Documentation does not provide information that the 32-bit version of DB2® is not supported on SUSE Linux Enterprise Server 11. | Documentation is updated to contain information about the lack of support for the 32-bit version of DB2 on SUSE Linux Enterprise Server 11. | Online Documentation | Interim fix 19 |
IV56350 | Software scans do not start according to the schedule but on a later time. | The problem occurs because the time when the next month starts is calculated differently on the server and on agents. After you apply the interim fix, software scans are started according to the schedule. | Server | Interim fix 19 |
IV56192 | The tlm command can be run with the status option enabled, however an error is returned. Additionally, the documentation does not list the status option as a supported one. | The tlm command that is run with the status option returns correct output. Documentation is updated to list the status option as a supported one. | Agent | Interim fix 19 |
IV55480 | The value of the inventoryScanGracePeriod parameter is ignored. It causes that agents go into the Missing software scan status. | The value of the inventoryScanGracePeriod parameter is not ignored. Agent status changes if the time that is specified in the parameter is exceeded. | Server | Interim fix 19 |
IV56111 | Local zones on Solaris 10.5 are in the Incomplete status even though the status of the global zone is OK. | Local zones and the global zone are in the same status. | Server | Interim fix 18 |
IV54978 | Information about the IP address of an agent is different on the user interface and in the exported CSV file. | The information about the agent IP address is consistent. | Server | Interim fix 18 |
IV54440 | When you produce a CSV report from the Manage Software Inventory panel, each row in the CSV file is duplicated multiple times. The problem occurs when the report is generated for data that was already aggregated. | The CSV report does not contain duplicated rows. | Server | Interim fix 18 |
IV54281 | When you reassign software instances to a different report group by using REST API, the following error is displayed. |
Software instances can be reassigned between report groups by using REST API. | Server | Interim fix 18 |
IV54045 | The upgrade from IBM License Metric Tool 7.2.2 to version 7.5 fails due to an invalid registry file. The problem occurs on a Japanese version of Windows 2008 R2. | Documentation is updated to contain a procedure for substituting the invalid registry file. | Online Documentation | Interim fix 18 |
IV53338 | Invalid time stamp conversion in time zones in which the daylight saving time clock change takes place at midnight leads to recalculation problems. The following message is written in the logs. |
The time at which the daylight saving time clock change occurs does not influence recalculation. | Server | Interim fix 17 |
IV53690 | Documentation does not provide information about how to migrate from the proof-of-concept mode to the production mode. | Documentation is updated to contain information about migration from the proof-of-concept mode to the production mode. | Online Documentation | Interim fix 17 |
IV52641 | When numerous agents simultaneously upload scan results, performance of License Metric Tool is poor. | After applying the fix, the performance is improved. | Server | Interim fix 16 |
IV52309 | When the name of the zipped file that contains the server installer is changed, the installation of the server fails. | Documentation is updated to contain information that the name of the file cannot be changed as this will inevitably result in a failed installation. | Online Documentation | Interim fix 16 |
IV51510 | When applying an interim fix, instructions for providing the user name and password for the DB2 instance owner are confusing and suggest that the DB2 administrator credentials are required. In fact, credentials of the user that is provided in the square brackets is required. | Instructions clearly indicate whose credentials are required. | Server | Interim fix 16 |
IV50758 | Documentation does not provide information that the WebSphere® Application server must be managed by a user with root privileges. | Documentation is updated to contain information about the that the WebSphere Application server must be started, stopped, and configured by a user with root privileges. | Online Documentation | Interim fix 16 |
IV50622 | Import of the software catalog fails or does not complete, and the following message is displayed: |
Import of the software catalog finishes successfully. | Server | Interim fix 15 |
IV47943 | The following message contains an incorrect use of the verb: |
The message is corrected: |
Server | Interim fix 15 |
IV47646 | The software catalog is successfully imported but the agent catalog packages are not generated. The displayed catalog version is Obsolete. The problem occurs when the catalog contains a large number of custom signatures. | Agent catalog packages are generated even if the catalog contains a large number of custom signatures. Proper version of the catalog is displayed on the panel. | Server | Interim fix 15 |
IV48015 | Documentation states that to install the IBM License Metric Tool server and database on separate computers you must run the installer twice on each computer. | Documentation is updated to say that the installer must be run on both computers, once on each. | Online Documentation | Interim fix 14 |
IV47977 | Documentation does not provide information about supported number of vCenters in a vCloud environment. | Documentation is updated to contain information that the UUID of BIOS must be unique and that only one vCenter can be present in the vCloud environment. | Online Documentation | Interim fix 14 |
IV47951 | Essential periodic calculations do not occur as expected and the following information is written in the logs. |
The reason for the problem is Java™ NullPointerException. After applying the fix, calculations occur as expected. | Server | Interim fix 14 |
IV47791 | If the relationship between a product and a component in the software catalog has the type MANAGED and is marked as DELETED, the product and component are not bundled. | Catalog relationships of this type are properly bundled. | Server | Interim fix 14 |
IV47645 | The dataimp command does not allow for transferring multiple scan groups while it is possible when using the graphical user interface. | It is possible to transfer multiple scan groups by using the dataimp command. | Server | Interim fix 14 |
IV47610 | The number of days since the last signed report is not accurate. | The number of days is accurate. | Server | Interim fix 14 |
IV47604 | Import of the stand-alone scan results fails and the following message is written in the logs. The problem is caused by duplicated entries for software scan results. |
Duplicated entries are handled properly and the import of stand-alone scan results succeeds. | Server | Interim fix 14 |
IV47152 | CPU consumption significantly increases after the IBM License Metric Tool server is started and all uploads fail. | Increase of CPU consumption is less significant. | Server | Interim fix 13 |
IV46424 | Documentation states that federated repositories, local operating system, stand-alone LDAP, and stand-alone custom repository are supported for authentication with LDAP. However, only federated repositories are in compliance with requirements of Tivoli® Integrated Portal. | Documentation is updated to list only federated repository as supported for authentication with LDAP. | Online Documentation | Interim fix 13 |
IV45065 | The last expected software scan date that is displayed on the user interface and in the output of the tlmagent -cmds command is incorrect when the agent was moved to a different scan group or the agent scan group was updated. | A correct date is displayed on the user interface. However, the output of the tlmagent -cmds command cannot be immediately updated when the scan group is updated. It is because changes to scan groups are available to the agent after the period that is specified in the agentCacheRefreshInterval parameter. It is the correct behavior and thus the fix does not change it. | Server | Interim fix 13 |
IV46265 | It is not possible to exclude PVU products from pricing calculations. The following message can be found in the logs. |
PVU products can be excluded from pricing calculations. | Server | Interim fix 12 |
IV45219 | If the same Hyper-V guest is reported by different hosts, problems with agent-host relation occur. Duplicated entries are inserted in the adm.agt_vm_rel table which affects PVU calculations. | Duplicated entries are ignored and do not affect PVU calculations. | Server | Interim fix 12 |
IV45593 | Numbers of communication ports that are defined in documentation are incorrect. | Documentation is updated to contain the correct port numbers. | Online Documentation | Interim fix 12 |
IV45610 | The VM manager task fails due to incorrect handling of long names of clusters. The following exception is written in the logs. |
The acceptable length of a cluster name is changed from 100 to 200 characters. | Server | Interim fix 12 |
IV45694 | On Solaris x86 computers with HyperThreading, the number of cores on the partition exceeds the number of cores of the physical server. Although the difference does not affect any calculations, it can be seen on the Processors and Agent Details panel. | The number of partition and physical cores is the same. | Server | Interim fix 12 |
IV45918 | License Metric Tool installer hangs on the DB2 check step. | Due to changes in DB2, the modification level of the product identifier can contain characters from A to Z while the SQL driver expects numeric values only. Documentation is updated to contain information about versions of DB2 that do not cause the problem. | Online Documentation | Interim fix 12 |
IV45381 | On Windows 2008, the server installer does not display Japanese characters correctly. | Japanese characters are displayed correctly. | Server | Interim fix 11 |
IV44963 | Installation of an interim fix fails if a group or role tlmsrv exists in the database. | Installation succeeds regardless of whether a group or role tlmsrv exists. | Server | Interim fix 11 |
IV44845 | After installing Nmap 6, it is not possible to import its results to License Metric Tool because of differences in the XML schema. Additionally, some hosts are not displayed on the Systems without Agents panel. | The results of Nmap can be imported to License Metric Tool and all hosts are properly displayed on the Systems without Agents panel. | Server | Interim fix 11 |
IV44265 | On the Tivoli Integrated Portal console, agent information is displayed in IPv6 format instead of IPv4 format. It causes that host names for different IP addresses are spelled with different letter cases. | The information is displayed in the IPv4 format. | Server | Interim fix 11 |
IV44194 | Inactive agents are not deleted after the period that is set in the maxAgentInactivityToDelete parameter is exceeded. | Inactive agents are deleted after the specified period. | Server | Interim fix 11 |
IV44192 | Documentation is inconsistent regarding the agent default installation path on Windows. | Agent default installation path is correctly documented as %WINDIR%\iltm. | Online Documentation | Interim fix 11 |
IV44140 | Because of a missing value for the REPORT_GROUP_ID column in the ADM.PROD_INV table, replacement operation causes that the inventory builder process fails. The following information is written in the log. |
REPORT_GROUP_ID is included in the inventory builder process and the process passes. | Server | Interim fix 11 |
IV43884 | When a software catalog with numerous entries is uploaded, the inventory builder process hangs. The following messages might indicate the problem. |
Automated bundling works when a catalog with numerous entries is uploaded. | Server | Interim fix 11 |
IV43432 | License Metric Tool cannot properly handle a situation in which product licensing is changed from the RVU model to a different one. | No problems with calculating capacity occur when the licensing model of a particular software item is changed. | Server | Interim fix 11 |
IV43425 | Upgrade from License Metric Tool version 7.2.2 fails during database migration. The following error is written in the logs: |
Documentation is updated to provide the procedure for solving the problem. For more information, see: Upgrading problems. | Online Documentation | Interim fix 11 |
IV43120 | The purpose of the tlmsrv user is to authorize JDBC connection with DB2. As such, it does not require administrative privileges and does not have to be a fenced user. The minimum DB2 authority that is required for the user includes the CREATETAB, BINDADD, and CONNECT permissions. | Documentation is updated to provide information about the minimum DB2 authority. | Online Documentation | Interim fix 11 |
IV42983 | For some duplicate software instances, the date when the software was installed is later than the date when it was uninstalled or no longer discovered by the agent. Such invalid records cause discrepancies between the software that is displayed on the Manage Software Inventory panel and the software that is displayed on the Agent Details and Software Components panels. | Software information is consistent across panels. | Server | Interim fix 11 |
IV42761 | Correct information about processors is displayed on the Processors panel but it is not reflected in the audit report. The problem occurs only on Solaris systems with LDOMs and zones, and results in subcapacity equal 0. | Subcapacity is properly calculated for software that is installed on LDOMs and zones. | Server | Interim fix 11 |
IV39807 | Data from agents on LDOM is incorrectly processed. | The data is processed correctly. | Server and agent | Interim fix 11 |
IV42650 | When usage data is aggregated on the detailed level, memory and disk space consumption increases. It might lead to overload of temporary table spaces and, as a consequence, aggregation failure. | Performance is improved. No aggregation failures should occur. | Server | Interim fix 10 |
IV42610 | Processor sockets are incorrectly matched, and thus incorrect data is displayed on the Processors panel. | Processor sockets are correctly matched. | Server | Interim fix 10 |
IV39419 | Universally unique identifiers (UUIDs) must contain only lowercase letters [a - f] and digits to be accepted by IBM License Metric Tool. However, some UUIDs that exist in the application are written in uppercase. | IBM License Metric Tool accepts UUIDs written in uppercase. | Server | Interim fix 10 |
IV42828 | During the import of part numbers, only license part numbers are imported. However, it might happen that the order history does not contain initial license purchases but only subsequent subscription or support part numbers. It is possible to use these part numbers for automated bundling. | Documentation is updated to provide information how to prepare a part number file that also contains subscription and support part numbers. | Online Documentation | Interim fix 10 |
IV37659 | Performance is poor for environments with a large number of signatures per agent. | Performance is improved. | Server | Interim fix 10 |
IV40234 | After installing interim fix 8, the CUSTOM.AGENT_V view is dropped and re-created with a predefined content. Any modifications and changes to the access control list are lost and a default file is created. It inhibits carrying out administrative tasks. | Modifications and changes to the access control list are preserved. | Server | Interim fix 9 |
IV39751 | You run the db2 -vf grant.sql -td% command from the DB2 administrator command prompt and sign in to the server with Administrator privileges. Then, you start a new command prompt as an Administrator. If you try to run the update.bat file from the interim fix folder, the script fails with the request for credentials of the tlmsrv user. | The script does not request for providing credentials of the tlmsrv user and the update succeeds. | Server and self-update | Interim fix 9 |
IV38595 | The CUSTOM.AGENT_V view in the TLMA database represents the AGENT table. However, it does not contain information about the status of the agent. | Information about the status of an agent is included in the CUSTOM.AGENT_V view. | Server | Interim fix 9 |
IV38580 | If the user whose credentials were used to install License Metric Tool is not present in the environment during the installation of fix pack 1, an error is returned. | Documentation is updated to provide information about this requirement. By default, the user is tipadmin. To check the credentials of this user, open the master.tag file and find the following information: |
Online Documentation | Interim fix 9 |
IV38561 | Connection to the database is not closed and temporary tables are not deleted. Thus, the maximum number of temporary tables in DB2 is exceeded. | Connection to the database is closed and temporary tables are deleted. | Server | Interim fix 9 |
IV38475 | During the self-update of agents, agent custom location is ignored and the custom certificate as well as the settings of the tlmagent.ini table are lost. | The agents are updated to the custom location. The custom certificate and settings of the tlmagent.ini table are preserved. | Server and self-update | Interim fix 9 |
IV38356 | After running stand-alone script on AIX®, a corrupted output is generated. The plugin.properties file is missing from the compressed output and there are two files with software scan results, one of which is empty. | Correct output is generated after running the stand-alone script. | Self-update | Interim fix 9 |
IV38242 | If data is concurrently inserted to the adm.aggr_pending table, recalculation problems occur. | No recalculation problems occur when data is concurrently inserted to the adm.aggr_pending table. | Server | Interim fix 9 |
IV38454 | The procedure for migrating License Metric Tool 7.5 agents to Tivoli Asset Discovery for Distributed 7.5 agents is not clearly documented. | Documentation is updated to contain the migration information. | Online Documentation | Interim fix 9 |
IV37389 | If the System Resource Controller is not working, installation of an agent on AIX fails. | Agent is installed on AIX regardless of whether the System Resource Controller is working or not. | Agent and self-update | Interim fix 9 |
IV37491 | On i5, the /QSYS.LIB/QRCL.LIB/ directory is used to store invalid objects and data that was found by the RCLSTG tool. When the Common Inventory Technology scanner scans the directory, the scanner fails because of a failing lstat system call. | The /QSYS.LIB/QRCL.LIB/* directory is added to the software scan configuration. | Agent | Interim fix 8 |
IV37618 | The scheduled date of a software scan in the software scan history report does not match the scan date on the Agents panel. The date is improperly converted to the local zone when read from the database. | Scan dates in the software scan history report and on the Agents panel are consistent. | Server | Interim fix 8 |
IV37691 | Incorrect data that comes from the agents causes that a higher count is returned for LPAR cores than for physical cores. | Information about the number of LPAR cores and physical cores is consistent. | Server and agent | Interim fix 8 |
IV37952 | Incorrect measures are uploaded to the ADM.MEASURE table by agents with version lower than 7.2.2. | Correct measures are uploaded to the ADM.MEASURE table. | Server | Interim fix 8 |
IV37969 | Installation of a private instance of the Common Inventory Technology scanner does not work on Linux and UNIX forLicense Metric Tool versions later than 7.5 fix pack 1. | A private version of Common Inventory Technology can be used on Linux and UNIX. | Agent and self-update | Interim fix 8 |
IV37007 | Hardware scans are not able to report information about LDOMs. It is caused by the fact that Solaris API reports an LDOM as present, while it is not. | Correct information about LDOMs is reported by hardware scans. | Agent | Interim fix 8 |
IV36493 | The VIRTUAL_COMP_TYPE column in the CUSTOM.HW_COMPUTER_V database view is incorrectly described. It is stated that the view shows the state of the agent while it indicates whether the system is virtual or physical one. | Documentation is updated to provide the correct description of the column. | Online Documentation | Interim fix 8 |
IV36548 | Documentation does not list the exact versions of WebSphere Application Server Network Deployment that are supported by License Metric Tool. | Documentation is updated to provide the correct supported versions of WebSphere Application Server Network Deployment. | Online Documentation | Interim fix 8 |
IV37286 | The serial number that is returned by the ComponentID group on Solaris might be inconsistent across LDOMs. | The serial number is consistent on LDOMs. The value that is returned by the v12n_chassis_serialno parameter of libv12n.so is used. | Agent | Interim fix 8 |
IV33537 | When an agent is installed on a device that has a NIC card with at least two IP addresses, the agent might first list an address that is not the IP address that is listed in the Systems without Agents table. In such a situation the agent is not removed from the list of systems without agents. | The agent is removed from the list of systems without agents regardless of which IP address of the device is listed first. | Server | Interim fix 7 |
IV33734 | When the number of reports in the adm.ibm_report table in the TLMA database is large, accessing the View Reports panel takes a lot of time. In some cases, a blank page is displayed. | The panel loads more quickly. | Server | Interim fix 7 |
IV34672 | License Metric Tool agents version lower than 7.2.2 are not able to download configuration parameters from the License Metric Tool 7.5.0.10 server. | The agents can download configuration parameters. | Server and agent | Interim fix 7 |
IV35764 | On AIX 5.3, License Metric Tool agent installer returns the following error. However, installation completes successfully. |
The message is not displayed if the installation is successful. | Agent | Interim fix 7 |
IV35895 | Inactive LDOMs are handled incorrectly because the same information is expected from them as is expected from active LDOMs. | The amount of information that is expected from active and inactive LDOMs is differentiated. Inactive LDOMs are correctly handled. | Agent | Interim fix 7 |
IV36123 | If agent threads are started in a wrong order, agents are not able to properly handle the SIGPIPE signal. It causes that the process ends and the core is dumped. | The order in which agent threads are started does not influence handling of the SIGPIPE signal. | Agent | Interim fix 7 |
IV36130 | During the configuration of the SMTP server for notifications, the following error is returned. |
Notification is correctly sent by the server. | Server | Interim fix 7 |
IV33963 | Japanese version of the Information Center incorrectly lists Windows 2000 as an operating system supported by the agents. | Extraneous information is removed from the documentation. | Online Documentation | Interim fix 7 |
IV35878 | The Information Center incorrectly describes the LAYER_V database view. | Documentation is updated to contain the correct description. | Online Documentation | Interim fix 7 |
IV36365 | Full hardware scans do not work on virtual machines even if the scans are scheduled. | Hardware scans work on virtual machines. | Server and agent | Interim fix 7 |
IV29153 | After you import a catalog fix that changes the relationship between a component and a product form free to charged, duplicated entries for the particular component appear in the adm.prod_inv table. The entries have TYPE=10 (not charged) which causes that PVU is incorrectly calculated. | Duplicated entries that indicate that a component is free of charge are removed from the table and PVU is correctly calculated. | Server | Interim fix 6 |
IV30815 | License Metric Tool agents that are installed on OS400/i5 computer with non-English-language settings fail to start and memory-related errors can be found in the logs. | Agents start properly. | Agent | Interim fix 6 |
IV31464 | After you set up the start date and frequency of a scheduled report, the scheduler ignores the start date and applies only the frequency settings to new reports. | Both start date and frequency settings are applied to the reports. | Server | Interim fix 6 |
IV33397 | Different definitions of users are used for Microsoft Hyper-V and VMware.
|
Documentation is updated to include description of the differences in user definitions. | Online Documentation | Interim fix 6 |
IV31999 | If a month that has 31 days follows a month that has 30 days, problems with generating reports occur. | Reports are properly generated regardless of the number of days in a month. | Server | Interim fix 6 |
IV33106 | The agent init script does not support the status option as required by the Linux Standard Base Core Specification 3.1. Additionally, the implementation of the stop option that should depend on PID files(/var/run/) is not valid. | The script is compliant with the Linux Standard Base Core Specification 3.1. | Agent | Interim fix 5 |
IV32827 | Duplicate rows in the ADM.LINK table block essential periodic calculations and cause problems with autobundling. It might lead to problems with confirmation of bundling of some product instances. A general error message CODBL0004W is displayed when the problem occurs. | No duplicated rows appear in the ADM.LINK table and thus periodic calculations are not blocked. No problems with aggregation caused by the duplicated rows occur. | Server | Interim fix 5 |
IV30913 | A VM manager that accesses Hyper-V host server is in the Pending status although the results of the test connection are successful. | The status of the connection is OK. | Server | Interim fix 5 |
IV32585 | A link for downloading FITSuit that is provided in documentation directs to version 2.2.0.9 instead of the required version 2.2.0.7. | Documentation is updated to contain the correct link. | Online Documentation | Interim fix 5 |
IV32579 | Documentation does not clearly state that setting cpu_threshold parameter causes that the execution of a scan on the agent side lengthens. | Documentation is updated with the missing information. | Online Documentation | Interim fix 5 |
IV03617 | Stand-alone scripts that are generated by License Metric Tool 7.2.2.1 server still contain the old version of Common Inventory Technology scanner. The problem occurs because the version of the Common Inventory Technology scanner is not updated in the stdas_scanner.zip file. | The correct version of the Common Inventory Technology scanner is displayed. | Server and self-update | Interim fix 5 |
IV27943 | The interim fix can be only installed in English. Language selection is not supported in the wizard. | The interim fix can be installed in language version. | Agent | Interim fix 4 |
IV28037 | The Description field in the custom.signature_v view is empty for every row in the table. | The Description field is populated after the import. | Server | Interim fix 4 |
IV29120 | A label on the VM managers panel is incorrectly translated to French. It indicates that there are problems with the VM manager while there are none. | The label correctly states that there are no problems with the VM manager. | Server | Interim fix 4 |
IV29627 | After installing License Metric Tool 7.5 on Solaris 10, the file /etc/ibm/tivoli/common/cfg/log.properties is installed with right permission 644. It causes that other IBM products cannot be started. | The log.properties file has correct permissions and installation of License Metric Tool does not influence other IBM products. | Agent | Interim fix 4 |
IV29921 | License Metric Tool agent cannot be installed on HP-UX 11i v3 (September 2012). | The agent can be installed on this version of HP-UX. | Agent | Interim fix 4 |
IV29984 | During the installation of the interim fix, public access is granted to the ADM.MIG_INSTR and ADM.MIG_SCRIPT tables. | Public access is not granted to these tables. | Server | Interim fix 4 |
IV30409 | If an invalid URL is defined or the VMware computer is incorrectly configured, the License Metric Tool server hangs when attempting to connect to the computer, even though the timeout period is 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 is 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 connecting to the particular VM manager are made until its status is manually changed to Pending. | Invalid URL of a VMware computer does not block other VMware computers from being processed correctly. | Server | Interim fix 4 |
IV31063 | Installation of License Metric Tool agents by using Tivoli Configuration Manager leaves the yes process command running. The problem occurs even after the agent is installed successfully and the process is ended manually after the installation. | The installation finishes properly. | Agent | Interim fix 4 |
The following table lists internal defects that are fixed in the interim fix.
Defect number | Symptoms | Behavior after applying the interim fix | Package that contains the fix | Available since |
---|---|---|---|---|
30274 | During the update of the License Metric Tool server, steps from earlier interim fixes are repeated regardless of whether they were already applied. | Steps from earlier interim fixes that were already performed are not repeated. | Server | Interim fix 24 |
30186 | License Metric Tool uses an outdated version of GSKit. | GSKit is updated to the latest version to comply with security standards. | Agent | Interim fix 24 |
27020 | When a new agent connects to the License Metric Tool server, the CODUI7003 Internal Error message is displayed on the Agents panel. | The agent is properly connected and the error is not displayed. | Server | Interim fix 24 |
26710 | Server performance is low. | A group of database indexes is added to improve the server performance. | Server | Interim fix 24 |
26126 | Exposure to known security vulnerabilities. The details are not provided in this readme file because of security best practices. | The known security vulnerabilities are resolved. | Server and agent | Interim fix 24 |
Defect number | Symptoms | Behavior after applying the interim fix | Package that contains the fix | Available since |
---|---|---|---|---|
22449 | After a successful installation or upgrade of the agent on Windows, Program Compatibility Assistant opens and information that the program might not be installed correctly is displayed. | The information is not displayed after a successful installation or upgrade of the agent. | Agent | Interim fix 23 |
25458 | When you reinstall an agent, its version is not properly displayed on the installation wizard. | Agent version is properly displayed. | Agent | Interim fix 23 |
25613 | The TLS protocol is not enabled in the agent-server secure communication. SSL v3 is used by default. TLS is enabled only when FIPS is used on the agent side. | The TLS protocol is enabled for secure communication even if FIPS is not used. | Server and agent | Interim fix 23 |
25731 | The type of processor is not correctly matched on the zBC12 server. | The type of processor is correctly matched. | Server | Interim fix 23 |
25736 | The name of the VMManagerPollingInterval is misspelled in documentation. | The name of the parameter is correctly spelled in documentation. | Online Documentation | Interim fix 23 |
26055, 26407 | Exposure to known security vulnerabilities. The details are not provided in this readme file because of security best practices. | The known security vulnerabilities are resolved. | Server and agent | Interim fix 23 |
26202 | When the scan of shared file systems is disabled, scan results are not removed from the agent inventory. | Results of scans from shared file systems are removed from agent inventory. | Server | Interim fix 23 |
26797 | When you re-run a failed installation of the interim fix, the step that previously failed is omitted. As a result, the interim fix is not properly installed. | The interim fix is properly installed. | Server | Interim fix 23 |
26930 | The interim fix installer loops on a failed step. The installation must be forced to stop. | The installer does not loop on a failed step. | Server | Interim fix 23 |
22503 | In the agent installation launchpad, the name of the service IBM License Metric Tool and IBM Tivoli Asset Discovery for Distributed Agent is translated. Thus, it mismatches the name in the system registry. | The name of the service that is displayed in the launchpad is the same as the name in the system registry. | Agent | Interim fix 22 |
22504 | The header of the agent installation panel is corrupted in Italian. | The translation is corrected. | Agent | Interim fix 22 |
23002 | When you try to extract the agent installation package, the following message is displayed although the package is successfully extracted. |
The extraneous message is not displayed. | Agent | Interim fix 22 |
23552 | When a database schema does not have some of the required rights, License Metric Tool attempts to grant these right to a table. The procedure fails with the following error. |
When a database schema does not have all of the required rights, installation of the interim fix fails with an appropriate message. | Server | Interim fix 22 |
23815 | Connection to the VM manager fails on ESX and vCenter systems that are configured to support TLS protocol version 1.0 or higher. The problem occurs because License Metric Tool uses SSL 3.0 protocol. | Connection to the VM mangers on ESX and vCenter systems that are configured to support TLS protocol version 1.0 or higher does not fail. | Server | Interim fix 22 |
23847 | Corrupted strings are displayed on the translated versions of the agent installation panels. | No corrupted strings are displayed on the agent installation panels. | Agent | Interim fix 22 |
24567 | When you merge VM manager data that contains VM managers with empty names, the data is not merged and the NullPointerException error is written in the logs. The agent remains in the Inactive state. | VM managers with empty names are skipped during the merge. | Server | Interim fix 22 |
24612 | Information on the Agents panel incorrectly states that in order to use Powershell as the communication protocol, Microsoft PowerShell version 2.0 or higher must be installed on the computer where the License Metric Tool server is installed. | The panel text is changed to state that Powershell must be installed on the computer that is used as the VM manager data collector. | Server | Interim fix 22 |
24795 | Debugging information is not collected from VMware. | If you set the logging level to DEBUG, logging information is collected from VMware. | Server | Interim fix 22 |
21913 | Documentation about downloading and installing the unrestricted JCE policy files states that you should choose Unrestricted SDK JCE Policy files for Java 5.0 SR16, Java 6 SR13, Java 7 SR4 and later versions. In fact, you should choose Unrestricted SDK JCE Policy files for older versions of the SDK. | Documentation is updated to state that you should choose Unrestricted SDK JCE Policy files for older versions of the SDK. | Online Documentation | Interim fix 21 |
22450 | The readme file for the log collector does not contain a detailed list of all information that the collector gathers. | The readme file is updated to contain the full list of collected information. | Log collector | Interim fix 21 |
22987 | Only a part of the scan group name is displayed in PDF reports. | The entire scan group name is displayed in PDF reports. | Server | Interim fix 21 |
23529 | The user interface hangs when you try to add a VM manager to an IP address that does not exist. | The user interface does not hang. | Server | Interim fix 21 |
23534 | The option to share credentials with other hosts in the same cluster is not visible on the VM managers panel. | The option to share credentials is visible. | Server | Interim fix 21 |
23567 | A question mark sign appears instead of the copyright sign in the Chinese version of the installers for the IBM License Metric Tool server as well as the log collector. | The copyright sign is properly displayed. | Server, log collector | Interim fix 21 |
23570 | Messages CODVM0009E and CODVM0010E are not translated. | The messages are properly translated. | Server | Interim fix 21 |
23572 | Operations that you perform on the VM managers panel time out after 60 seconds. | Timeout of operations on the VM managers panel equals connection timeout and is specified in the vmManagerConnectionTimeout parameter. | Server | Interim fix 21 |
23579 | Performance of the software catalog import is low. | Performance of the software catalog import is improved by indexing the database tables. | Server | Interim fix 21 |
23683 | The agent.txt file uses improper encoding. | The file uses UTF-8 encoding. | Agent | Interim fix 21 |
23894 | It is not possible to easily determine why a certain software detection occurred as no information about software signature location is provided. | Documentation is updated to contain information that the SIGNATURE_ID column in the table with information about software instances can be used for determining which signature was used to detect the software. | Online Documentation | Interim fix 21 |
22697 | The -dbonly and -apponly options are listed as available for the installation of the self-update and log collector packages, but do not in fact apply to those packages. | The -dbonly and -apponly options are not listed as available for the self-update and log collector packages. If you specify an option that cannot be used, information that it is not supported and will be skipped is displayed. | Server | Interim fix 20 |
22779 | Although the overall status of the agent is OK, the following message is displayed on the report details panel. |
The message is displayed because some agent data was sent too late. It does not affect the overall status of the agent. After you apply the interim fix, the following message is displayed instead. |
Server | Interim fix 20 |
23022 | The copyright year that is displayed on the installer for the License Metric Tool server, agent, and log collector is incorrect. | The correct copyright year is displayed on the installers. | Agent, server, log collector, self-update | Interim fix 20 |
23094 | The procedure of installing the interim fix is not clear. | Documentation is updated to clarify the procedure. | Online Documentation | Interim fix 20 |
23282 | Documentation does not contain information about the supported configuration of SELinux. | Documentation is updated to contain information that SELinux is supported on Red Hat Enterprise Linux version 6.0 and higher with SELinux enabled in the enforcing mode with Policy version at least 24 and a targeted policy type. | Online Documentation | Interim fix 20 |
23144 | Documentation does not contain information that Korn Shell (ksh) is a prerequisite for installing the agent. | Documentation is updated to list Korn Shell as an installation prerequisite. | Online Documentation | Interim fix 20 |
23200 | After enabling the service providers feature, you can sign a single report that covers the entire period from the installation of License Metric Tool to enabling the service providers feature. However, if the feature is enabled on a day of month other than the installation of License Metric Tool, the generated report is not continuous and must be corrected manually. | The reports are continuous. | Server | Interim fix 20 |
23211 | The procedure of enabling the VM manager data collector on the side of the server is only available in the Tutorials section but is missing from the Administering section. | Documentation is updated and the procedure of enabling the VM manager data collector is also present in the Administering section. | Online Documentation | Interim fix 20 |
23263 | Documentation does not contain information that stand-alone scans must be run by a root user. | Documentation is updated to contain information that only the root user can run stand-alone scans. | Online Documentation | Interim fix 20 |
22943 | Documentation does not contain information that the X Server is needed to run the gsk7ikm script. The script checks the version of the certificate that is used for authenticating parties that are involved in secure communication. | Documentation is updated to contain information that the X Server is required to run the gsk7ikm script. | Online Documentation | Interim fix 19 |
22938 | Documentation does not contain information that Windows Hyper-V 2012 and 2012 R2 are supported virtualization technologies. | Documentation is updated to contain information about the supported virtualization technologies. | Online Documentation | Interim fix 19 |
22925 | When you run the agent installer on AIX with locale set to any language that uses the UTF-8 coding, the following message is displayed. The message is displayed even though everything works correctly. |
The extraneous message is not displayed. | Agent | Interim fix 19 |
22373 | Although a standard agent is installed on a computer, you can run a stand-alone script. Such an operation should not be allowed as it is not complaint with auditing requirements. | It is not possible to run a stand-alone script when a standard agent is installed on the computer. | Agent | Interim fix 19 |
22246 | When a virtual machine that runs on Solaris is moved from one hypervisor to another, the License Metric Tool database does not reflect this change. | The problem occurs because the assignment of the LDOM on which the VM is installed to the hypervisor is random. After you install the interim fix, the LDOM is assigned to the correct hypervisor. | Server | Interim fix 19 |
22154 | When an agent sends hardware scan results for the first time, an exception is written in the message handler logs. | The exception is not written in the message handler logs as it does not indicate a problem. | Server | Interim fix 19 |
22141 | After you upload the results of the stand-alone scan to the server, the IP address of the agent that sent the scan results is always set to 127.0.0.1. | The correct IP address of the agent is displayed on the Agent panel. | Server | Interim fix 19 |
21040 | Interim fix corrections are reapplied or skipped as a result of an incorrect procedure for verification of interim fix history in the TLMA database. | Verification procedure for interim fix verification prevents from reapplying or skipping corrections. | Server | Interim fix 19 |
20008 | Help information in the agent shell installer is displayed in English when the locale is set to Chinese. | Help is displayed in Chinese. | Agent | Interim fix 19 |
22440 | The upgrade process requires providing the user name and password to the database. License Metric Tool version and database structure are changed simultaneously via a remote connection that requires the user name and password of the database administrator. | Changes to the database structure can be done separately from the changes to the application version (also in the local JDBC connection mode where password authorization is not required). It is also possible to change the application version on a system where the database was already upgraded. The previous upgrade process is still supported on condition that the user name and password for the database owner are known. | Server | Interim fix 18 |
22388 | The CUSTOM.PROCESSOR_INFO_V database view does not contain information about the CPU frequency. | The column is added to the database view. | Server | Interim fix 18 |
22249 | The default path to the directory where the log collector output is stored contains unnecessary elements. | The unnecessary elements are removed from the default path. | Other | Interim fix 18 |
22205 | The tlmsrv user cannot select data from the CUSTOM.PROCESSOR_INFO_V database view. | The tlmsrv user is granted the right to select data from the CUSTOM.PROCESSOR_INFO_V database view. | Server | Interim fix 18 |
22139 | Service names of License Metric Tool agents differ depending on which interim fix you install. | Names of services are consistent. | Agent | Interim fix 18 |
22053 | After you set the maxSubsequentCredentialFailures parameter to 0, an unlimited number of failed attempts of logging in to the VM manager should be allowed. Instead, the connection is suspended after one failed attempt. | After you set the maxSubsequentCredentialFailures parameter to 0, an unlimited number of failed logging attempts is allowed. | Server | Interim fix 18 |
21806 | If during the installation of License Metric Tool interim fix 16 on base WebSphere Application Server in silent mode, a wrong path to the command line home directory is specified, the path is accepted but afterward the command line does not work. | Information that a wrong path to the command line home directory was specified is written in the logs. | Server | Interim fix 18 |
21532 | The size of the DB2 table considerably increases during the inventory builder phase. | The size of the DB2 table does not increase that much during the inventory builder phase. | Server | Interim fix 18 |
21224 | ACFS does not provide the overall status of interim fix installation in the logs. | The status of interim fix installation is provided in the logs. | Server, self-update | Interim fix 18 |
21918 | The License Metric Tool service description contains a typographical error: |
The typographical error is removed so that the service description is correct. | Server | Interim fix 17 |
21917 | Documentation states that each part number in the part numbers file should be separated with quotation marks. However, a part numbers file that is prepared in such a way is not properly handled by License Metric Tool. | Documentation is updated to contain information that each part number in the file should be listed in a new line without any field separator. For example: |
Online Documentation | Interim fix 17 |
21766 | Documentation does not contain information that starting from interim fix 4, the cpu_threshold parameter limits not only the CPU consumption of software scans, but also of the hardware and use scans. | Documentation is updated to contain information that the cpu_threshold parameter limits the CPU consumption of software, hardware, and use scans. | Online Documentation | Interim fix 17 |
21763 | Documentation about the Common Inventory Technology enabler is out-of-date. | Documentation is updated to contain information that the Common Inventory Technology enabler is an obsolete technology and that VM manager and VM manager data collector should be used instead. | Online Documentation | Interim fix 17 |
21724 | If more than one IP address is detected for a particular agent, including both private and public addresses, a random IP address is displayed on the agent report. | The active IP address is displayed on the agent report. | Server | Interim fix 17 |
20093 | Documentation lists only average CPU and memory requirements for the server and database. Information about maximum requirements is not provided. | Documentation is updated to provide maximum requirements. | Online Documentation | Interim fix 17 |
21691 | Documentation does not clearly state which virtualizations are supported by the VM Manager Data Collector. It also incorrectly indicates that the functionality is supported from interim fix 8. | Documentation is updated to list supported virtualization and to indicate that the functionality is supported from interim fix 15. | Online Documentation | Interim fix 16 |
21580 | Documentation does not provide a complete description of the dataimp -entity scangroup command. | Documentation is updated to include a complete description of the command. | Online Documentation | Interim fix 16 |
21366 | It is not possible to connect to an ESX server by using the VM manager. | The VM manager can connect to the ESX server. | Server | Interim fix 16 |
20921 | After upgrading the License Metric Tool server with an interim fix in silent mode, it is not possible to access the server command-line interface. The problem is caused because the interim fix is installed in a wrong directory. | It is not possible to install the interim fix in a wrong directory. The command-line interface can be accessed after upgrading the server. | Server | Interim fix 16 |
20782 | The following information is written in the server logs: |
The information is removed from the log as it does not indicate a problem. | Server | Interim fix 16 |
21491 | Documentation does not provide information that self-update packages are signed by using the public-key infrastructure (PKI). | Documentation is updated to state that PKI is used for signing self-update packages. | Online Documentation | Interim fix 15 |
21489 | Documentation does not contain full information about DB2 prerequisites. | Documentation is updated to contain a full list of DB2 prerequisites. | Online Documentation | Interim fix 15 |
21390 | When a default scan group is not set, import or export of data might causes that all scan groups are deleted. | When the default scan group is not set, it is selected by License Metric Tool. | Server | Interim fix 15 |
21275 | Documentation does not contain information that the alias of the certificate request should be lmt server. Otherwise, communication between the server and agent is not possible. | Documentation is updated to contain information about the required name of the alias. | Online Documentation | Interim fix 15 |
21153 | In the database views, some columns do not have descriptions provided. Without those descriptions, it might not be clear what information the column contains. | Descriptions are provided for all columns in the database. | Server | Interim fix 15 |
21152 | Documentation provides incomplete descriptions of some database views. | Database views are updated. | Online Documentation | Interim fix 15 |
20603 | After the agent stops and resets the cache, it does not start again. | The agent starts after the reset of the cache. | Agent | Interim fix 15 |
20747 | The comment field is missing from the ADM.AGENT_HARDWARE_STATUS.RESET_SW table. | The comment field is present in the table. | Server | Interim fix 14 |
21203 | Documentation states that Windows Server 2012 is supported from the GA version of License Metric Tool while the support starts from interim fix 3. | Documentation is updated to indicate that support starts from interim fix 3. | Online Documentation | Interim Fix 13 |
21170 | After the installation of the latest interim fix, an exception is written in the logs that it is not possible to access the SYSCAT.ROLEAUTH table. | The exception is removed from the log as it does not indicate a problem. | Server | Interim Fix 13 |
21166 | Out of memory exception is written in the logs but no additional information about the cause of the exception is provided. | When the exception is caused by automatic bundling, the following message is written in the logs. |
Server | Interim fix 13 |
21160 | During the installation of the interim fix, the grant.sql script does not grant appropriate permissions to the tlmsrv user and the installation fails. | After you run the script, the user is granted the appropriate permissions. | Server | Interim fix 13 |
21033 | Incorrect PVU value is returned by VM managers for non-QPI processors in multi-socket configuration. | The PVU value is correctly counted for non-QPI processors in multi-socket configuration. | Server | Interim fix 13 |
20989 | Interim fix installation fails when the DB2 user name contains a period, for example user.name. | User name that contains a period does not cause installation problems. | Server, self-update | Interim fix 13 |
20978 | English strings are displayed on the administration server command-line interface when the locale is set to Portuguese. | All strings on the command-line interface are displayed on Portuguese. | Server | Interim fix 13 |
20954 | Installation of the interim fix succeeds but the log contains an exception that the DB2 user tried to grant himself access to the CUSTOM.AGENT_SCAN_HISTORY_V view. | The exception is removed from the log as it does not indicate a problem. | Server | Interim fix 13 |
20938 | If a user name written in the Cyrillic alphabet is provided during the installation, the installation fails. | Documentation is updated to contain information that the user name can contain only Latin alphanumeric characters and the following special characters: |
Online Documentation | Interim fix 13 |
20889 | Documentation is not clear about the prerequisites that have to be fulfilled by a Hyper-V system that is to be used as a VM manager. | Documentation is updated to contain information that the Hyper-V Virtual Machine Management service must be installed and running on each Hyper-V system that you want to add as a VM manager. | Online Documentation | Interim fix 13 |
20976 | If the name of a cluster is longer than 255 characters, connection with the VM manager is terminated. | The name of the cluster is trimmed to 255 characters and the connection to the VM manager passes. | Server | Interim fix 12 |
20906 | After installation of the interim fix, the following exception is written in the logs. |
Instead of the exception, the following message is written in the logs. |
Server | Interim fix 12 |
20876 | Inactive agents are not activated by any services, for example software or hardware scans, but only by the plug-in service. | All services activate an inactive agent. | Server | Interim fix 12 |
20740 | During the installation of ACFS by using a version of Java lower than 1.6, the patchtool.jar file is invalid or corrupted. | ACFS uses Java that is available with License Metric Tool to avoid file corruption. | Server, self-update | Interim fix 12 |
15123 | The CUSTOM.AGENT_SCAN_HISTORY_V database view shows scan history only for agents that had problems. | The view contains information about all agents. | Server | Interim fix 12 |
20880 | After running the revoke.sql script and triggering aggregation, the following exception is written in the logs. |
The redundant message is removed from the logs. The tlmsrv user has the required privileges. | Server | Interim fix 11 |
20847 | When trying to open the agent view in Firefox or Internet Explorer, the following message is displayed. |
The agent view can be opened in the two browsers. | Server | Interim fix 11 |
20776 | Documentation does not indicate that some operating systems are supported by agents only after installing a particular interim fix. | Documentation is updated to indicate whether an interim fix is required. | Online Documentation | Interim fix 11 |
20759 | During the import of a file that contains the list of scan groups, the following message is displayed and the import fails. |
The file can be imported. | Server | Interim fix 11 |
20757 | The agent can communicate with the server, but is unable to download any files from the server, for example the software catalog. | The agent can download files from the server. | Agent | Interim fix 11 |
20755 | When trying to view the default stand-alone group in Internet Explorer, an internal error is returned. | It is possible to view the default stand-alone group in the browser. | Server | Interim fix 11 |
20746 | ACFS logs contain error messages that indicate problems with privileges assigned to the database user. | Privilege assignment is corrected. | Server | Interim fix 11 |
20744 | Description of the excludedir command is not correct. | Documentation is updated to contain a correct | Online Documentation | Interim fix 11 |
20740 | During the installation of ACFS, the path to Java 1.6 must be provided manually if an incorrect version is selected. | The correct version of Java is selected by default. | Server, self-update | Interim fix 11 |
20698 | During the upgrade of an agent that is installed in the default location from version 7.2.1 or older, the upgrade binary files should be installed in the /opt/itlm directory. The /var/itlm directory should contain only temporary files. Instead, the new agent is installed in the /opt/itlm directory, but the /opt/itlm directory still contains binary files of the previous version of the agent. | Unnecessary binary files are removed. | Agent | Interim fix 11 |
20614 | When you click a product that is not eligible for subcapacity licensing on the RVU panel, an internal error is displayed. | RVU product that is not eligible for subcapacity is displayed correctly. | Server | Interim fix 11 |
20603 | After you schedule agent self-update, the agent performs cache restart during which it stops and does not start again. | The agent starts after performing the cache restart. | Server, self-update | Interim fix 11 |
20601 | Java NullPointerException is produced when invalid parameters are passed to the command-line interface. | After applying the interim fix, a correct message is displayed. | Server | Interim fix 11 |
20583 | The command for stopping the agent does not always work. | The command works properly. | Agent | Interim fix 11 |
20545 | Some characters, for example double quotation marks, cause that an error message is displayed when the Manage Software Inventory panel is opened in a language other than English. | This problem was fixed for German in interim fix 10. In interim fix 11, the solution is improved to prevent such characters from causing that the user interface is not displayed correctly. | Server | Interim fix 11 |
20457 | During an attempt of reassigning an agent to a scan group to which it already belongs, no action should be taken. Instead, a warning message is displayed that states that the particular agent ID does not exist in the database. | A meaningful message is displayed. | Server | Interim fix 11 |
20072 | Primary and guest domains correctly report the serial number of a computer but the serial numbers of local zones are not matched correctly. | Serial numbers of local zones are matched correctly. | Server, agent | Interim fix 11 |
20051 | After reassigning a component from an RVU to a non-RVU product, the audit report should go into the Running state. After about 10 minutes it should go back to the Ready state, and reflect changes that were made. Instead, the audit report goes to the Running state, but recalculation is completed at midnight. | Recalculation is completed shortly after the component is reassigned. | Server | Interim fix 11 |
20020 | Some elements of the user interface are displayed in English or as code strings if the browser locale is set to Portuguese. | All elements of the user interface are displayed in Portuguese. | Server | Interim fix 11 |
20598 | Documentation incorrectly states that after deactivating the Unknown status of the agent, the status is no longer displayed on the user interface. However, this status is not removed. It is the desired behavior. | Documentation is updated to provide the correct description of the status. | Online Documentation | Interim fix 11 |
18451 | Unreadable entries are recorded in the agent trace.log file. | Agent trace files sometimes contain non-ASCII characters when the peer ID of an SSL connection is logged. To avoid unreadable entries in the trace.log file, the hexadecimal equivalent of the peer ID is now written to the trace file. | Agent | Interim fix 11 |
20544 | Some characters, for example double quotation marks, cause that an error is displayed on the Manage Software Inventory panel in German. | Such characters are prevented from causing that the user interface is not displayed correctly. | Server | Interim fix 10 |
20452 | ACFS fails when multiple SQL scripts with the same name are to be installed. For example, if there is a system that is migrated from version 7.2.2 where interim fix 9 is already installed (IF9.sql), the script for License Metric Tool 7.5 interim fix 9 (also IF9.sql) is also considered already installed. | During the installation, the name of the script and version of the product are checked. If they are unique, the installation succeeds. | Server | Interim fix 10 |
20447 | When the server is trying to perform agent self-upgrade on Solaris 10 x86 64-bit, problems with creating a temporary directory occur. The following message is displayed: |
The temporary directory is created. | Server, self-update | Interim fix 10 |
20463 | Subcapacity always equals 0 on Solaris systems. | Subcapacity is properly calculated on Solaris. | Server | Interim fix 9 |
20364 | The readme.txt file contains an incorrect syntax of the db2 -vf grant.sql - td% command. | The correct syntax is provided: db2 -vtd% -f grant.sql. | Server | Interim fix 9 |
20333 | When the server update is run with db2inst1 as DB2_USER, it fails on step IF6.sql and a message that the user has an insufficient grant is displayed. When grant.sql is run and tlmsrv is provided as DB2_USER, IF6.sql passes. However, the update fails on step IF9_IV38595.sql and the following message is displayed. |
No problems with authorization occur. | Self-update | Interim fix 9 |
20199 | The readme file is not contained in the 7.5.0-TIV-ILMT-TAD4D-IF000X-self_update-multi.zip package. | The file is contained in the package. | Self-update | Interim fix 9 |
20079 | When the installation of an interim fix completes, whether successfully or not, logs are nor copied to the Tivoli Common Directory. | The logs are copied to the Tivoli common directory regardless of whether the installation completed successfully or failed. | Server | Interim fix 9 |
20061 | An incorrect version of agent is displayed on the wizard on the Polish version of Windows. | The correct version of the agent is displayed. | Agent | Interim fix 9 |
20050 | An exception is produced in the logs because License Metric Tool is not able to automatically create a report in the future. The exception is a way to break the loop of generating reports. | Exception handling and the logic of report creation are correct. | Server | Interim fix 9 |
20047 | Periodic self-update from License Metric Tool version 7.2.2.2 fails on HP Itanium. | The periodic self-update works. | Server, self-update | Interim fix 9 |
20018 | If an agent is installed in a custom directory on AIX, the self-update does not work correctly. After scheduling self-update, the agent is not updated, and its files are missing from the following directories: /opt/myagent/var, and /opt/myagent/opt. | Agent self-update works correctly. | Server, self-update | Interim fix 9 |
19827 | A generic message that suggests database connection problem is displayed although the problem is caused by a mismatch between the versions of the database and server. | A message that describes the reason for the problem is displayed. | Server | Interim fix 9 |
19697 | The version of the stand-alone scanner is different from the version of interim fix. | Versions of the scanner and agent match. | Self-update | Interim fix 9 |
20132 | Documentation does not clearly state that the WinRM configuration procedure must be repeated on all hosts in a cluster. | Documentation is updated to provide the missing information. | Online Documentation | Interim fix 9 |
19235 | The procedure of reassigning agents from one scan group to another by using the agtremap command is not properly documented. Documentation does not describe how to create and name DTD documents, nor where to find information about scan group IDs. | Documentation is updated to provide the missing information. | Online Documentation | Interim fix 9 |
19313 | An agent ID that was once logged is repeated for the consecutive log entries. For example, if you stop an agent with ID 1, and then plug in an agent with ID 2, first the agent with ID 1 is logged (incorrect), and then the agent with ID 2 is logged (correct). | Logs contain correct information about agent action. | Server | Interim fix 9 |
20007 | On Linux, UTF-8 encoding is not used by default, and thus Polish characters are not displayed. | Polish characters are displayed correctly. | Server, self-update | Interim fix 8 |
20005 | An incorrect version of the agent installer is displayed on the Chinese version of Windows. | The correct version of the installer is displayed. | Agent | Interim fix 8 |
20004 | Some ACFS output messages are not globalized. | All ACFS messages are globalized. | Server, self-update | Interim fix 9 |
19997 | Documentation that describes how do disable automounting of unmounted AutoFS shares is imprecise. | Documentation is updated to provide more detailed instructions. | Online Documentation | Interim fix 8 |
19967 | Chinese characters are displayed on the home panel although the web browser locale is not set to Chinese. | Text on the home panel is displayed in the correct language. | Server, self-update | Interim fix 8 |
19966 | ACFS output messages should be displayed in Chinese but are displayed in English instead. | ACFS messages are displayed in Chinese. | Server, self-update | Interim fix 8 |
19956 | An unnecessary debugging message is displayed in the stdout in the com.ibm.license.mgmt.vmmanager.hyperv.net.HttpConnector class. | Extraneous messages are removed. | Server | Interim fix 8 |
19932 | During simultaneous processing of hardware scan data from multiple agents, the correct processor is not found in the PVU table for some computers. It causes that correct PVU value is displayed in the report but not on the Processors panel. | Correct values are displayed both in the report and on the panel. | Server | Interim fix 8 |
19646 | The status of the VM manager Hard timeout - suspended is not documented. | Documentation is updated to contain the description of the status. | Online Documentation | Interim fix 8 |
19432 | On computers that are using LDAP authentication, the setup tries to create the tlmsrv user, although such a user exists. | The setup does not attempt to create the user. | Server | Interim fix 8 |
19651 | An internal error is displayed on the user interface during generation of the stand-alone scan results. | Generation of stand-alone scan results completes successfully. | Server | Interim fix 7 |
19429 | If during a software scan, software instances with null scope (empty installation paths) are found, information about these signatures is not updated in the CUSTOM.INSTALLED_OFFERING_SIGNATURE_DETAILS_V view. | Information about such software instances is updated in the view. | Server | Interim fix 7 |
19390 | Initial scan configuration files are missing after an agent is deployed on i5/OS™. The /QIBM/ProdData/QITLM/data/scanner_default catalog is empty. | The configuration files are present in the catalog. | Agent | Interim fix 6 |
19344 | If the VM manager of a Hyper-V is added over https, and the Hyper-V host to which you are connecting does not use basic authorization, the connection fails. | Connection over https that uses basic authorization passes. | Server | Interim fix 6 |
19185 | NTLMv2 support is limited. | Support for the following NTLMv2 security features is added: extended sessions security, signing, key exchange, 56 and 128-bit encryption. | Server | Interim fix 5 |
This interim fix does not contain new enhancement.
ID | Abstract | Description | Package that contains the fix | Available since |
---|---|---|---|---|
25519 | Support for Microsoft Internet Explorer 11 | Microsoft Internet Explorer 11 can be used to access the License Metric Tool user interface.
Restriction: Enterprise Mode and Compatibility View must be enabled to use Internet Explorer 11.
|
Server | Interim fix 23 |
23148 | PVU table signed with SHA2 certificate | The PVU table is signed with the SHA2 security certificate. To use this feature, install Java SDK that supports the RSA-SHA256 algorithm (version 7.0.0-WS-WASSDK FP31 or higher). | Server | Interim fix 22 |
24456 | Agent file signed with the IBM certificate | The agent file tlmagent.exe is signed with the IBM certificate on Windows. | Agent | Interim fix 22 |
22003 | API for bundling | API for bundling is a command-line alternative to the user interface. It allows for managing the assignment of software instances to products in large environments by providing a function that can cover extensive data. You can use the API for reassigning software instances and confirming the assignment. | Server | Interim fix 21 |
22007 | Preserved bundling of upgraded products | If you confirmed the assignment of a component to a particular product, the assignment is preserved after you upgrade the component to a newer version. For example, the assignment of component DB2 9.1 to product DB2 9.1 is confirmed and you upgrade the component to version 9.5. The component DB2 9.5 is automatically bundled with product DB2 9.5. To enable the feature, set the value of the preserveBundlingForUpgraded parameter to true. |
Server | Interim fix 21 |
22986 | Upgrade of Apache Commons File Upload | Due to a security vulnerability, Apache Commons File Upload is upgraded to a newer version. | Server | Interim fix 21 |
22001 | Communication by using Microsoft PowerShell | Configuration of the Hyper-V VM manager is considerably simplified due to the possibility of using Microsoft PowerShell for communication with the Hyper-V host. | Server | Interim fix 20 |
22781 | Single report to cover the entire period from installation until service provider creation | Currently, when you enable the service providers functionality, you must sign empty audit reports for every month since the installation of License Metric Tool until the date when you enabled the functionality. After installing the interim fix, a single report is generate for the entire period. | Server | Interim fix 19 |
21996 | Improvements of the Common Inventory Technology scanner | The way in which the Common Inventory Technology scanner handles memory allocation problems is improved. It aims at eliminating the risk of an uncontrolled failure of the scanner and ensures improved error reporting. | Agent | Interim fix 19 |
20886 | ACFS verbose mode | It is possible to run ACFS in verbose mode in which only information about the result of interim fix installation is displayed. If the installation fails, additional warning and error messages are provided. The mode improves readability of information. | Server, self-update | Interim fix 19 |
13758 | Updated version of GSKit | GSKit is updated to the latest version to comply with security standards. | Agent | Interim fix 19 |
22440 | Improved procedure for the database upgrade | Changes to the database structure can be done separately from the changes to the version of License Metric Tool (also in the local JDBC connection mode where password authorization is not required). It is also possible to change the application version on a system where the database was already upgraded. The previous upgrade process is still supported on condition that the user name and password for the database owner are known. | Server, self-update, other | Interim fix 18 |
21999 | Exclusion of free components from bundling options | You can enable an option that hides software instances for which all bundling options are free of charge from the Manage Software Inventory panel. Thus, the number of possible bundling options is reduced and it is easier to properly assign software relations. | Server | Interim fix 18 |
21578 | RPM package signed with an IBM key | The RPM package can be signed with a key that is provided by IBM. | Agent, self-update | Interim fix 18 |
21425 | Scalability guide | Recommendations that can improve performance in environments that consist of over 15000 agents are added to the documentation. | Online Documentation | Interim fix 18 |
21995 | Log collector | A stand-alone tool for collecting logs that are required by the IBM support. The package that contains the tool is called: 7.5.0-TIV-ILMT-TAD4D-if_number-logCollector.zip. | Log collector | Interim fix 17 |
21427 | Server-side matching algorithm for processor brand | If a few entries from the processors table have the same brand but different number of sockets, the enhanced algorithm looks for the smallest PVU row that has the number of sockets greater than the number of discovered sockets. For example: the discovered processor is Intel Xeon CPU X7560 @ 2.27 GHz. The following three entries exist in the processors table.
|
Server | Interim fix 16 |
15567 | Indication of duplicate agent IDs in the infrastructure | Information that agents with duplicate IDs exist is discovered and logged. It allows for ensuring that every agent has a unique ID before duplicates cause problems. | Server | Interim fix 16 |
21287 | Extension of the VM manager functionality | VM Manager Data Collector is a stand-alone application that collects virtualization infrastructure capacity data. It can be deployed inside a virtualization environment that is in a network with limited connectivity. It uses License Metric Tool agents to transfer the virtualization infrastructure capacity data to the server. Packages that contain the tool are called:
|
Other | Interim fix 15 |
21115 | PROCESSOR_INFO_V database view | The view provides a summary of information about the processors and cores. | Server | Interim fix 15 |
20888 | Improvements to information about the reason of agent failure | CUSTOM.AGENT_STATUS_V database view is added to provide information about the reason of the agent failure. | Server | Interim fix 12 |
20189 | PVU matching algorithm for sockets | An enhanced algorithm matches all configurations that have the number of sockets equal to or lower than the number of sockets that is defined in the PVU table. If an exact match is not possible, the algorithm looks for the smallest PVU row that has the number of sockets greater than the number of discovered sockets. For example: three sockets are discovered. Their models, types, and vendors are properly matched in the PVU table, but there is no match for the number of sockets. However, the following three entries are found in the PVU table.
The algorithm is also supported on VM managers as it gathers all necessary data. |
Server | Interim fix 11 |
14165 | Installation of a private instance of Common Inventory Technology | A private instance of Common Inventory Technology scanner that is not shared with other software can be installed on Windows. For more information, see: http://www-304.ibm.com/support/docview.wss?uid=swg21605765. | Agent | Interim fix 8 |
18493 | AIX agent installer improvement | To fulfil compatibility requirements and AIX guidelines for software installation, changes were made to AIX agent native installer that significantly changed the way in which the agent is installed.
|
Agent | Interim fix 6 |
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). | Server, agent | Interim fix 4 |
Supported operating systems and hypervisors | Supported for | Available since |
---|---|---|
IBM i V7R2 | Agent | Interim fix 24 |
Red Hat Enterprise Linux 6.5 on Power 8 | Agent | Interim fix 23 |
SUSE Linux 11.3 on Power 8 | Agent | Interim fix 23 |
Red Hat Enterprise Linux 7 | Agent | Interim fix 23 |
Microsoft Hyper-V Server 2012 R2 | Agent | Interim fix 18 |
Fujitsu SPARC64 X | Agent | Interim fix 17 |
Oracle VM Server for SPARC 3.1 | Agent | Interim fix 16 |
Oracle VM Server for SPARC 3.0 | Agent | Interim fix 16 |
Oracle SPARC T5 | Agent | Interim fix 14 |
Oracle VM Server for SPARC 2.2 | Agent | Interim fix 11 |
Intel Itanium 9500 Poulson | Agent | Interim fix 11 |
IBM zEnterprise® zEC12 | Agent | Interim fix 10 |
RHEV-M (Red Hat Linux Virtualization Manager) 3.1 | Agent | Interim fix 10 |
Microsoft Hyper-V Server 2012 | Agent | Interim fix 8 |
ID | Symptoms | Behavior after updating the scanner | Scanner version |
---|---|---|---|
IV68409 | PVU values are incorrectly calculated for 2-socket machines running on OS/400. | PVU values are correctly calculated. | 2.7.0.2049 |
ID | Symptoms | Behavior after updating the scanner | Scanner version |
---|---|---|---|
IV65050 | Hardware scan does not return the IP address on Linux computers. | The IP address is returned. | 2.7.0.2047 |
IV66838 | The type of processor is incorrectly matched for zBC12 processors. | The type of the processor is correctly matched. | 2.7.0.2047 |
IV67496 | GPFS file systems on UNIX are recognized as local, not remote. | GPFS systems are recognized as remote. | 2.7.0.2047 |
IV67778 | The scan fails on Solaris computers that are mounted with automounter. | The scan succeeds. | 2.7.0.2047 |
IV67966 | The family and type of the processor are missing on Windows computers for Intel Core i3, i5, i7, and i9. | The family and type of the processor are properly returned. | 2.7.0.2047 |
IV65218 | The number of active cores is not properly counted on Linux x86 for AMD processors that are limited by BIOS. | The number of active cores is properly counted. | 2.7.0.2045 |
IV63635 | IP address 127.0.0.2 is discovered instead of the actual IP address of the agent on SUSE Linux. The problem occurs if loopback addresses different than 127.0.0.1 are discovered. | Loopback addresses are not contained in the scan output. The proper IP address of the agent is displayed. | 2.7.0.2044 |
IV63716 | Hardware scan reports more processors platforms than actually exist. The problem occurs on the x86 platforms that run on the AMD processor. | The problem occurs because the chip ID and core ID values are incorrectly calculated. After you install the fix, the values are properly calculated and the correct number of processors is reported. | 2.7.0.2044 |
280777 | Common Inventory Technology scanner is unable to classify drives that are mounted with automounter as local or remote. It causes that some remote shares are unnecessarily scanned. It can in turn cause degradation of the scan performance or high CPU utilization. | Common Inventory Technology scans automounter configuration to avoid situations in which some remote shares are unnecessarily scanned. | 2.7.0.2042 |
IV59084 | Hardware scan returns incorrect core and capacity values for the SPARC T3 processor for local and global zones. | Core and capacity values are properly returned for SPARC T3 processor for local and global zones. | 2.7.0.2040 |
280722.1 | Software scan fails on AIX due to improper dynamic linking. | Software scan succeeds on AIX. | 2.7.0.2038 |
280722.2 | MAE exception (std::bad_alloc) is improperly handled and the program ends with code 0 (OK) instead of 127 (OUT_OF_MEMORY) when the MAE condition occurs. | The program ends with code 127 (OUT_OF_MEMORY) when the MAE condition occurs. | 2.7.0.2038 |
280725 | Hardware scan fails on OS/400 during the retrieval of information about the IP address group. The problem occurs when two hardware scans run simultaneously. | The hardware scan succeeds on OS/400. | 2.7.0.2038 |
IV53171 | The software scan fails on Solaris because the vendor string contains non-UTF-8 characters. It is not compliant with the specified XML version. The Common Inventory Technology scanner takes the output of the pkginfo command and does not filter out the non-UTF-8 characters. | The software scan succeeds on Solaris. | 2.7.0.2035 |
IV47996 | Software scan fails on OS/400 due to the MCH1212 error in the usleep() function. The error is caused by a limitation of the usleep() function that cannot have a value greater than 1 000 000. | The software scan succeeds on OS/400. | 2.7.0.2032 |
IV37286 | The serial number that is returned by the ComponentID group on Solaris might be inconsistent across LDOMs. | The serial number is consistent on LDOMs. The value that is returned by the v12n_chassis_serialno parameter of libv12n.so is used. | 2.7.0.2029 |
278353 | The compressed XML output of the hardware scan is corrupted. | The output is not corrupted. | 2.7.0.2028 |
IV34610 | An additional IP interface that is dynamically bound to a network address by using iproute2 utilities is not properly recognized. | The additional IP address is recognized correctly. | 2.7.0.2027 |
IV33935 | NFSv3 and CIFS are reported as local drives on HP-UX. | NFSv3 and CIFS are recognized as remote drives, not local ones. | 2.7.0.2025 |
IV33463 | Inactive LDOMs are improperly reported as active on Solaris. | Inactive LDOMs are reported correctly. | 2.7.0.2024 |
IV03058 | Performance of software scans is poor on the i5 operating system. | Common Inventory Technology scanner uses a faster method of scan storage. Drivers of the REMOTE type are automatically skipped and thus the software scan performance is improved. | 2.7.0.2003 |
Before you install the interim fix, make sure that fix pack 7.5-TIV-ILMT-FP0001 is installed with License Metric Tool. For fix pack installation procedure, see the product documentation.
Because of file paths length, not all file archivers can properly extract the interim fix installer. To extract the files, use a dedicated application that handles long file paths.
If you want to update agents with a particular interim fix, ensure that the License Metric Tool server is also updated with the same version of the interim fix. The version of agents that connect to a particular server must be the same as or lower than the version of the server. The version of agents cannot be higher than the version of the server.