Index Violation Errors

An index violation error conflict occurs when there are two different objects of the same type having the same combination of contents. A potential violation of the index is detected as a result of the rebase and the merge process cannot select any resolution. Hence the system displays an error on the object and fails the rebase process.

You can fix this error either by manually modifying the fields involved in the index or by performing the RevertObject operation on the object (on a single version or the entire Workspace). This fix ensures that there is no longer a violation and then users can run the rebase process again.

Deleting Unique Indexes

If Oracle adds a new index (for example, S_EVT_ACT_CAL_Index2 which uses the PAR_REPTEVT_MST_ID column) with the same columns as an existing custom index (for example, S_EVT_ACT_CAL_Index1 which has already been created and uses the same PAR_REPTEVT_MST_ID column), then errors will be encountered when running the PostInstallDBSetup utility and RepositoryUpgrade utility. To resolve this issue, do the following:

1. Manually delete or inactivate the custom index object under (in this example) S_EVT_ACT_CAL in the Siebel Repository. For example:

   1. Locate the index object S_EVT_ACT_CAL_Index1 under the S_EVT_ACT_CAL table.

   2. Delete the index object S_EVT_ACT_CAL_Index1.

   Note that it is not sufficient to delete the index object just at the database level, you must delete the index object from the repository as well.

2. Run the PostInstallDBSetup utility again.

   For more information about the Post Installation Database Update process and running the PostInstallDBSetup utility, see Siebel Database Upgrade Guide.

3. If there are Test, QA, or Production environments that also have the same index (S_EVT_ACT_CAL_Index1 in this example), then run the RepositoryUpgrade utility.

   For more information about the RepositoryUpgrade utility and how to run the utility, see Siebel Database Upgrade Guide.