We had an UIM upgrade last week and after that quite a few UMP e2e_appmon QOS previously displayed are now missing data.
Jul 25 14:14:40:814 [139975012632320] 3 de: allocateOCIErrorHandle OCIHandleAlloc errhp...
Jul 25 14:14:40:814 [139975012632320] 4 de: OCIPrep - (StmtPrepare) preparing oracle statement for SQL(INSERT /*+ APPEND */ INTO
S_QOS_DATA ( QOS_DEF_ID, CHECKSUM, QOS, SOURCE, TARGET, HOST, R_TABLE, H_TABLE, CI_METRIC_ID, ORIGIN, ROBOT, PROBE )
VALUES ( :QOS_DEF_ID, :CHECKSUM, :QOS, :SOURCE, :TARGET, :HOST, :R_TABLE, :H_TABLE, :CI_METRIC_ID, :ORIGIN, :ROBOT, :PROBE ))
Jul 25 14:14:40:814 [139975012632320] 4 de: OCIPrep - (OCIAttrGet) getting oracle statement type.
Jul 25 14:14:40:816 [139975012632320] 0 de: data_engine [QoS] [QoSData] - InsertQosObjectOracle [QoSData] data_engine [QoS] status: -1
OCI_ERROR - ORA-00001: unique constraint (UIMSLM_USER.UQ_S_QOS_DATA) violated
OCIEnv: 0x0x7f4e6c004d70 OCIAuthInfo: 0x0x7f4e6c012bc0 OCISvcCtx: 0x0x7f4e6c045d18
- Error: InsertQosObjectOracle [QoSData] data_engine [QoS] status: -1
Jul 25 14:14:40:816 [139975012632320] 3 de: allocateOCIErrorHandle OCIHandleAlloc errhp...
Jul 25 14:14:40:816 [139975012632320] 4 de: OCIPrep - (StmtPrepare) preparing oracle statement for SQL(SELECT S_QOS_DATA_table_id_ASQ.CURRVAL FROM DUAL)
Release: UIM 9.0.2
Component : UIM - UMP
Depending on how critical the old data entries are, you may choose to:
1. Delete the e2e_appmon entries from the S_QOS_DATA table (which is more of an index to the backend data in the RN (raw) and HN (historical) tables).
2. Then restart the e2e_appmon probe(s) and the data_engine, then check the log to see if the errors persist.