Troubleshooting
Problem
Alert functions, which use calculated metrics as input, create alerts only for one entity.
Resolving The Problem
There is a workaround for this issue. It involves adding the entity_id column to the unique constraint on the table "DM_WIOT_AS_ALERT".
Follow the steps below to add the entity_id column to the unique constraint:
- Obtain the DB2/PostgreSQL connection parameters from the Maximo Asset Monitor UI located under the Services section.
- Connect to your database using the credentials obtained in the previous step.
- Run the following SQL statement:
ALTER TABLE BLUADMIN.DM_WIOT_AS_ALERT ADD CONSTRAINT DM_WIOT_AS_ALERT_PK PRIMARY KEY (ENTITY_TYPE_ID,ENTITY_ID,DATA_ITEM_NAME, "TIMESTAMP");
Document Location
Worldwide
[{"Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSRHPA","label":"IBM Maximo Application Suite"},"ARM Category":[{"code":"a8m0z000000cx3cAAA","label":"Maximo Monitor"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.3.0"}]
Was this topic helpful?
Document Information
Modified date:
04 February 2021
UID
ibm16412269