Troubleshooting
Problem
Depending on the upgrade or install path taken, there may be some columns missing from Impact's Derby database for NOI. Two known issues are detailed in this document. Depending on the upgrade or install path taken, one, none or both issues may present.
Problem 1
DEFAULT_PATTERN_FILTER column is missing from the RELATEDEVENTS.RE_CONFIGURATION table
The field was introduced in FP24, but upgrades from very early versions to FP24 and FP25 will not have this field. Direct upgrades from versions FP1, FP2, FP3, FP4 and FP5 to FP24 or FP25 will be missing this field. This also affects combined installs to FP24 and FP25 if running a combined install with 7101 or 7104. In these cases the field would be missing. Customers upgrading from higher versions (FP6+) will not have this issue.
The field was introduced in FP24, but upgrades from very early versions to FP24 and FP25 will not have this field. Direct upgrades from versions FP1, FP2, FP3, FP4 and FP5 to FP24 or FP25 will be missing this field. This also affects combined installs to FP24 and FP25 if running a combined install with 7101 or 7104. In these cases the field would be missing. Customers upgrading from higher versions (FP6+) will not have this issue.
Problem 2
IS_FROM_OLD_CONFIG_RUN column is missing from the SEASONALITY.SEASONALITY_RESULTS_DATA
The field was introduced in FP19. The only install type for which this field is missing is a Full Install at FP20 level. All other installs (Full or Upgrade) will have this field.
Symptom
Symptom for Problem 1
If the DEFAULT_PATTERN_FILTER column is missing from the RELATEDEVENTS.RE_CONFIGURATION table, then configurations are not shown on the Configure Analytics page for On-Prem Event Analytics. The page will display either no results, or an error "Failed to Load Data"
Symptom for Problem 2
If the IS_FROM_OLD_CONFIG_RUN column is missing from the SEASONALITY.SEASONALITY_RESULTS_DATA table, then the following errors can be seen in the policy log for the SE_GETEVENTDATA policy.
com.micromuse.common.datasource.SQLDataSourceException: Exception while executing database operation after trying twice. First exception: Column 'IS_FROM_OLD_CONFIG_RUN' is either not in any table in the FROM list
The same errors can be seen in the impact server logs.
com.micromuse.common.datasource.SQLDataSourceException: Exception while executing database operation after trying twice. First exception: Column 'IS_FROM_OLD_CONFIG_RUN' is either not in any table in the FROM list
The same errors can be seen in the impact server logs.
On the UI, the filter option for the Seasonality page is not functional.
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSB2GF","label":"Netcool\/Impact"},"ARM Category":[{"code":"a8m500000008a6cAAA","label":"Impact-\u003ENOI Netcool Operations Insights"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.1.0"}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Was this topic helpful?
Document Information
Modified date:
09 May 2025
UID
ibm16591435