My Oracle Support Banner

Siebel Merge LOY Member Process unique constraint S_LOY_SOM_HIST_U1 (Doc ID 2410057.1)

Last updated on OCTOBER 06, 2021

Applies to:

Siebel Loyalty Member Services Representative - Version [IP2013] and later
Information in this document applies to any platform.


For example, by logic, we need to change the status of prospect from “active” to “inactive”. So, two records inserted to S_LOY_SOM_HIST with exactly the same fields and differentiated only by state of status (FROM_STATUS, TO_STATUS). When these two records inserted in one second ORA-00001: unique constraint (SIEBEL.S_LOY_SOM_HIST_U1) violated. Constraint for uniqueness of three columns: CONFLICT_ID, MEMBER_ID, TXN_DT.

Based on this, we would like to know is it possible to update not only member points but also another fields such as last date of transaction or member status etc. using “MergeRecords” vanilla method? Alternatively, change the index SIEBEL.S_LOY_SOM_HIST_U1 on table S_LOY_SOM_HIST and add fourth column (FROM_STATUS, TO_STATUS) to eliminate errors?


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.