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

About Migrating Repositories Between Databases

Migrate the repository and application customizations 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 target database schema. For information on migrating application customizations, see Migrating Customizations Between Applications.

For background information on Siebel repositories and schemas, see Using Siebel Tools.

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

Note the following restrictions and recommendations when migrating repositories between databases:

• Isolate development and test environments from the production environment.
• Do not migrate repository customizations to your target environment until you have completed testing to verify that the customizations work correctly and meet your business requirements.
• Do not migrate repositories between different versions of Siebel applications, as this action leads to an inconsistent environment.

Use the configuration utility, as described in Using Siebel Tools, to replace the object definitions. Then distribute a new Siebel repository file (SRF) to the servers and any remote clients. For customizations involving schema changes, you need to use the configuration utility, which:

• Updates the data in the target Siebel Server to the new schema.
• Updates the repository object definitions.

All mobile users need to synchronize prior to the schema update and (if not using Siebel Anywhere) reextract 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 Siebel 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. For further information on Siebel Anywhere, see Siebel Anywhere Administration Guide.

NOTE:  Importing a repository and then synchronizing the schema definition in a target system is equivalent to migrating the repository. However, after importing the repository and before synchronizing the schema definition, it is necessary to rename the older repository to a temporary name and give the imported repository the correct name. For further information on repository importing and exporting, see Using Siebel Tools.

After the repository migration, perform any post-repository migration tasks, if necessary. See Post-Repository Migration Tasks for information on these tasks.