DDL Sync Execution Resulting in Dropping and Recreation of Unchanged Indexes
Last updated on AUGUST 31, 2017
Applies to:Siebel CRM - Version 184.108.40.206  and later
Information in this document applies to any platform.
Customer is executing DDL Sync on a Siebel 220.127.116.11 environment. During the execution, DDL Sync is dropping and rebuilding indices even though there have not been any relevant changes for these indices between the database schema and the Siebel Repository. This takes a long time to complete and may negatively impact moving this to production with its larger data set.
The desired behavior is that DDL Sync would only rebuilt indices that are not in sync between the database schema and the Siebel Repository.
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