Siebel System Admin, Install and Upgrade (MOSC)

MOSC Banner

Better workaround for S_ACCELERATOR_M9 SQL Server bug

edited Oct 4, 2018 5:00AM in Siebel System Admin, Install and Upgrade (MOSC) 1 commentAnswered

For those upgrading to IP 17/18 on SQL Server you will face bug

IP2017 Production Mode Upgrade Failing with Duplicate Key on _M9 indexes, SQL Server (Doc ID 2376204.1)

BUG:27616636 - DUPLICATE KEY ERROR ON _M9 INDEX IN PROD MODE UPGRADE ON SQL SERVER

We ran into the same bug and don't like the workaround suggested and are providing what we think is a better work around.  The problems with the suggested workaround are these:

- Running the dev upgrade sequence in production will add hours of downtime you don't want.  E.g. instead of the upgrade running two hours now it will run 10 hours.

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