Bookshelf v7.8.2: Comparing and Merging DAC Repositories

Comparing and Merging DAC Repositories

The DAC Repository Merge feature allows you to identify differences between a source DAC repository and a target DAC repository and to move new objects from the source to the target repository. You can use this feature to upgrade repository customizations of prior releases to a new release or to compare and merge two repositories, such as development and production repositories.

The DAC Repository Merge feature identifies the following differences between the source and target repositories. The identified differences are listed in the DAC Repository Difference report. This report is automatically generated during the compare and merge process and saved in the SiebelAnalytics\DAC\diff\html directory.

Modified objects. The row ID and user key of an object type in the source repository is compared with the row ID and user key of the same object type in the target repository. If either the row ID and user key are the same for the two objects or if both the row ID and user key are the same, the objects are considered to be a match, and the any difference between the attributes of these objects will appear in the Difference report.

Objects added to the target repository. Objects that appear in the target repository but do not appear in the source repository.

Objects missing from the target repository. Objects that appear in the source repository but do not appear in the target repository.

Table 35 lists the objects that are compared and the table and user key associated with the object.

When you perform the compare process, using the Compare and Merge Repositories dialog box, you can choose to import from the source repository into the target the objects that are missing. Records that were modified in the source repository cannot be imported into the target. You must enter the modifications manually in the target repository.

Table 35. Objects Compared in DAC Repository Compare Process
Entity	Main Table	User Key
Database Connections (source/target)	W_ETL_DBCONN	NAME
Database Indices	W_ETL_DB_INDEX	W_ETL_DB_INDEX.DB_TYPE, W_ETL_INDEX.NAME
Database Tables	W_ETL_TABLE_DT	W_ETL_DBCONN.NAME, W_ETL_TABLE.NAME
Execution Plan	W_ETL_DEFN	W_ETL_NAME
Execution Plan—Database Connections	W_ETL_DEFN_DB	W_ETL_DBCONN.NAME, W_ETL_DEFN.NAME
Execution Plan—Subject Area	W_ETL_DEFN_SA	W_ETL_DEFN.NAME, W_ETL_SA.NAME
Execution Plan—Pre-Post Steps	W_ETL_DEFN_STEP	W_ETL_DEFN.NAME, W_ETL_STEP.NAME
Group	W_ETL_GROUP	NAME
Group Tables	W_ETL_GRP_TBL	W_ETL_GROUP.NAME, W_ETL_TABLE.NAME
Index Columns	W_ETL_INDEX_COL	W_ETL_INDEX.NAME, W_ETL_INDEX_COL.NAME
Indices	W_ETL_INDEX	NAME
Informatica Folder	W_ETL_FOLDER	NAME
Tables	W_ETL_TABLE	NAME
Tasks	W_ETL_STEP	NAME
Task Dependencies	W_ETL_STEP_DEP	W_ETL_STEP.NAME, W_ETL_STEP.NAME
Task Phase	W_ETL_PHASE	NAME
Task Tables	W_ETL_STEP_TBL	W_ETL_STEP.NAME, W_ETL_TABLE.NAME
Subject Area	W_ETL_SA	NAME
Subject Area/Group	W_ETL_SA_GROUP	W_ETL_GROUP.NAME, W_ETL_SA.NAME
System Properties	W_ETL_SYSPROP	NAME

To compare and merge DAC repositories

Restore the target DAC repository on a separate database instance.

If you are upgrading from a previous version, the target repository is the new version.

Export the source DAC repository to back up the data.

Set up the database connections for the source and target repositories.

In the DAC, navigate to Setup > Database Connections.

Enter the following:


Field	Enter
Logical Name	A logical name for the connection.
Type	DAC Repository.
Connection Type	Type of database connection.
Dynamically changes based on Connection Type	If you are using... Oracle (OCI8) enter the TNS name. Oracle (Thin) enter the instance name. SQL Server enter the database name. DB2-UDB enter the connect string as defined in the DB2 configuration. Teradata enter the database name.
Table Owner	Name of table owner.
Table Owner Password	Password for table owner.
Max Num Connections	The maximum number of connections the DAC server will maintain to the database.
DB Host	Host machine where the database resides. Required for Oracle (Thin) and MSSQL databases. Not required for Oracle (OCI8), DB2, and DB2-390.
Port	Port where the database receives requests. Required for Oracle (Thin) and MSSQL databases. Not required for Oracle (OCI8), DB2, and DB2-390.

From the DAC toolbar, select Tools > DAC Repository Management > Compare and Merge Repositories.

In the Compare and Merge Repositories dialog box, select the source and target repositories that you want to compare.

To import from the source repository into the target the objects that are missing, select the Import Missing Objects check box.

NOTE: Modifications made to objects in the source repository must be entered manually in the target repository.

The Difference report is automatically created.

To view the Difference report, navigate to SiebelAnalytics\DAC\diff\html, and double-click index.html.