![]() |
![]() |
[ Bottom of Page | Previous Page | Next Page | Contents ]
This section describes some limitations found during the usage of the IBM Tivoli Configuration Manager, Version 4.2 GA version, that were not reported in the IBM Tivoli Configuration Manager: Release Notes.
Any leaf table will have unique constraint violations, but the performance degradation is most pronounced when large numbers of rows are being inserted into the table and the number of unique rows is relatively small. This being the case, this fix specifically targets the leaf tables FILE_DESC, FILE_PATH, NATIV_SWARE, and HEADER_INFO. All other leaf tables process as before.
Leaf tables are processed by inserting first into a temporary table, then copying from the temporary table to the operational table only the records that do not already exist in the operational table. This removes unique constraint violations, because the only records inserted are rows that do not already exist. This also eliminates database rollbacks caused by too many unique constraint violations. For DB2 and MSSQL, these tables are dynamically created by the data handler. To minimize the load on the temporary tablespace, the records are processed in batches of 1000.
This fix is currently for DB2, Oracle and SQL only. Because of the way Sybase and Informix manage their temporary tables, this solution has not produced reliable results. The fixes for Sybase and Informix have been deferred for now.
For DB2, the temporary tablespace 'usertemp1' must first exist. If you are using an existing DB2 inventory database, run inv_db2_admin_patch.sql as the DB2 administrator user to create this tablespace. If you are installing a new DB2 database and using the inv_db2_admin.sql script, you do not need to run the patch script as it is now contained in the latest version of the admin script.
For Oracle, the global temporary tables persist, so they are created in the schema. Run inv_ora_fp07.sql for Inventory 4.0 or inv_ora_FP02.sql for Inventory 4.2 as the schema owner to create the temporary tables.
For SQL, no additional or admin scripts are required to enable this change.
Workaround: Add the APM_KERNEL_LINUX variable to the Tivoli environment using the odadmin environ set command.
Workaround: Use the Desktop Administrative interfaces. You can install them using the IBM Tivoli Configuration Manager Desktop CD-ROM.
Workaround 1: If you have not run the installation yet, perform the following steps:
Workaround 2: If you are currently running the installation in the Select When to Reboot to Complete the Installation dialog, re-insert the IBM Tivoli Configuration Manager Installation CD before clicking Next.
Workaround 3: If you have already performed the installation and the reboot has already occurred, run the following command from the /FRESH subdirectory of the IBM Tivoli Configuration Manager Installation CD:
setup.exe -goto loadSavedParmsAfterReboot
autoscan_active=n is_swd_inv_enabled=true Inventory-Software Distribution Integration is enabled: ythen the MS* file that is related to the database is left in the message directory.
The output file contains the following message:
FRWII0087E No Catalog '42APM002.IND(e.g.)' found in the cdrom directory '(null)'.
Workaround: First specify the required host from the Tivoli desktop, and then launch the ISMP installation program as follows:
Workaround: To turn off the JIT, disable the JAVA_COMPILER in the Tivoli environment by entering the following commands:
odadmin environ get > env.out echo JAVA_COMPILER=NONE >> env.out odadmin environ set < env.out
[ Top of Page | Previous Page | Next Page | Contents ]