IBM® Tivoli® Compliance Insight Manager
Fix Pack 8.5.0-TIV-TCIM-FP005 README

©Copyright International Business Machines Corporation 2008. All rights reserved. U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

NOTE: Before using this information and the product it supports, read the general information under Notices in this document.

Date: 2008 December 19

 

About the fix pack

This fix pack corrects several problems in IBM Tivoli Compliance Insight Manager, Version 8.5.0. It requires that IBM Tivoli Compliance Insight Manager, Version 8.5.0, already be installed. After installing this fix pack, your Tivoli Compliance Insight Manager installation will be at software service level 8.5.0.5.

Patch contents and distribution

This fix pack package contains:

This fix pack is distributed as an electronic download from the IBM Software Support Web site.

Architectures

This fix pack package supports the same operating system releases as the IBM Tivoli Compliance Insight Manager 8.5 product. Refer to chapter 1 ("System Requirements") of the IBM Tivoli Compliance Insight Manager 8.5 Installation Guide for a complete list.

Fix packs superseded by this fix pack

This fix pack supersedes the Windows, AIX, HP-UX, and Solaris part of fix packs from 8.5.0-TIV-TCIM-FP001 to 8.5.0-TIV-TCIM-FP004. z/OS actuator last fix pack is 8.5.0-TIV-TCIM-FP001.

Fix pack structure

Tivoli Compliance Insight Manager supports multiple platforms; for each platform requiring updates, a separate package is installed. Each package contains the updates for all components installed on that platform.

APARs and defects fixed

The following problems are corrected by this fix pack. For more information about the APARs listed here, refer to the Tivoli Compliance Insight Manager Support site.

Problems fixed by fix pack 8.5.0-TIV-TCIM-FP005

APAR IZ31172
SYMPTOM: Aggregation process fails after a GEM database has been cleared under some circumstances.

APAR IZ16883
SYMPTOM: When adding more than one machine, the custom properties are applied only to the first event source.

APAR IZ31773
SYMPTOM: When clearing a GEM database with sliding schedule or "Map at Collect" time, subsequent loads on this database may fail with postprocessing error.

APAR IZ26004
SYMPTOM: DB2 event source collection temporarily blocks access to the database.

Internal Defect PE07400
SYMPTOM: TCIM actuators may drop connections under some special circumstances.

APAR IZ36555
SYMPTOM: Fixpack may fail to apply when the server has multiple users defined.

APAR IZ31032
SYMPTOM: Passwords generated when creating an eventsource may appear garbled.

APAR IZ27992
SYMPTOM: Mapping may be slow on some event sources.

Internal Defect PE07210
SYMPTOM: Logfile retrieval Tool doesn't show the original logs if an event source has more than 9 sublogs.

APAR IZ23381
SYMPTOM: It is not possible to login on both to management console and iView when there are more than one network adapters in the machine.

APAR IZ30569
SYMPTOM: SAP R/3 event source is not able to collect more than once a day.

APAR IZ32605
SYMPTOM: SAP Netweaver WAS ABAP 7.0 event source cannot collect UTF16 encoded logs in AIX.

APAR IZ31307
SYMPTOM: Solaris SSH login audit events are not mapped.

APAR IZ27846
SYMPTOM: No collect history for TCIM TAM 6.1 User Information Source is present.

APAR IZ25854
SYMPTOM: The "getitimgroups.jar" file is not present.

APAR IZ30928
SYMPTOM: It's not possible to have 200 ESes on a single server.

APAR IZ33813
SYMPTOM: The connection string for z/OS event source and user information source is not visible.

APAR IZ27927
SYMPTOM: The import function may create event source duplicates.

Problems fixed by fix pack 8.5.0-TIV-TCIM-FP004

APAR IZ18785
SYMPTOM: A newly created user isn't able to modify the settings in the Report Distribution even when the correct access rights were assigned to him.

APAR IZ23725
SYMPTOM: Some reports are not shown correctly to users other than CIFOWNER.

APAR IZ20152
SYMPTOM: PostProcessing takes long time for step fillUserIsRowOwner.

APAR IZ18098
SYMPTOM: iSeries mapping for deleted objects shows (user) unavailable for Who, and Object for onWhat.

