Error sorting columns in Alert Viewer

Edit online

Changing the on-premises ObjectServer in a hybrid installation causes errors because the new ObjectServer does not have the columns and triggers that are needed by the cloud native components.

Problem

Sorting by seasonal or temporal groups in the Alert Viewer fails with the following error: "Event dataset error HEMDP0389E: e is undefined. Recovery will be attempted automatically on the next refresh".

Cause

When a hybrid installation of on-premises Operations Management and cloud native components is installed, the cloud native components create new columns and triggers on the on-premises ObjectServer. If you change the on-premises ObjectServer that the cloud native components are pointing to, or re-create your on-premises ObjectServer, then these columns and triggers are missing. These missing columns are:

ScopeID
AsmStatusId
CEACorrelationKey
CEACorrelationDetails
CEAIsSeasonal
CEASeasonalDetails
CEAAsmStatusDetails
NormalisedAlarmName
NormalisedAlarmGroup 
NormalisedAlarmCode
ParentIdentifier
QuietPeriod
CustomText
JournalSent
SiteName
CauseWeight
ImpactWeight
TTNumber

Resolution

To integrate your hybrid deployment with a different on-premises ObjectServer to the one that it was originally configured with, you must update the on-premises ObjectServer's schema with the columns that are needed by the cloud native components.

Find the pod name for the cloud native components action service.
```
oc get pods -l app.kubernetes.io/component=eanoiactionservice
```
Get the ObjectServer schema changes that are needed by the cloud native components from the cloud native components action service pod.
```
oc cp actionservice_pod:ea-noiomnibus-config/objectserver/cea_aggregation_schema.sql cea_aggregation_schema.sql
```
Where actionservice_pod is the name of the cloud native components action service pod that was retrieved in step 1.
Get the ObjectServer triggers that are needed by the cloud native components from the cloud native components action service pod.
```
oc cp actionservice_pod:ea-noiomnibus-config/objectserver/cea_aggregation_triggers.sql cea_aggregation_triggers.sql
```
Where actionservice_pod is the name of the cloud native components action service pod that was retrieved in step 1.
Copy the extracted SQL files, cea_aggregation_schema.sql and cea_aggregation_triggers.sql, to the servers that are hosting your primary and backup ObjectServers.
Run cea_aggregation_schema.sql on the primary ObjectServer.
```
$OMNIHOME/bin/nco_sql -U root -P password -S OSname < cea_aggregation_schema.sql
```
Where
- password is the password for the root user on the ObjectServer.
- OSname is the name of the ObjectServer.
Run cea_aggregation_triggers.sql on the primary ObjectServer.
```
$OMNIHOME/bin/nco_sql -U root -P password -S OSname < cea_aggregation_triggers.sql
```
Where
- password is the password for the root user on the ObjectServer.
- OSname is the name of the ObjectServer.
Run cea_aggregation_schema.sql on the backup ObjectServer.
```
$OMNIHOME/bin/nco_sql -U root -P password -S OSname < cea_aggregation_schema.sql
```
Where
- password is the password for the root user on the ObjectServer.
- OSname is the name of the ObjectServer.
Run cea_aggregation_triggers.sql on the backup ObjectServer.
```
$OMNIHOME/bin/nco_sql -U root -P password -S OSname < cea_aggregation_triggers.sql
```
Where
- password is the password for the root user on the ObjectServer.
- OSname is the name of the ObjectServer.
Draft comment: LOUISERoberts
#1999