Siebel System Admin, Install and Upgrade (MOSC)

MOSC Banner

Upgrade failing at Migrate Repository

edited Aug 5, 2017 5:00AM in Siebel System Admin, Install and Upgrade (MOSC) 1 commentAnswered

Upgrading from 8.1.10 to 16.9. This is occurring on the PRODUCTION upgrade. I did not run into this issue doing the Production Test upgrade.

Running the Migrate Repository config, I'm running into this error:

[Microsoft][SQL Server Native Client 11.0][SQL Server]The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name 'dbo.S_ACCELERATOR' and the index name 'S_ACCELERATOR_M9'. The duplicate key value is (<NULL>, <NULL>, <NULL>).

SQL Statement:

create unique nonclustered index S_ACCELERATOR_M9 on S_ACCELERATOR

("WS_SRC_ID", "WS_ID", "WS_OBJ_VER")

on 'default'

What I've found is that this means that this S_ACCELERATOR table has to not been updated with values for use with SIebel Workspaces. For all of the pre-16 rows, the WS_SRC_ID, WS_ID, and WS_OBJ_VER columns are null, as there were no workspaces in Siebel 8.1. Further testing by adding values to those columns just causes the upgrade to fail when doing the next table, with the same problem.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

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

Category Leaderboard

Top contributors this month

SBL Sys Admin Tags

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center