Internal Defect IZ22011
SYMPTOM: Solaris Event Source does not collect all Audit Trail records.

APAR IZ20407
SYMPTOM: Collect Directory event source property is missing.

APAR IZ21023
SYMPTOM: Some Tandem events are collected more than once..

APAR IZ23051
SYMPTOM: Informix DS events with different "Who"s are grouped together.

APAR IZ16012
SYMPTOM: Notification email is not sent when multiple distribution tasks are scheduled concurrently.

APAR IZ23426
SYMPTOM: GEM_PROPERTY is not cleared before a sliding schedule.

APAR IZ23907
SYMPTOM: Empty z/OS chunks are not mapped correctly..

APAR IZ19606
SYMPTOM: All collects fail due to corruption in EPRISEDB.OBJECT table.

APAR IZ18093
SYMPTOM: Report Distribution doesn't work with a non-default EPRORADB.

Internal Defect PE06780
SYMPTOM: A "No more SearchManagers available in the pool" is shown when a new search is started.

APAR IZ23459
SYMPTOM: When two GEM names differ by an underscore character, the GEM with underscore in the name has problems when reading from the database.

APAR IZ14060
SYMPTOM: z/OS actuator runs out of memory because of a memory leak.

Internal Defect PE07120
SYMPTOM: Some iView reports don't contain report table for large (new) database

APAR IZ23664
SYMPTOM: Middleware uninstall doesn't work.

APAR IZ25201
SYMPTOM: On a grouped server installation is not possible to change the default partition to store the TCIM DB2 instance.

Problems fixed by fix pack 8.5.0-TIV-TCIM-FP003

APAR IZ26792
SYMPTOM: 8.5.0-TIV-TCIM-FP001 and 8.5.0-TIV-TCIM-FP002 don't apply on a grouped server.

Problems fixed by fix pack 8.5.0-TIV-TCIM-FP002

APAR IZ09908
SYMPTOM: Scoping shows empty report when it contains the event detail column.

APAR IZ03732
SYMPTOM: Mapping for the AIX event source is not correct.

APAR IZ19365
SYMPTOM: The WHERE or platformname is reported with the module name instead of the hostname of the Stratus machine.

APAR IZ15383
SYMPTOM: When connecting via HPUX SSH, TCIM server cannot find the gzip or sudo utilities.

APAR IZ12338
SYMPTOM: The "From where" field seems to be incorrect when Caller Domain and Target Domain are different in the Windows event source.

APAR IZ13776
SYMPTOM: Filters with EventAspect field cannot be added when creating a Summary report.

APAR IZ17154
SYMPTOM: iView dashboard shows error when creating a node grid with mode than 1000 objects.

Problems fixed by fix pack 8.5.0-TIV-TCIM-FP001


APAR IZ16064
SYMPTOM: Report distribution fails when a custom defined report contains ' symbol

APAR IZ10918
SYMPTOM: When exporting the dashboard to PDF the axis labels do not display correctly

APAR IZ14745
SYMPTOM: Informational header is missing in distributed reports

APAR IZ13138
SYMPTOM: Additional rows show up in custom report when using Aspect columns

Internal Defect PE06250
SYMPTOM: Threshold reports cannot be opened for large database

Internal Defect PE05990
SYMPTOM: In the Management Console User Management, the role "Administer Tivoli Insight Manager Users" should be listed as "Administer Tivoli Compliance Insight Manager Users"

Internal Defect PE06000
SYMPTOM: Created distribution tasks are not executed

Internal Defect PE06020
SYMPTOM: Current implementation of HistoryClean.sql and gemcln.bat can cause deadlocks if there are multiple GEMDb loading concurrently

Internal Defect PE06120
SYMPTOM: Concurrent loads of more than 6 GEM dbs, causes some of them to fail

APAR IZ05689
SYMPTOM: Mapping of TCIM mainmapper is incorrect

Internal Defect PE05960
SYMPTOM: Mapper has OutOfMemory exception when during the mapping of multiple HP-UX chunks

Internal Defect PE06230
SYMPTOM: Actuator and Agent executables showed significant memory leaks during the TCIM 8.5 performance tests

