Cloud native analytics triggers are not re-created in certain situations

Edit online

In situations where the ObjectServer's data store is corrupted, the preinstall job needs to be run manually to re-create the schema and triggers in the ObjectServer.

Problem

The setup of the ObjectServer schema and triggers in the ObjectServer is done by a preinstall job when cloud native analytics is installed. If in situations where the ObjectServer's data store is corrupted and needs to be rebuilt, then the preinstall job needs to be rerun to re-create the schema and triggers in the ObjectServer.

Resolution

To re-create the schema and triggers in the Object Server, manually run the preinstall job.

  1. Delete the original setup job definition by running the following command:
    oc delete job <name>-ea-noi-layer-easetupomnibus
    Where <name> is the name of your Netcool® Operations Insight® deployment. The default value is evtmanager.
  2. Restart the Netcool Operations Insight operator by deleting its current pod to force a reconcile so that the job is re-created and run. Run the following command to determine the name of the pod and delete it: 
    oc get pod | grep "^noi-operator-[0-9]*-*" | awk '{print $1}' | xargs oc delete pod
    When the new Netcool Operations Insight operator pod is started, it detects that the job is missing and reruns the job. After some time, the job <name>-ea-noi-layer-easetupomnibus is re-created and an associated pod is created and run, which reapplies the schema and triggers.