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 steps are as below:
Step 1: Take backup (Export) from Target DAC Repository make it separate folder(Just for Backup)
Step 2: Import Schema DAC repository into to Target DAC repository
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 Main Table 1 Database Connections W_ETL_DBCONN 2 Database Indices W_ETL_DB_INDEX 3 Database Tables W_ETL_TABLE_DT 4 Execution Plan W_ETL_DEFN 5 Execution Plan—Database Connections W_ETL_DEFN_DB 6 Execution Plan—Subject Area W_ETL_DEFN_SA 7 Execution Plan—Pre-PostSteps W_ETL_DEFN_STEP 8 Group W_ETL_GROUP 9 Group Table W_ETL_GRP_TBL 10 Index Columns W_ETL_INDEX_COL 11 Indices W_ETL_INDEX 12 Informatica Folder W_ETL_FOLDER 13 Tables W_ETL_TABLE 14 Tasks W_ETL_STEP 15 Task Dependencies W_ETL_STEP_DEP 16 Task Phase W_ETL_PHASE 17 Task Tables W_ETL_STEP_TBL 18 Subject Area W_ETL_SA 19 Subject Area/Group W_ETL_SA_GROUP 20 System Properties W_ETL_SYSPROP

Step 4: Import this tables into Target DAC Repository.
Step 5: After importing we need to make some changes in the Setup tab, Database connection and informatica server setup in Target DAC Repository.
Step 6: Refresh all dates (for full load)
The steps to refresh are: Tools–>ETL Management–> Reset Data Warehouse
Step 7: Before running Full Load truncate below mentioned tables, please take backup before truncating.

Tables:

1. S_ETL_RUN from OLTP
2. W_ETL_RUN_S from OLAP

Any better ideas out there?

Inputs from Raghunatha Yadav & Sanjay Rao

you can read it More SiebelDAC

Limitation of Scripting in Siebel

Siebel CRM is one of the most effective CRM solution available till date. Clients with complex business requirements opt for Siebel to help themselves in identifying, acquiring and retaining their respective Customers. As a Siebel Professional we use Configuration, Scripting and EAI in order to build an Application.

There are nearly 200 different types of objects that can be configured in Siebel to reflect the changes in the User Interface Layer, Business Objects Layer, and Data Objects Layer. Also, the Siebel objects have intertwined multiple relationships between them.

We need to write programs in case of complex requirements (According to Siebel best practices — scripting should be the last resort in situations where only configuration cannot accomplish the business and technical requirements).

There are primarily 4 programming languages used when customizing Siebel.
Siebel Visual Basic (Siebel VB), Siebel eScript, JavaScript (available as of Siebel 7) and Java (through Java Business Services).

But there are some limitations of scripting in Siebel which are cited below:

• It’s case sensitive.
• Siebel eScript code is executed one statement at a time, in the order in which it is read.
• If objects are not instantiated properly then it can lead to Memory leakages.
• Need to take extra care while declaring the variables at application level.
• Difficult to maintain the code.

Some of the biggest demerits of Scripting in Siebel are:

1. May not be fully upgradable. In Siebel upgrades, scripts undergo extensive retrofitting
2. 
   
3. One object can be scripted in only one programming language, i.e. if you are writing a BS in eScript and want to access some COM / ActiveX object then in most of the cases you need to switch on to a different Object which is written in VBscript. If the facility to use many scripting language in an Object has been given then one do not require to switch in between objects.
4. 
   
5. In one method of an Object one can write only 16KB of code, which some times becomes critical especially when one wants to modify some existing functionality.
6. 
   
7. If the script is written in Browser side then one can easily call Server side script and get it executed, but the vice-versa is not true.
8. 
   

There are numerous benefits of scripting in Siebel in comparison to its miniscule limitations. However it is very vital that one is aware of the limitations too.

Please feel free to Read More : Scripting in Siebel

Unleashing the Giant – Siebel CRM

The first “C” program that I wrote was about printing “Hello World”. On synonymous lines to my first “C” program, while blogging the first post I would like say “Welcome and Explore the Siebel Street”. Siebel has been the most active promoter of CRM for more than a decade. How many customers have been better served because Tom Siebel decided to help popularize Customer Relationship Management? The answer is innumerable.

Siebel CRM has been consistent market leader in CRM software arena. The best in-class customization, top-notch user interface, strong integration tools, diversified industry-wide applications, easy upgrades and reliable customer support are few key attributes of this Giant – Siebel CRM. Siebel CRM caters to its clients in various verticals like Finance, Pharma, Telecom, Hi-tech manufacturing, Insurance, Sales, Marketing etc.

The customizations in the Siebel applications are implemented using Configuration, Scripting and Workflows. Siebel EAI integrates third party applications/objects with Siebel and Siebel EIM populates external data in interface tables and user data in base tables. Siebel Analytics furnishes the needs of Report generation, analyzing of business trends, logistics etc. This Giant CRM’s robustness lies in the sheer depth and breadth of its functionality. Siebel products are continuously rated at the apex in sales, marketing, customer service and other CRM peripheral areas.

Post-Oracle’s big ticket acquisition Siebel CRM has been the lustrous feather in the cap of Oracle. Oracle already has PeopleSoft, JD Edwards, Oracle Apps under its belt and now the bellwether – Siebel CRM. With so-many CRM solution providers under its kitty, Oracle plans to roll-out Oracle-Fusion in near future.

Moving forward, Oracle plans to make Siebel as the center piece of its CRM product, while bringing together the functionality of all its acquisitions under Fusion. So if I was to choose between a newcomer, a struggling cameo or a strong veteran with no signs of fading off, the choice would be clear – Siebel CRM.

Watch out this space for more on various Siebel CRM topics, techno-functional issues, problems-resolutions, experiences etc.