Internal Defect PE06010
SYMPTOM: Multiple stacktraces are seen in main mapper log

Internal Defect PE06040
SYMPTOM: Indexer and mapper can't find default gsl for Ubiquitous log ES while GSL scanning

Internal Defect PE06130
SYMPTOM: Mapping of sudo in linux syslog is incorrect

Internal Defect PE06240
SYMPTOM: Consolidation is slower on TCIM v8.5 than on TCIM v8.0

APAR IZ15528
SYMPTOM: Compress function (daily restart) may corrupt idx/val database files

Internal Defect PE05930
SYMPTOM: *.bcp.err, *gempst.stdout and *gemcln.stdout log files are never cleaned

Internal Defect PE06030
SYMPTOM: Perl engine generates inefficient SQL-statements

Before installing the fix pack

Be aware of the following considerations before installing this fix pack:

Prerequisites

You must already have Tivoli Compliance Insight Manager 8.5.0 and its prerequisites installed.

Fix pack package

The Fix Pack 5 package is provided as an executable file for the Microsoft Windows platform and as an archive file for each supported non-Windows platform.

 

Installing the fix pack

Installing the fix pack on Microsoft Windows systems

  1. Before installing the fix pack, close the Management Console. Otherwise, fixes for the Management Console might fail to be applied. If this problem occurs, close the Management Console and install the fix pack again.
  2. Ensure that the fix pack is installed when there is no other process in progress, such as the daily restart task or loads.
  3. It is preferable not to have iView open while applying the fix pack. If iView is open, it might become unavailable after the fix pack is applied. In that case the "IBM Tivoli Compliance Insight Manager Tomcat" service needs to be restarted.
  4. Run the 8.5.0-TIV-TCIM-Win32-FP005.exe file to install the fix pack.

    The fix pack detects all the Tivoli Compliance Insight Manager components that are installed on the system and automatically updates them.

    Note: If one or more interim fixes have already been installed on the system, the fix pack automatically detects them and takes the appropriate action to ensure they do not need to be reapplied.

Installing the fix pack on AIX

To apply the fix pack for Tivoli Compliance Insight Manager Actuator for AIX, follow these steps:

  1. Transfer the 8.5.0-TIV-TCIM-AIXPPC32-FP005.tar.gz to a temporary directory on the AIX system by using FTP in binary mode.
  2. Decompress the upgrade package:
    # gzip -dc 8.5.0-TIV-TCIM-AIXPPC32-FP005.tar.gz | tar xvf -
  3. Apply the fix pack package, (The default installation directory is assumed.)
    # ./apply.sh /usr/lpp/IBM/TCIM/actuator
  4. Verify that the Actuator agent has started by inspecting the list of active processes:
    # ps -ef | grep agent

    Note: Only one instance of the Actuator agent should be active.

Installing the fix pack on HP-UX

To apply the fix pack for Tivoli Compliance Insight Manager Actuator for HP-UX, follow these steps:

  1. Transfer the 8.5.0-TIV-TCIM-HPUXPARISC-FP005.tar.gz to a temporary directory on the HP-UX system by using FTP in binary mode.
  2. Decompress the upgrade package:
    # gzip -dc 8.5.0-TIV-TCIM-HPUXPARISC-FP005.tar.gz | tar xvf -
  3. Apply the fix pack package, (The default installation directory is assumed.)
    # ./apply.sh /opt/IBM/TCIM/actuator
  4. Verify that the Actuator agent has started by inspecting the list of active processes:
    # ps -ef | grep agent

    Note: Only one instance of the Actuator agent should be active.

Installing the fix pack on Solaris

To apply the fix pack for Tivoli Compliance Insight Manager Actuator for Solaris, follow these steps:

  1. Transfer the 8.5.0-TIV-TCIM-SolarisSparc-FP005.tar.gz to a temporary directory on the Solaris system by using FTP in binary mode.
  2. Decompress the upgrade package:
    # gzip -dc 8.5.0-TIV-TCIM-SolarisSparc-FP005.tar.gz | tar xvf -
  3. Apply the fix pack package, (The default installation directory is assumed.)
    # ./apply.sh /opt/IBM/TCIM/actuator
  4. Verify that the Actuator agent has started by inspecting the list of active processes:
    # ps -ef | grep agent

    Note: Only one instance of the Actuator agent should be active.


