search cancel

Unique constraint violation errors in iDash log

book

Article ID: 243080

calendar_today

Updated On:

Products

iDash Workload Automation for CA 7

Issue/Introduction

Moved Oracle database to new servers.  Looking into the info.log file, and notice the following errors. Are these anything to be concerned about?

22-05-25 09.31.41 [ INFO] jfmevent-store-jobrun-thread-1: Batch insert of JobRuns into idash_hist_job_run_ca7 failed:ORA-00001: unique constraint (IDASH.SYS_C008723) violated
java.sql.BatchUpdateException: ORA-00001: unique constraint (IDASH.SYS_C008723) violated
[[email protected]:lwai307a log]$ cat info.log | grep -i constraint | tail -10
22-05-25 13.39.33 [ INFO] jfmevent-store-jobrun-thread-1: Batch insert of JobRuns into idash_job_run_ca7 failed:ORA-00001: unique constraint (IDASH.SYS_C008722) violated
java.sql.BatchUpdateException: ORA-00001: unique constraint (IDASH.SYS_C008722) violated
22-05-25 13.39.34 [ INFO] jfmevent-store-jobrun-thread-1: Batch insert of JobRuns into idash_hist_job_run_ca7 failed:ORA-00001: unique constraint (IDASH.SYS_C008723) violated
java.sql.BatchUpdateException: ORA-00001: unique constraint (IDASH.SYS_C008723) violated

Environment

Release : 12.1

Component :

Resolution

If this happens for a short while, it's safe to ignore, particularly if it's around an outage of some sort. If it continues to happen for an extended period of time, it might indicate a problem. The 2 most likely scenarios are that the secondary thinks the primary is down and they are both trying to write events, or iDash is taking so long to process and write events that JFM is timing out and resending the same batch of events over and over.