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

Running the Repository Migration Configuration Utility

This topic describes the task of running the repository migration configuration utility. This task is a part of the Process for Migrating Repositories. For background information on migrating repositories, see About Migrating Repositories Between Databases.

Running the configuration utility achieves the following results:

• Exports the designated repository from the source database or reads the source repository from file.
• Imports the designated repository into the target database
• Exports the logical schema definition from the specified repository to a control file
• Synchronizes the physical schema of the target database with this logical schema definition

NOTE:  The repository migration configuration utility skips the previous two schema-related steps if you select no schema changes while running the utility.

Take note of the following items before running a repository migration:

• When migrating repositories over a wide area network (WAN) and running the repository migration utility from the target environment, only the process of exporting the source repository to a flat file takes place on the WAN. All other processing takes place on the local area network (LAN) of the target environment. Consider the export processing times when processing the export over a WAN. The most efficient option is to export the file on the source then transport the exported file to the target environment.
• For multilingual installations where the source respiratory contains additional language strings, all languages are copied with the repository to the target environment.
• Siebel Business Applications version 7.x do not support customized database triggers. If you have created customized triggers on your Siebel base tables, you must disable them before migrating the schema. You will then need to recreate the triggers after the migration is finished.

NOTE:  If you have a custom table space defined on DB2 UDB for OS/390, the Database Server Configuration Utility used in the migration process is tablespace-aware.

To migrate a repository on Windows

1. Launch the Database Server Configuration Utility by choosing Start > Programs > Siebel Enterprise Server version_number > Configure DB Server.

   The Gateway Server Address screen appears.

2. Specify your Siebel Gateway Name Server Address and Enterprise Server Name and click Next.

   The Siebel Server Directory screen appears.

3. In the Siebel Server Directory screen, either accept the default value or choose the Browse button to select a directory, and then click Next.

   The Siebel Database Server Directory screen appears.

4. In the Siebel Database Server Directory screen, either accept the default value or choose the Browse button to select a directory, and then click Next.

   The RDBMS Platform screen appears.

5. In the RDBMS Platform screen, select the platform for your environment and then click Next.

   The Siebel Database Operations screen appears.

6. In the Siebel Database Operations screen, select Migrate Repository from the list of operations, and then click Next.

   The Source Repository Selection screen appears.

7. In the Source Repository Selection screen, select to read the source repository from the database or from a previously exported file.
   • If you select to read the source repository from file, the Repository File Selection screen appears.

     Enter the path and filename of the source repository file and click Next. The Target Environment Status screen appears.

     For background information on creating a source repository file, seeCreating a Source Repository Migration File.

   • If you select to read the source repository directly from the database, the Target Environment Status screen appears.
8. In the Target Environment Status screen, select whether the target Siebel enterprise will be online or offline, and click Next. For further information on this selection, see Preparing for Target Environment Status Selection.
9. In the Schema Changes screen, select whether there are new schema changes to be applied during the repository migration, and click Next. For further information on this selection, see Preparing for Schema Changes Selection.
10. In the Language Selection screen, select the appropriate language, and then click Next.

    NOTE:  The repository migration process migrates all language strings within the repository. Select the base language installation that applies for this screen.

11. The next succession of screens are dependent on the repository source selection:
    • If you chose to read the source repository from file, the Target Repository Name screen appears. Enter the target repository name, and click next.
    • If you chose to read the source directly from database, the following succession of screens appears to define the source database.

      Screen	Description
      ODBC Data Source Name	If you chose to read the source repository from the database, enter the ODBC data source name.
      Database User Name	If you chose to read the source repository from the database, enter the source database user name and source database password.
      Database Table Owner	If you chose to read the source repository from the database, enter the source database table owner and source table owner password.
      Source Database Repository Name	If you chose to read the source repository from the database, enter the database repository name and the target database repository name.

12. Progress by completing the information in the following screens, and then clicking Next.

    Screen	Description
    Target RDBMS Platform	Select the target RDBMS platform. IBM DB2 UDB v7.1 is the default.
    Target Database Encoding	Select whether the target database is Unicode. Consult with your DBA on the setup of the target database.
    Target Database ODBC Datasource	Enter the target database ODBC datasource.
    Target Database User Name	Enter the target database user name and password.
    Target Database Table Owner	Enter the target database table owner and table owner password.
    Index Table Space Name (DB2-specific)	If you choose IBM DB2 for the target database platform, you get this screen. Enter the index table space name and 4-KB Table Space Name.
    16-KB Table Space Name (DB2-specific)	If you choose IBM DB2 for the target database platform, you get this screen. Enter the 16-KB table space name and 32-KB table space name.
    Index Table Space Name (Oracle-specific)	If you choose Oracle as the target database platform, you have only two questions about index and table space. There are no 4-KB, 16-KB, and 32-KB tablespaces in Oracle. For Microsoft SQL server, there are no screens about tablespaces.

