This section includes the following topics:
■ Replace Base:
High-Level Process Flow
■ Replace Base: Procedure
for Upgrading
The Replace Base option
enables you to upgrade the DAC Repository when you are
phasing out an older release
of a transactional application and moving to a newer
release, for example, phasing
out Siebel 7.5.3 and moving to Siebel 7.8.
10.6.1 Replace Base:
High-Level Process Flow
Figure 10–4 shows a high-level process
flow for using the Replace Base option to
upgrade the DAC Repository
when you are phasing out an older release of a
transactional application and
moving to a newer release.
The term base is used to refer to a source
or target container that you have not changed
or customized in any way.
Figure 10–4 Upgrade Process for Replace Base Option
In Step 1 of the high-level process flow, you import the
repository data for the new
base container into the repository temporary tables. This
repository is referred to as the
source in the Upgrade/Merge Wizard
In Step 2, you create a Difference Report that compares the new
base container (source
repository) with the existing base container (including
customizations). The existing
base container is referred to as the target
In Step 3, you accept or reject the objects that the Difference
Report shows as being
present in the source but not the target or changed in the source
but not the target. See
Section 10.8.3, "Possible Repository Merge Outcomes
Based on Your Decisions" 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 DAC references the customizations in the newly merged
repository with the new
base container.
Note: The repository data is imported from a file system
and should
be in the DAC 10.1.3.4 format. If it is in the 7.9.x format, you
should do
the following:
1. Restore the repository data into a database using the
7.9.x DAC (using the
regular DAC import process).
2. Install and configure DAC 10.1.3.4 to the 7.9.x
repository.
3. Export the relevant source system container to a file
folder.
The metadata in the folder in Step 3 above will become the source
for this
upgrade.
10.6.2 Replace Base: Procedure for Upgrading
Follow this procedure to use the Replace Base option to upgrade
the DAC Repository
when you are phasing out an older release of a transactional
application and moving
to a newer release.
Before you begin this procedure you should review the section "Resolving Object
Differences in the View Difference Report" to gain an understanding of your options
for resolving object differences.
To upgrade an existing DAC Repository
1. Navigate to the Upgrade/Merge Wizard by selecting
Tools, then DAC Repository
Management, and then Upgrade/Merge Wizard.
2. From the drop-down list, select Replace Base, and
then click OK.
The Import Source System Container dialog box appears.
3. Click Change import/export folder to navigate to
the directory that holds the
metadata files for the new base container to which you are
upgrading.
4. Select the appropriate container from the Source
System Container drop-down list,
and click OK.
5. In the Importing Tables dialog box, re-type the
text in the text box to confirm you
want to proceed, and click Yes.
When the import process is complete, the Importing Tables dialog
box tells you
how long the process took.
6. Click OK.
The Create Difference Report dialog box appears.
7. Create the Difference Report to view the
differences between the new and existing
DAC repositories.
a. Enter a name for the Difference Report, or leave
the default name.
b. Select the appropriate existing container.
c. (Optional) Enter a description for the Difference
Report.
d. Click OK.
When the Difference Report is complete, the Creating Difference
Report dialog
box tells you how long the process took.
e. Click OK.
No comments:
Post a Comment