IBM Support

Upgrades and import may fail for systems with customized Operator View files with 7.1.0-TIV-NCI-FP0020

Troubleshooting


Problem

Artifacts related to Operator Views are stored in the $IMPACT_HOME/opview/displays directory. These files are typically prefixed with the clsuter name but can also legitimately contain javascript, image and other customized files which are not prefixed with a cluster name.
Due to a change introduced in 7.1.0-TIV-NCI-FP0020, nci_import will fail if opview/displays directory contains non-prefixed files. This is true if the non-prefixed files exist in the existing opview/displays directory, or in the opview/displays directory to be imported.
Also, upgrades to systems with NOI Extensions rely on the Import function, to import NOI, Seasonality and Related Events projects. The FP20 upgrades will report success but the projects will not be correctly updated. Again, this is only the case if the opview/displays directory contains non-prefixed files.
For all systems at FP19 level and below, the upgrade will fail if the opview/displays directory contains non-prefixed files.

Symptom

1. nci_import
The nci_import command fails with the following  message : javax.management.MBeanException: Error executing policy: Import; Exception: Unhandled Exception: String index out of range: 0 in policy: Import at line: 16. in Import
 

The full error and stack trace in the policy log for the Import policy is

[Import][pool-5-thread-748]Caused by: java.lang.StringIndexOutOfBoundsException: String index out of range: 0 
java.lang.String.substring(String.java:2726)   
com.micromuse.response.Importer.importFunction(Importer.java:350)      
com.micromuse.response.common.parser.functions.ImportFunction.runCompute(ImportFunction.java:69)       
com.micromuse.common.parser.FunctionImpl.compute(FunctionImpl.java:57) 
com.micromuse.common.parser.internal.core.PolicyParserInterpreterVisitor.visit(PolicyParserInterpreterVisitor.java:1052)
Caused by: java.lang.StringIndexOutOfBoundsException: String index out of range: 0 
java.lang.String.substring(String.java:2726)
com.micromuse.response.Importer.importFunction(Importer.java:350)

2. Upgrades of system which have NOI Extensions installed will report that they have completed successfully but the NOI related projects will not have been imported. Any new policies for the upgrade will not be updated on the running system. For systems at FP19 level and below, the upgrade will fail if the opview/displays directory contains non-prefixed files.

Resolving The Problem

APAR IJ30671, planned for 7.1.0-TIV-NCI-FP0021 will address this issue. 
In the meantime, see the workarounds below:
1. For nci_import:
Before using nci_import, move any files in opview/displays, without a clustername prefix, to a different directory.  This needs to be performed on the existing opview/displays directory and on the opview/displays directory to be imported. After upgrade, the files must be reinstated.
Alternatively, contact support for a hot fix for APAR IJ30671.
2. For FP20 Upgrades:
Before upgrading systems with NOI extensions, move any files in opview/displays, without a clustername prefix, to a different directory. After upgrade, the files can be reinstated.

Document Location

Worldwide

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSSHYH","label":"Tivoli Netcool\/Impact"},"ARM Category":[{"code":"a8m500000008ZvjAAE","label":"Impact->Installation->Upgrade"},{"code":"a8m500000008bolAAA","label":"TBSM->DASH->DASH UI Services - CLI Category->DUIS-CLI - Export\/Import"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.1.0"}]

Document Information

Modified date:
11 February 2021

UID

ibm16413353