Using Siebel Tools > Managing Repositories > Process of Migrating Repositories >

Using the Database Configuration Wizard to Migrate Repositories

In this topic, you use the Database Configuration Wizard to migrate repositories.

This task is a step in Process of Migrating Repositories.

To use the Database Configuration Wizard to migrate repositories

1. Make sure all users, including the database administrator, disconnect from the Siebel application.
2. Start the Database Configuration Wizard according to the following operating system that you are using:
   • Windows. Do Step 1 through Step 5.
   • UNIX. Do Step 1 through Step 5.
3. In the Database Configuration Wizard, click Migrate Repository when the wizard prompts you to choose a database operation, and then click Next.

   For important caution information, see Caution About Migrating a Repository.

4. Choose to get the source repository from one of the following items, and then click Next:
   • Get from a file. If you choose this option, then the wizard displays the Repository File Selection window. Enter the path and the file name of the source repository file that you created in Step 8, and then click Next.
   • Get from the database.
5. Specify whether or not the target enterprise is online or offline, and then click Next:
   • Online.
   • Offline.

     If you choose the online option, then Siebel CRM keeps the Siebel Enterprise where the target repository resides online during the migration until it must shut down this environment. When it must do this shut down, it displays a dialog box that informs you that it will shut down the target environment during the remainder of the migration. This option allows you to minimize the amount of downtime during a migration. If you run this migration unattended, then do not choose this online option. Running this migration from a script is an example of running it unattended.

6. Choose one of the options, and then click Next:
   • There are new schema changes to be applied. Choose this option if the source repository includes any physical or logical schema modifications. Examples of schema modifications include adding an extension column to an existing table, or adding a new extension table. If you are not sure whether or not any schema modifications exist, then it is recommended that you choose this option.
   • There are no new schema changes. Choose this option if the source repository does not include any physical or logical schema modifications. If you choose this option, then the Database Configuration Wizard requires less time to finish the migration.
7. If in Step 4 you choose to get the source repository:
   • From a file. The wizard displays the Target Repository Name window. Enter the target repository name, and then click Next.
   • From the database. The wizard displays the series of dialog boxes that require you to define the source database. Use information from the following table to complete each of these dialog boxes.

     Dialog Box	Description
     ODBC Data Source Name	Enter the ODBC data source name.
     Database User Name	Enter the user name and password for the source database.
     Database Table Owner	Enter the table owner and table owner password for the source database.
     Source Database Repository Name	Enter the source database repository name and the target database repository name.

8. Complete the information in the following windows, and then click Next.

   The sequence that the wizard uses to display these windows and the information that you enter might vary slightly depending on whether or not your environment uses Windows or UNIX, or the type of database that your environment uses. The wizard does not display any windows for Microsoft SQL Server.

   Window	Description
   RDBMS Platform	For UNIX only. Choose an RDBMS platform.
   Target Database Encoding	Choose whether or not the target database is Unicode. Consult with your DBA regarding how to set up the target database.
   Target Database Repository Name	Enter the repository name of the target database.
   Target RDBMS Platform	Choose the target RDBMS platform.
   Target Database ODBC Datasource	Enter the ODBC data source for the target database.
   Target Database User Name	Enter the user name and password that the server components that reside on the target database use.
   Target Database Table Owner	Enter the table owner and the table owner password for the target database.
   Index Table Space Name	If you choose IBM DB2 for the target database platform, then the wizard displays the Index Table Space Name dialog box. Enter the index tablespace name and 4KB tablespace name.
   16K Table Space Name	If you choose IBM DB2 for the target database platform, then the wizard displays the 16K Table Space Name dialog box. Enter the 16KB tablespace name and the 32KB tablespace name.
   Index Table Space Name	If you choose Oracle Database for the target database platform, then the wizard displays the Index Table Space Name dialog box.

9. If the wizard displays a Language Selection window, then choose the appropriate language, and then click Next.

   The wizard migrates strings from the repository that uses the language that you choose. If you migrate a repository in a multilingual environment, and if the source repository includes duplicate strings in multiple languages, then the wizard copies all of these strings to the target repository.

10. Finish the migration, depending on the following operating system that your environment uses:
    • Windows. Do Step 8 through Step 11.
    • UNIX. Do Step 7 through Step 9.
11. Wait for the wizard to finish the migration.

    The Database Configuration Wizard does the following work:

    • Exports the source repository from a file. You can also export the repository for the database.
    • Imports the repository into the target database.
    • If you choose to apply new schema modifications in Step 6, then the wizard does the following work:
      • Exports the logical schema definition from the source repository to a control file.
      • Synchronizes the physical schema of the target database with this logical schema definition.

Caution About Migrating a Repository

If you migrate a custom repository, then you must use the Migrate Repository option in the Database Configuration Wizard.

CAUTION:  If you migrate a custom repository and schema from one environment to another environment, such as migrating from a development environment to a test environment, then do not use the Export/Import option in the Database Configuration Wizard. Instead, you must use the Migrate Repository option.

This Migrate Repository option calls the Repository Migration Utility (dev2prod). If you use the Repository Migration Utility directly instead of calling it from the Database Configuration Wizard, then you must reset the Locked and Allow Object Locking columns after you finish the migration. For more information, see Allowing Object Locking for a Project.