Last updated on MARCH 01, 2016
Applies to:Siebel CRM - Version 126.96.36.199  and later
Information in this document applies to any platform.
CHECKED FOR RELEVANCE ON 1-FEB-2013
We are implementing Siebel Call Center and are faced with a peculiar problem. There is an index S_ORDER_BU_M1 on S_ORDER_BU table which is a vanilla index with index columns as BU_ID Asc, ORDER_CAT_CD Asc and ORDER_DT Desc in the repository. For business requirements, we have to keep ORDER_DT Desc. If the sort changes to Asc on this column, the screen/view performance is very bad.
We have noticed that during repository migration (Dev2prod), ddlsync modifies this index to ORDER_DT Asc on the database even though the schema.ddl has correct definition. I also tried dropping this index from the database and then, applying the table in which case the index was correctly created.
On looking through previous SRs, I found that Oracle, by default, sorts indices in ascending order.
Can you please let me know why this is happening and also, what is the fix/workaround for this issue?
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