Going Live with Siebel Business Applications > Migrating Repositories Between Databases >

Preparing to Run the Repository Migration Configuration Utility

The repository migration process differs based on several selections made during the running of the repository migration configuration utility. Depending on your selections, some preparatory tasks may be required before running this utility.

This task is a part of the Process for Migrating Repositories. For background information on migrating repositories, see About Migrating Repositories Between Databases.

The three repository migration selections of note are:

• Source Repository Selection. For information on this selection, see Preparing for Source Repository Selection.
• Target Environment Status. For information on this selection, see Preparing for Target Environment Status Selection.
• Schema Changes Selection. For information on this selection, see Preparing for Schema Changes Selection.

See Figure 1 for a high-level view of the repository migration utility screen flow based on the different source repository selections.

Figure 1. High-level View of Repository Migration by Source Repository Selection

Preparing for Source Repository Selection

The source repository selection allows the administrator to migrate the repository:

• By creating a source repository file (Recommended)

  If using this source repository migration selection, create a source repository migration file before running the repository migration utility. For information on this task, see the following section, Creating a Source Repository Migration File.

• Directly from the source database

  If using this source repository migration selection, no preparations are required.

Preparing for Target Environment Status Selection

The target environment status selection allows the administrator the option to import the repository while the target Siebel application is online, which lessens the downtime of the target environment.

To use this option, select the following at the Target Environment Status screen when running the repository migration configuration utility:

• The Target Enterprise will be online when the migration starts.

Selecting this option allows the administrator to run a repository migration process—a portion of which does not require the target environment to be offline—until it is absolutely necessary that the target environment be shutdown. At that point during the repository migration process, a dialog box appears informing the administrator to shut down the target environment for the remainder of the migration.

NOTE:  If you are planning to run the repository migration unattended, for example, by script, do not select the online option.

Preparing for Schema Changes Selection

The schema changes selection allows the administrator the option not to run the schema migration portion of the repository migration process, which lessens the amount of time required for the migration process.

To use this option, select the following option at the Schema Changes screen when running the repository migration configuration utility:

• There are no new schema changes.

Selecting this option allows the administrator to skip the schema upgrade portion of the repository migration process if there are no changes to apply to the target's physical or logical schema. Examples of schema updates include the addition of an extension column to an existing table or the addition of a new extension table.

If in doubt, select the option;

• There are new schema changes to be applied.