DDLsync - Unnecessarily Rebuilding Indexes For Tables
(Doc ID 1494393.1)
Last updated on APRIL 01, 2019
Applies to:Siebel System Software - Version 188.8.131.52 SIA  to 184.108.40.206  [Release V8]
Siebel CRM - Version 220.127.116.11 SIA to 18.104.22.168 SIA [Release V8]
Information in this document applies to any platform.
DDLSYNC rebuilds all clustered indexes whether they have changed or not.
Since our upgrade to Siebel 22.214.171.124 (SIA) the DDLsync functionality causes unwanted behaviour:
We use the following command to start the DDL sync: <SES install directory>\Config\config.bat -mode dbsrvr (for example: D:\Ses\config\config.bat -mode dbsrvr)
repimexp -> works just as we expected.
ddldict -> works just as we expected.
ddlimp -> During the 'ddlimp' process the indexes for our tables are rebuild (rebuilding indexes for tables because clustering index has changed), although nothing has changed in the indexes. This slows down the entire DDLsync process and may be expensive in production environment, as it takes hours to create/rebuild the indexes.
Example from the ddlsync1_01.log (see attachment):
2012-09-04 08:47:40 Rebuilding indexes for S_CONTROL because clustering index has changed
2012-09-04 08:50:47 Dropping index S_CONTROL_P1 ... 3:06.094m
2012-09-04 09:00:34 Creating index S_CONTROL_P1 ... 9:47.625m
2012-09-04 09:00:34 Granting table S_CONTROL ... 0.109s
2012-09-04 09:00:34 Merging table S_CONTROL_INTL ...
Fast assistence is required in this, since we plan to roll-out our next release (and 126.96.36.199) in the coming weeks.
This issue occurs in 188.8.131.52FP and affects MSSQL Server, Oracle and DB2LUW. Please note that DB2LUW is impacted when using the "allow reverse scans" attribute which affects 46 indexes in the current schema by default.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document