Documentation updates

How to roll back mitigation provided by document "Control growing DB2 audit log on Tivoli Compliance Insight Manager 8.5 Server "

After applying the fixpack, a new option named "Truncate" is present in the DB2 8-9.1 ES properties. It's set to 'yes' by default in the DB2 SelfAudit ES (the one that audits TCIM's DB2 instance) and 'no' by default for all the other ES instances. If this option is set to 'yes', TCIM will automatically prune db2audit.log after each collect, at most once an hour; the db2audit.log pruning process consists in removing logs that have already been collected, reducing the log file size. A mitigation was provided by the support document named "Control growing DB2 audit log on Tivoli Compliance Insight Manager 8.5 Server", and this fix renders the described mitigation obsolete.

To roll back the mitigation:

Remove cifdb2prune.vbs script from the scheduled tasks

From the Windows Start menu, open the Control Panel, and then "Scheduled Tasks". Delete the task that executes C:\ibm\TCIM\Tools\cifdb2prune.vbs.

Deleting cifdb2prune.vbs script

Delete the cifdb2prune.vbs file from the C:\ibm\TCIM\Tools\ folder.

Enable TCIM's db2audit.log truncation

If you are using DB2 SelfAudit ES, and want to prune the log file, you simply need to apply the fix pack; the 'Truncate' option will appear in all DB2 ES properties, and it will be set to 'yes' for the SelfAudit one, which will prune the db2audit.log as described before. If you are using other DB2 ES, and want to enable this feature, set the 'Truncate' option to 'yes' in the ES properties panel after applying the fix pack.

Note: It's highly recommended to prune "db2audit.log" periodically to keep that file small, as a large audit log file may affect the database performance.

z/OS Event Source (ES) or User Infortmation Source (UIS)

If the z/OS Event Source (ES) or User Infortmation Source (UIS) is installed in a VIPA Network Configuration, the Event Source property "Connect String" must be updated for that z/OS ES or UIS. The part of the "Connect String" 127.0.0.1 must be replaced with the IP-address of the VIPA Network Interface. Only 127.0.0.1 has to be replaced, the rest of the Connect String field value must remain unchanged. So for example, a connect string A:127.0.0.1:5994 for a machine with ip address 9.142.236.10, the string should be updated to A:9.142.236.10:5994.

Improve mapping speed in case of a big amount of hostname lookups

For experienced TCIM users only, when in doubt, please contact TCIM L2
During the mapping phase, the "gethostname" GSL operator queries the DNS for the host name corresponding to the supplied argument, which is assumed to be an IP address. Use of this operator can seriously reduce the performance of the mapper.

To solve the performance problem, it's possible to disable the "gethostname" function in "gensub.ini", at the cost of not having the reverse lookups in the mapped results.

To disable the "gethostname" function for all ESes, the following lines have to be added to <TCIM directory>\server\run\gensub.ini:

[RegexOperators]
gethostname=nl.consul.cea.gensub.scanning.regex.OperLit


It's also possible to disable the operator for a specific GSL file. To disable the function for a specific GSL file, the following lines should be added to the <TCIM directory>\server\run\gensub.ini file:

[RegexOperators.<GSL file name without the extension>]
gethostname=nl.consul.cea.gensub.scanning.regex.OperLit


For instance, the following lines will disable the "gethostname" function for FW1.gsl:

[RegexOperators.FW1]
gethostname=nl.consul.cea.gensub.scanning.regex.OperLit

Instructions to move the DB2 instance to another drive

