Refresh Base

10.4 About the Refresh Base Option

This section includes the following topics:

■ Refresh Base: High-Level Process Flow

■ Refresh Base: Procedure for Upgrading

The Refresh Base option enables you to upgrade an existing customized DAC

Repository. You should use this option if you are upgrading from a DAC release

higher than 7.8.4. If you are upgrading a DAC Repository in the release 7.8.4 format or

lower-numbered releases, see "About the Repository Upgrade (DAC 784) Option".

The Refresh Base option enables you to compare a new base container with the

existing customized repository and to create a Difference Report. If you want to

upgrade an existing customized DAC Repository without comparing repositories and

creating a Difference Report, you can use the Simplified Refresh From Base option. See

"About the Simplified Refresh From Base Option" for more information.

10.4.1 Refresh Base: High-Level Process Flow

Figure 10–3 shows a high-level process flow for using the Refresh Base option to

upgrade existing customized repositories from DAC releases higher than 7.8.4, such as

Oracle BI Applications 7.9 and higher.

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–3 Upgrade Process for Refresh Base Option

In Step 1 of the high-level process flow, you import the repository data for the new

base container from the file system 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 with

the existing repository (including customizations). The existing customized repository

is referred to as the target.

In Step 3, you accept or reject the objects that the Difference Report shows as being

present 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.4.2 Refresh Base: Procedure for Upgrading

Follow this procedure to use the Refresh Base option to upgrade an existing

customized repository from DAC releases higher than 7.8.4.

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 repository using the Refresh Base option

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 Refresh 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 container to which you are upgrading 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.

The View Difference Report dialog box displays the differences between the

new and existing DAC repositories.

8. In the View Difference Report dialog box, resolve the differences between the new

repository (source) and existing repository (target). 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 are listed as

new or changed in the new repository (the version to which you are upgrading).

a. In the navigation tree, select the repository object for which you want to view

the differences between the new and existing 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

window.

b. (Optional) Filter the objects that appear in the top, right 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

object.

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.

9. Click Merge to begin the merge process.

10. Click OK in the Merging Repositories dialog box when the merge process is

complete.