Bookshelf Home | Contents | Index | Search | PDF

Siebel Tools Reference > Repositories > Renaming, Deleting, Backing Up, and Migrating Repositories >

Migrating Repositories and Schemas Between Databases

---

It is recommended that you have development and test environments that are isolated from the production environment.

The repository and user data need to be migrated in parallel between databases so the database schema for the user data, the business objects, and the user interface remain synchronized. Populate the test database, and when sufficient testing has taken place, migrate the repository and update the production database schema.

For information about setting up your system and database environment, see the Siebel Server Installation Guide for your operating system.

CAUTION:  Do not migrate repositories between different versions of Siebel applications, as this will lead to an inconsistent environment.

If you configure only business object and user interface object definitions, you need to replace only the object definitions in the production repository with those in the development repository. Do this using the configuration utility, as described in Backing Up and Restoring Repositories. Then distribute a new .srf file to client computers.

However, for upgrades involving schema changes, you need to use the configuration utility, which:

• Upgrades the data in the production server to the new schema
• Updates the repository object definitions

All mobile users need to synchronize prior to the upgrade and (if not using Siebel Anywhere) re-extract following the upgrade.

If you are using Siebel Anywhere, mobile users need to synchronize the next time they log on to their local database after the migration has occurred. Synchronizing will download new schema changes from the server to the mobile user's local database. If they do not synchronize, there will be a mismatch between the local database and the server database.

It is recommended that you follow these major steps to migrate a repository and schema from one database to another. The first three steps are described in the following sections. The final step is an application administration task, and is described in Applications Administration Guide.

• Check in all projects—in both the source and target databases.

  If you migrate a database schema with some projects still checked out, the migration will work but the project state will be not locked in the target database.

• Prepare the target database for the new repository.

  The Target Repository parameter should be the name of a repository that does not already exist in the target database. Rename the current production repository if you already have one, for example, to Old Repository.

• Run the repository migration configuration utility.

  NOTE:  Siebel eBusiness Applications version 7.0 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.

• Upgrade mobile databases that are dependent on the target database.
• If you move a repository from one database to another, such as from development to test, you need to also re-create any new views, responsibilities, and list of values entries in the new environment.

Preparing the Target Database for the New Repository

Complete the following actions before you migrate the repository to the target database:

• Make sure that all mobile users perform a full synchronization to avoid any unexpected issues in a production environment as a result of database schema changes made to the new repository.
• Stop all server tasks and disconnect all database access until migration has been successfully executed.

  NOTE:  All connected users (including the database administrator) must disconnect before running the repository migration Configuration Utility.

• Do a full backup of the production database once all mobile user transactions have been merged.
• Make sure that the production database configuration meets the database requirements outlined in the Siebel Server installation guide for your operating system.
• Verify the names of all repositories in the target database.

  You will later choose a new name that the repository being migrated will have in the target database. Siebel Systems recommends that you keep the name of your production repository constant. Accordingly, rename the existing production repository to show that it has been superseded. You will also later import a repository, to which you should give the standard name for your production repository.

Running the Repository Migration Configuration

NOTE:  When you are 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.

The configuration utility does the following:

• Exports the designated repository from the source database
• Imports the designated repository into the target database
• Exports the logical schema definition from the specified repository to a .ddl file
• Synchronizes the physical schema of the target database with this logical schema definition
• (If you are using Siebel Anywhere) propagates new repository schema changes to mobile users

NOTE:  If you have custom table spaces defined, the Database Server Configuration Utility used in the migration process is tablespace-aware.

To migrate a repository under 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 Gateway Server Address and Enterprise Server Name and click Next.

   The Siebel Server Directory dialog box appears.

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

   The Siebel Database Server Directory dialog box appears.

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

   The RDBMS Platform dialog box appears.

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

   The Siebel Database Operations dialog appears.

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

   The following succession of dialog boxes appears.

7. Progress by completing the information in each dialog box, and then clicking Next.

   Dialog Box	Description
   ODBC Data Source Name	Enter the ODBC Data Source Name.
   Database User Name	Enter the Database User Name and Database Password.
   Database Table Owner	Enter the Target Database Table Owner and Table Owner Password.
   Source Database Repository Name	Enter the Database Repository Name and the Target Database Repository Name.
   Target RDBMS Platform	Select the Target RDBMS Platform. IBM DB2 UDB v7.1 is the default.
   Target Database Encoding	Select whether or not the target database is Unicode.
   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 dialog box. 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 dialog box. 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 DB 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 dialog boxes about tablespaces.
   Configuration Parameter Review	Summary dialog box gives a list of your choices. You can accept this configuration by clicking Finish.

To migrate the schema under UNIX

1. Source environment variables from $SIEBEL_ROOT by typing:

   source siebenv.csh

2. Set the following environment variables:
   • SIEBEL_ROOT should be the path of your Siebel eBusiness 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 ENU (where ENU represents your display language)
   • setenv SIEBEL_ENTERPRISE <Enterprise Name>
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. Progress by completing the information in each screen.

   Dialog Box	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.
   ODBC Data Source Name	Enter the ODBC Data Source Name.
   Database User Name	Enter the Database User Name and Database Password.
   Database Table Owner	Enter the Target Database Table Owner and Table Owner Password.
   Source Database Repository Name	Enter the Source Database Repository Name.
   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.
   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 dialog box. 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, you get this dialog box. 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 DB Platform, you have only two questions about Index and Table space. There are no 4K, 16K, and 32K tablespaces in Oracle. For Microsoft SQL server, there are no dialog boxes about tablespaces.
   Configuration Parameter Review	Summary dialog box gives a list of your choices. You can accept this configuration by entering Y.

NOTE:  Updating statistics with a full table scan is the job of the DBA once any repository migration, upgrade, or installation finishes.

Upgrading Mobile Databases

Follow these steps:

1. Restart Siebel Remote processes.

   If you have mobile users in your target database environment, restart the Application Server Processes, regardless of whether you are using Siebel Anywhere.

   When you have restarted the processes, wait until the Transaction Pre-Processor and the Transaction Router have processed all pending transactions before proceeding with the remaining steps.

2. Regenerate local database templates.

   Use the Siebel Server component Generate New Database to regenerate the local database template file to update its schema to the same version as the database server.

3. Re-extract mobile users.

   If you are not using Siebel Anywhere to upgrade your mobile clients, re-extract all mobile users, using the Database Extract Component.

   Make sure that you have copied the new database template to all production Siebel Remote Servers before re-extracting the mobile users. The distmpl.ksh (check) helps you copy the database template.

   NOTE:  However, if mobile databases are not reextracted, users will still be able to synchronize—no error message will be generated. This is to allow Siebel Anywhere, which users might use to upgrade mobile databases, to continue working.

   If you are using Siebel Anywhere, refer to Developing and Deploying Siebel eBusiness Applications for instructions on propagating schema extensions.

Bookshelf Home | Contents | Index | Search | PDF