Fixes are available
APAR status
Closed as program error.
Error description
Problem Description: Customer tried to import the Navigator using tacmd importNavigator command on 6.2.2 FP01. The prerequisite for the above command to work on 6.2.2 FP01 is the two provisional APARs IZ64617 & IZ69796 Customer applied the two provisional fix on the 6.2.2 FP01 and executed the command but received the outofMemory exception error Apr 7, 2010 8:36:30 AM com.ibm.tivoli.itm.workspace.cli.WorkspaceImportExportCLI run SEVERE: Unhandled exception caught java.lang.OutOfMemoryError at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) at javax.xml.parsers.DocumentBuilder.parse(Unknown Source) at com.ibm.tivoli.itm.workspace.xml.WorkspaceXMLImporter.parseXMLFi le(WorkspaceXMLImporter.java:1175) at com.ibm.tivoli.itm.workspace.xml.WorkspaceXMLImporter.importNavi gatorFromXML(WorkspaceXMLImporter.java:974) at com.ibm.tivoli.itm.workspace.cli.WorkspaceImportExportCLI.execut eNavigatorImport(WorkspaceImportExportCLI.java:2108) at com.ibm.tivoli.itm.workspace.cli.WorkspaceImportExportCLI.run(Wo rkspaceImportExportCLI.java:780) at com.ibm.tivoli.itm.workspace.cli.WorkspaceImportExportCLI.jnimai n(WorkspaceImportExportCLI.java:296) Apr 7, 2010 8:36:30 AM com.ibm.tivoli.itm.workspace.cli.WorkspaceImportExportCLI jnimain SEVERE: KUICIN099E The importNavigator command failed because an unexpected error occurred. Please consult the /Tivoli/itm/logs/TepImportExportCLI_0.log log file to determine the cause of the error. The developer already provided a provisional fix to resolve the above issue The stack trace indicates that the process got past the navigator import and the situation association import, and failed under the workspace import. There were two fixes 1. The upper JVM memory limit is removed 2. Modify the import code to free the massive amount of memory required by the navigator before proceeding with the situation association, workspace, and query imports. (memory optimization) This will work on all the platform
Local fix
Provisional fix is already available
Problem summary
The tacmd importnavigator command can fail with an OutOfMemoryException and core the JVM when a large XML input file is used. The current JVM heap allocation limit is set by the TACMD_JVM_MAX_MEMORY environment variable, but is capped at a value of "2048" (2 GB). Some systems may be able to use more memory than this if the hardware supports it.
Problem conclusion
The upper limit for the TACMD_JVM_MAX_MEMORY argument has been removed and the import code was modified to optimize memory usage such that a lower amount of available heap space is required to successfully complete the import. The fix for this APAR is included in the following maintenance vehicle: | fix pack | 6.2.1-TIV-ITM-FP0003
Temporary fix
Comments
APAR Information
APAR number
IZ74912
Reported component name
TEMS
Reported component ID
5724C04MS
Reported release
622
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-04-21
Closed date
2010-05-14
Last modified date
2010-07-23
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
TEMS
Fixed component ID
5724C04MS
Applicable component levels
R621 PSY
UP
[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSTFXA","label":"Tivoli Monitoring"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"622"}]
Document Information
Modified date:
30 December 2022