13. After the last screen in the previous step, a dialog box appears prompting you to run the repository migration now or at a later date. Click OK to begin the repository migration process, and CANCEL to run the migration process at a later date.
    • If you select OK, a Configuration Parameter Review screen appears. Review this screen to check your configurations.
    • If you select CANCEL, run the migration process at a later date by navigating to the bin subfolder of the Siebel Server root directory and entering the following command:

    Siebupg /m master_dev2prod.ucf

To migrate the repository on UNIX

1. Source environment variables from $SIEBEL_ROOT by typing:

   source siebenv.sh

   or

   source siebenv.csh

2. Set the following environment variables:
   • SIEBEL_ROOT should be the path of your Siebel Business Application installation directory.
   • LANGUAGE should be set to the language in which the Configuration Wizard prompts appear; for example, ENU for U.S. English.

     If either of these values is incorrect or empty, reset them using one of the following commands:

   • setenv LANGUAGE language_code (where language_code represents your display language)
   • setenv SIEBEL_ROOT Installation_directory_path
3. Navigate to $SIEBEL_ROOT/bin and enter:

   dbsrvr_config.ksh

   This launches the Database Server Configuration Wizard.

4. Review the values of the following environment variables and confirm whether or not the settings are correct by entering either Y or N.
   • SIEBEL_ROOT
   • LANGUAGE

     NOTE: If either the SIEBEL_ROOT or LANGUAGE value is not set or is incorrect, you must correct them before proceeding.

5. Specify the path of your Siebel Server root directory, or accept the default by pressing ENTER.
6. Specify the path of your database server root directory, or accept the default by pressing ENTER.
7. Enter the number that corresponds to your database platform.
8. From the Select Repository Operations menu, choose Migrate Repository (4).
9. From the Source Repository Selection menu, select to read the source repository from the database or from a previously exported file.
   • If you select to read the source repository from file, the Repository File Name menu appears.

     Enter the path and filename of the source repository file and click Next. The Target Environment Status menu appears.

     For background information on creating a source repository file, seeCreating a Source Repository Migration File.

   • If you select to read the source directly from the database, the Target Environment Status menu appears.
   • In the Target Environment Status menu, select whether the target environment will be online or offline, and click Next. For further information on this selection, see Preparing for Target Environment Status Selection.
10. In the Target Environment Status screen, select whether the target environment will be online or offline, and click Next. For further information on this selection, see Preparing for Target Environment Status Selection.
11. In the Schema Changes menu, select whether there are new schema changes to be applied during the repository migration, and click Next. For further information on this selection, see Preparing for Schema Changes Selection.
12. In the Language Selection screen, select the appropriate language, and then click Next.

    NOTE:  The repository migration process migrates all language strings within the repository. Select the base language installation that applies for this screen.

13. The next succession of screens are dependent on the repository source selection:
    • If you chose to read the source repository from file, the Target Repository Name screen appears. Enter the target repository name, and click next.
    • If you chose to read the source directly from database, the following succession of screens appears to define the source database.

      Screen	Description
      ODBC Data Source Name	If you chose to read the source repository from the database, enter the ODBC data source name.
      Database User Name	If you chose to read the source repository from the database, enter the source database user name and source database password.
      Database Table Owner	If you chose to read the source repository from the database, enter the source database table owner and source table owner password.
      Source Database Repository Name	If you chose to read the source repository from the database, enter the database repository name and the target database repository name.

14. Progress by completing the information in each screen.

    Screen	Description
    RDBMS Platform	Select an RDBMS platform. IBM DB2 UDB v7.1 is the default.
    Target Database Encoding	Select whether or not the target database is Unicode.
    Target Database Repository Name	Enter the target database repository name.
    Target RDBMS Platform	Select the target RDBMS platform. IBM DB2 UDB v7.1 is the default.
    Target Database ODBC Datasource	Enter the target database ODBC datasource.
    Target Database User Name	Enter the target database user name and password used by the server components.
    Target Database Table Owner	Enter the target database table owner and table owner password.
    Index Table Space Name (DB2-specific)	If you choose IBM DB2 for the target database platform, this screen appears. Enter the index table space name and 4-KB table space name.
    16K Table Space Name (DB2-specific)	If you choose IBM DB2 for the target database platform, this screen appears. Enter the 16-KB table space name and 32-KB table space name.
    Index Table Space Name (Oracle-specific)	If you choose Oracle as the target database platform, you have only two questions about index and table space. There are no 4-KB, 16-KB, and 32-KB tablespaces in Oracle. For Microsoft SQL server, there are no screens about tablespaces.

15. After the last screen in the previous step, a dialog box appears prompting you to run the repository migration now or at a later date. Click OK to begin the repository migration process, and CANCEL to run the migration process at a later date.
    • If you select OK, a Configuration Parameter Review screen appears. Review this screen to check your configurations.
    • If you select CANCEL, run the migration process at a later date by navigating to the bin subfolder of the Siebel Server root directory and entering the following command:

    Srvrupgwiz /m master_dev2prod.ucf

NOTE:  Updating statistics is the job of the database administrator once any repository migration, upgrade, or installation finishes.