Issues and workarounds for the Siebel DAC compare and Merge strategy

The Siebel provided DAC compare and merge strategy is a nice tool that helps us identify differences between a source DAC repository and the target DAC repository. Also helps to figure out which objects are to be moved to the target. But, there onwards the merge process is manual and a big waste of time. One cheat used by many administrators is to simply copy the repository from the lower environment to the higher environment. This works, but it has one major drawback. The last ETL process id is inherited from the lower environment.

The implication is that the run ids stored in the Run Stats table has no relation to the run number stored in the W_PARAM_G table and it becomes a major challenge to figure out which ETL run did what. Then one has to meddle with the DAC repository tables to get the last ETL process being stored in the DAC repository in sync with the numbers stored in W_PARAM_G. This is a risky proposition especially if one has not understood the relationships between the repository tables and the significance of all the long keys stored by Siebel in the repository to maintain the relationship between the tables.

So, here is a solution which we have tried out (with success) to move a DAC repository from a lower environment to a higher environment without making a hash of the run history.The basic idea here is to move only few selected tables from the source environment to the target instead of doing a complete repository overwrite.

The Step 2: Import

steps Schema DAC

are repository into to

as Target DAC

below: repository

Step 1: Take backup (Export) from Target DAC Repository make it separate folder(Just for Backup) Step 3: Export below mention Tables from Source DAC Repository. Make a separate folder which should contain below mention tables (20) only.

Sr. No Entity 1 Database Connections 2 Database Indices 3 Database Tables 4 Execution Plan Execution PlanDatabase 5 Connections 6 Execution PlanSubject Area 7 Execution PlanPre-PostSteps 8 Group 9 Group Table 10 Index Columns 11 Indices 12 Informatica Folder 13 Tables 14 Tasks

Main Table W_ETL_DBCONN W_ETL_DB_INDEX W_ETL_TABLE_DT W_ETL_DEFN W_ETL_DEFN_DB W_ETL_DEFN_SA W_ETL_DEFN_STEP W_ETL_GROUP W_ETL_GRP_TBL W_ETL_INDEX_COL W_ETL_INDEX W_ETL_FOLDER W_ETL_TABLE W_ETL_STEP

15 16 17 18 19 20
Step

Task Dependencies Task Phase Task Tables Subject Area Subject Area/Group System Properties
4: Import server 6: steps to Refresh refresh are: this setup all Tools>ETL tables in

W_ETL_STEP_DEP W_ETL_PHASE W_ETL_STEP_TBL W_ETL_SA W_ETL_SA_GROUP W_ETL_SYSPROP

into Target Target dates Management> (for Reset DAC DAC full Data Repository. Repository. load) Warehouse

Step 5: After importing we need to make some changes in the Setup tab, Database connection and informatica Step The Tables:

Step 7: Before running Full Load truncate below mentioned tables, please take backup before truncating.

1. S_ETL_RUN from OLTP 2. W_ETL_RUN_S from OLAP Any better ideas out there?

Inputs from Raghunatha Yadav & Sanjay Rao