DDLSYNC Drops And Recreates Index S_XMLP_REP_TMPL_U1 After Applying ACR719B (Doc ID 1514972.1)

Last updated on AUGUST 31, 2017

Applies to:

Siebel Sales - Version 8.1.1.7 SIA [21238] and later
Information in this document applies to any platform.

Goal

After applying ACR719B, you have found that the ddlsync process drops and recreates the index S_XMLP_REP_TMPL_U1 every time it is run.

Having investigated further it looks like this is due to the field "Cluster - DB2" being set to Y for both S_XMLP_REP_TMPL_U1 and S_XMLP_REP_TMPL_U2. I performed a quick test, removing the flag setting for S_XMLP_REP_TMPL_U2, and does seem to be the root cause, as ddlsync no longer does the drop / create.

What should be the correct table definition?
 

Solution

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms