Troubleshooting
Problem
When a Information Analyzer project is being imported either from a previous or current version, using istool command, WebSphere Application Server reports java.lang.OutOfMemoryError in SystemOut.log file, after the import of Information Analyzer project hangs for several minutes.
Cause
Objects with null name are being created by IA, in the XMETA repository, when data sources are registered to IA project. For every column registered, one such object is created.
Proper names are eventually populated when Column Analysis is run on these columns. If CA is not run, the name remains as null.
These objects with null name are exported as part of the IA project when exported using the istool export command.
At the time of import, on a target server, since both the archive and the target server's XMETA repository have these objects, the asset import service considers them as duplicates, and loads these objects in the code, so they lie in the WAS Java heap, and lead to OOM.
Resolving The Problem
The cleanup utility, CleanupBadReferenceTableObjects.sh/bat removes all such objects from the repository, so that the next import does not find the matching objects.
Usage:
- Copy CleanupBadReferenceTableObjects.sh/bat and CleanupBadReferenceTableObjects.jar to <IS-Install-Home>/ASBServer/lib
- Execute CleanupBadReferenceTableObjects.sh
./CleanupBadReferenceTableObjects.sh on linux
CleanupBadReferenceTableObjects.bat in windows.
Note:
IA code is also fixed to not generate such objects. Fix is in 11.3.1.2 RP3, and 11.5 RU1, and in all later releases.
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21983774