About the Repository Upgrade (DAC 784) Option
This section includes the following topics:
Repository Upgrade (784): High-Level Process Flow
Repository Upgrade (784): Procedure for Upgrading
1) DAC versions before Oracle BI Applications 7.9 had a non-partitioned DAC Repository structure and held metadata for a single application.
2) DAC versions released with Oracle BI Applications 7.9 and higher and with the DAC 10.1.3.4 release have partitioned DAC Repository structures.
3) The partitioned structure, also known as a container, can hold metadata for multiple applications.
4) The Repository Upgrade (DAC 784) option enables you to upgrade from the DAC Repository release 7.8.4 (non-partitioned) to the new partitioned structure.
Note: If you want to upgrade a pre-7.8.4 release of a DAC
Repository, you must first upgrade the repository to the 7.8.4 release
before you can use the Repository Upgrade (DAC 784) option to
upgrade to the new release.
10.3.1 Repository Upgrade (784): High-Level Process Flow
Figure 10–2 shows a high-level process flow for using the Repository Upgrade (DAC
784) option to upgrade an existing release 7.8.4 DAC Repository to the new release.
The term base is used to refer to a source or target container that you have not changed
or customized in any way. The base container is also referred
Figure 10–2 Upgrade Process for Repository Upgrade (DAC 784) Option
In Step 1 of the high-level process flow, you import the existing 7.8.4 DAC Repository
into the repository temporary tables. The existing 7.8.4 repository is referred to as the
source in the Upgrade/Merge Wizard.
In Step 2, you create a Difference Report that compares the existing repository with the
new base container, which is referred to as the target. (The new base container is the
version to which you are upgrading and is the version you imported from the file
In Step 3, you accept or reject the objects that the Difference Report shows as being
either present or changed in the source but not the target. See Section 10.8, "Resolving
Object Differences in the View Difference Report" for a description of how objects are
merged based on the action you take.
In Step 4, after you have resolved the differences, you then execute the merge. In Step
5, the Upgrade/Merge Wizard references the customizations in the newly merged
custom container with the new base container.
10.3.2 Repository Upgrade (784): Procedure for Upgrading
Follow this procedure to upgrade a DAC Repository in the release 7.8.4 format to the
Note: You cannot use the Repository Upgrade (784) option with
pre-7.8.4 releases of the DAC. To confirm your existing repository is in
the release 7.8.4 format, open the 7.8.4 DAC client and in the toolbar,
select Help, and then select About DAC. The About DAC dialog box
displays the version of DAC you are running.
Before you begin this procedure, you need to have already installed the new release of
Oracle BI Applications and imported the metadata that is the same version as the
metadata in the existing 7.8.4 DAC Repository. For example, if the existing 7.8.4
repository contains Siebel 6.3 metadata, you need to have imported the Siebel 6.3
source system container metadata from the new Oracle BI Applications release. If you
are using Oracle BI Applications 7.9.x with the DAC 7.9.x, then you should have the
correct Siebel source system container in the 7.9.x DAC Repository.
You should also review the section "Resolving Object Differences in the View
Difference Report" to gain an understanding of your options for resolving object
To upgrade a DAC Repository in the release 7.8.4 format to the new release
1. Edit the datamapping.xml file to reflect the upgrade environment.
a. Navigate to the folder DAC\conf\upgrade
b. Open the datamapping.xml file for editing.
c. Edit the entries for folder, database connection, and subject area to reflect the
upgrade environment. See the comments in the datamapping.xml file for
2. Configure the connection between the release 7.8.4 DAC Repository and the new
a. In the Setup view, click Physical Data Sources.
b. Click New to create a new record for the 7.8.4 DAC Repository.
c. Enter the appropriate information to connect to the release 7.8.4 DAC
Repository database. For information about the required fields, see the section
"Physical Data Sources Tab".
d. Click Test Connection to confirm the connection works.
e. Click Save.
3. Navigate to the Upgrade/Merge Wizard by selecting Tools, then DAC Repository
Management, and then Upgrade/Merge Wizard.
4. From the drop-down list, select Repository Upgrade (DAC 784), and then click
The Import 7.8.4 Repository dialog box appears.
5. From the 784 Repository drop-down list, select the repository you configured in
Note: In order for a repository to appear in the drop-down list, it
must be configured in the Physical Data Sources tab of the Setup view.
6. From the Source System Container drop-down list, select the new base container
to which you are upgrading. This is the container you will compare against the
existing release 7.8.4 DAC Repository.
Caution: Make sure you select the appropriate container. If you
select a container different from that contained in the existing release
7.8.4 DAC Repository, the Difference Report will compare dissimilar
source system containers and will be inaccurate.
7. Select the categories of metadata from the existing release 7.8.4 DAC Repository
you want to import into the repository temporary tables for comparison with the
new base container. The categories are as follows:
Logical Imports all information contained in the DAC Design view and the
execution plan information for the DAC Execute view.
Run Time Imports ETL Run History and the last refresh date information.
System Imports all information contained in the DAC Setup view, except
passwords for servers and database connections.
Categories Options Description
The release 7.8.4 DAC Repository tables are imported into the temporary tables.
8. Click OK in the Importing Tables dialog box when the process is finished.
The Create Difference dialog box appears.
9. Create the Difference Report to compare the differences between the source and
target DAC repositories.
a. Enter a name for the Difference Report, or leave the default name.
b. From the Source System Container drop-down list, select the new base
c. In the New Custom Container ID/Name fields, enter an ID and a name for the
custom container that will be created during the upgrade process.
The ID and Name fields are alphanumeric. The Name field can contain spaces
and must be at least five characters long. The ID field cannot contain spaces.
d. (Optional) Enter a description for the Difference Report.
e. Click OK.
When the Difference Report is complete, the Creating Difference Report dialog
box tells you how long the process took.
f. Click OK.
The View Difference Report dialog box displays the differences between the
existing and new DAC repositories.
10. In the View Difference Report dialog box, resolve the differences between the
existing (source) and new (target) containers, that is, between the release 7.8.4
DAC Repository and the repository that contains the new base container. For
detailed information about the View Difference Report, see "Resolving Object
Differences in the View Difference Report".
To resolve the differences, you either accept or reject the objects that appear in the
release 7.8.4 DAC Repository but do not appear in the new base container to
which you are upgrading.
a. In the navigation tree, select the repository object for which you want to view
the differences between the existing and new repositories.
If the object selected in the navigation tree is a hierarchical object, the subtabs
for the child objects appear in the bottom pane of the Object Difference
b. (Optional) Filter the objects that appear in the Object Difference window by
selecting one of the options from the drop-down list in the toolbar.
c. For parent objects in the top pane and any child objects in the bottom pane,
accept or reject the object in the difference list by selecting or deselecting the
Accept Source check box.
For detailed information about these options and the merge outcome, see
"Possible Repository Merge Outcomes Based on Your Decisions".
Note: If a child object has been changed but not the parent object, the
parent object will still appear in the Object Difference window even
though it has not been changed.
d. (Optional) Once you have made a decision about whether to accept or reject
the difference, select the Resolved check box to indicate you have resolved the
e. Repeat Steps a, b, and c, until you have resolved all object differences.
f. Click Merge.
The Merge dialog box appears and lists the details of the merge.
11. Click Merge to begin the merge process.
12. Click OK in the Merging Repositories dialog box when the merge process is