After TCIM v85 group server is installed on a drive other than c:, the TCIM DB2 instance is installed on c:. Follow the instructions to move the DB2 instance to the right drive:

  1. Create a file called reloc.cfg with the following contents:
    	DB_NAME=CIFDB
    	DB_PATH=C:,F:
    	INSTANCE=CIFINST
    	NODENUM=0
    	STORAGE_PATH=C:,F:
    

    STORAGE_PATH variables should be taken for each case separately from the database: select * from sysibmadm.dbpaths where type='DB_STORAGE_PATH' If there are more then one storage path all them should be added.

    (Assuming the destination drive is drive F:, and the DB name/DB instance name are the default CIFDB/CIFINST.)

  2. Stop all TCIM services
  3. Execute from the command line: db2stop force
  4. Copy C:\CIFINST to D:\CIFINST with the same permissions!! (after copying add DB2ADMNS user with full control)
  5. Execute from the command line: db2start
  6. Execute from the command line: db2relocatedb -f reloc.cfg
  7. Execute from the command line: db2stop force
  8. Remove C:\CIFINST folder
  9. Execute from the command line: db2start
  10. Start TCIM sevices

Uninstalling IBM Tivoli Compliance Insight Manager components

This procedure will replace "Chapter 5. Uninstalling IBM Tivoli Compliance Insight Manager components", page 35 from the TCIM v8.5 Installation Guide

To uninstall IBM Tivoli Compliance Insight Manager to the following steps should be executed in order. (Note the steps need to be performed with a user that has local administrator privileges.)

  1. Uninstall any Management Modules that are installed, using the use the Add/Remove Programs option in Windows.
  2. You can uninstall the following Tivoli Compliance Insight Manager components, using the Add/Remove Programs option in Windows:
  3. Stop the following ITDS services from the Windows Services Panel:
  4. Navigate to the %ProgramFiles%\IBM\ldap\V6.1\sbin folder
  5. Run the following idsidrop command to drop the ITDS instance. The command must be run from the folder chosen in the previous step. In this example we assume the default ITDS instance name - "idsinst".
    MSDOS> idsidrop.cmd -I idsinst
    
    Choose option 1 : (1) - Continue and delete the directory server instance
    Subsequently, choose option 2: (2) Completely erase the database instance (and all databases).
    Subsequently, choose option 1: (1) Continue with the above actions.
    The above actions will drop the ITDS instance.
  6. Uninstall ITDS using the use the Add/Remove Programs option in Windows. This action may prompt a restart of the machine. Please choose not to perform a restart immediately, and continue with the next steps below.
  7. Uninstall ITDS DB2 instance using the use the Add/Remove Programs option in Windows.
  8. Uninstall CIF DB2 instance , using the use the Add/Remove Programs option in Windows.
  9. The following folders or files need to be removed manually after completing the above steps. (Note: E: drive was chosen as target drive for installation, idsinst refers to the ITDS instance name, CIFINST refers to the TCIM DB2 instance and IDSINST refers to the ITDS DB2 instance name):
  10. Delete the OS users cifdb2admin, db2adminitds, idsinst
       MSDOS>net user /delete cifdb2admin
       MSDOS>net user /delete db2adminitds
       MSDOS>net user /delete idsinst
       
  11. Delete the following directories
  12. Reboot the machine

RSA Authentication Manager Configuration

When configuring RSA, ensure that only RSA authentication logfiles will be found in the Eventsource Properties RSA Log directory because all files in this directory will be processed and deleted, even when these are not logfiles.

New event source property

For the following Event Sources we added an additional property 'Collect Directory':

This property could be used to specify a path to the directory where the TCIM Actuator stores its temporary files; these temporary files contain audit data created during collect before it is transferred to the log depot. The default value points to the directory /tmp. This value can be changed. Ensure that the directory exists; otherwise, collect will not start.

Note: For SSH version of the event sources, represented above, the 'Collect Directory' property is not used. The TCIM Actuator stores its temporary files in the run directory in the SSH user's home directory.

Software limitations

Installing a component after installing the fix pack

If you install a Tivoli Compliance Insight Manager component on the system after the fix pack has been applied, you must install the fix pack on that system again to ensure that all components are running at the same software service level.

Known problems and workarounds

None.

Notices

This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions; therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information that has been exchanged, should contact:

IBM Corporation
2Z4A/101
11400 Burnet Road
Austin, TX 78758
U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurement may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.


Trademarks

IBM and Tivoli are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both.

Adobe, Acrobat, Portable Document Format (PDF), and PostScript are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, other countries, or both.

Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Other company, product, and service names may be trademarks or service marks of others.