Flattening Workspace Command With /DropIndexes Didn't Change The Indexes Xxx_M9 To NONUNIQUE (Doc ID 2232684.1)

Last updated on FEBRUARY 10, 2017

Applies to:

Siebel CRM - Version 16.3 [IP2016] and later
Information in this document applies to any platform.

Symptoms

On :  16.3 [IP2016] version, Configuration - General

ACTUAL BEHAVIOR  
---------------
Flattening workspace command with /DropIndexes didn't change the indexes xxx_M9 to NONUNIQUE  


EXPECTED BEHAVIOR
-----------------------
Bookshelf indicated the  /DropIndex parameter will mark all indexes as non-unique indexes:
http://docs.oracle.com/cd/E74890_01/books/UsingTools/using_siebel_tools57.html#wp1187396
Run this command to mark all indexes as non-unique indexes and flatten the workspace versions:
siebdev /c tools.cfg /l enu /d ServerDataSrc /u /p /FlattenWorkspace /DropIndexes <DB_user_name> <DB_password> <DB_platform>
 


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1) EnableWorkspace -s "C:\Siebel\Tools" -t SIEBEL -u SIEBEL -p SIEBEL -o "SSD default instance" -d Oracle -l C:\Siebel\Tools\LOG\EnableWorkspace.log -w SADMIN

2) Before flatten the woorkspace, follow the below steps to get around the error posted in the doc ID 2192128.1
   Log into siebel tools
   Create new workspace  (In Siebel Tools, select the Workspace menu and then Create option.)
   Make a change to any object
   Checkpoint  (In Siebel Tools, select the Workspace menu and then select the Checkpoint option.)
   Submit for Delivery  (In Siebel Tools, select the Workspace menu and then select the Submit for Delivery option.)
   Deliver (In Siebel Tools, select the Workspace menu and then select the Deliver option.)
   Log out

3) Run command to flatten workspace with the  /DropIndexes option to mark all indexes as non-unique indexes:
   siebdev /c tools.cfg /l enu /d ServerDataSrc /u SADMIN /p SADMIN /FlattenWorkspace /DropIndexes SIEBEL SIEBEL ORACLE


Go to the database and check that  xxx_M9 indexes(for example,S_APPL_WEB_TMPL_M9,S_APPLET_M9) are not updated to NONUNIQUE . They are still UNIQUE

Cause

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