- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-17-2018 02:57 AM
We detected an issue due to the fact that a field (correlation_id on the cmdb_ci table) has the dictionary attribute "unique" set to "true". Comparing with a brand new system, we discovered that, OoB, this attribute is set to "false".
We therefore decided to go OoB and set it to false on our instance.
But now, despite this "unique" attribute is set to false, when we test it and try to enter in this field a duplicate value, we still get the following message:
java.sql.BatchUpdateException: Duplicate entry '42 31 54 a5 49 98 59 1f-2c 65 96 74 70 c6 c3 c3' for key 'correlation_id'
What else needs to be done to have this change in effect?
Thanks
Marcus
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-17-2018 06:37 AM
It should be handled just by checking/unchecking the 'Unique' dictionary attribute. There's no safe way other than that to delete/remove an index. You'll need to contact SN support to handle that for you.
Please mark my answer correct if I've answered your question.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-17-2018 06:37 AM
It should be handled just by checking/unchecking the 'Unique' dictionary attribute. There's no safe way other than that to delete/remove an index. You'll need to contact SN support to handle that for you.
Please mark my answer correct if I've answered your question.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2018 12:18 AM
I created a hi ticket and they confirm that they were expecting that when unflagging the unique flag, the unique index would be removed.
They are investigating now.
I will update this post with the outcome for future reference.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-22-2018 09:02 AM
ServiceNow did regenerate the index of the table with the correlation_id set as non-unique and it is now solved.
Thank you for your support.
BR
MArcus