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

Preparing to Migrate Repositories

In this topic, you prepare to migrate the repository.

This task is a step in Process of Migrating Repositories.

To prepare to migrate repositories

1. Make sure you complete testing.

   You must verify that any customizations you make work correctly, and that they meet your business requirements.

2. Make sure the target database configuration meets the database requirements.

   For more information, see the Siebel Installation Guide for the operating system you are using and Siebel System Requirements and Supported Platforms on Oracle Technology Network.

   NOTE:  For Siebel CRM product releases 8.1.1.9 and later and for 8.2.2.2 and later, the system requirements and supported platform certifications are available from the Certification tab on My Oracle Support. For information about the Certification application, see article 1492194.1 (Article ID) on My Oracle Support.

3. Check in all projects in the source database and in the target database.

   If a project is checked out, and if you migrate a database, then the migration works but Siebel CRM does not lock the project in the target database. For more information, see Checking Out and Checking In Projects and Objects.

4. If your environment includes Remote users, then make sure all these users do a full synchronization.
5. Do a full backup of the target database.
6. Delete old repositories from the target database.

   For more information, see Deleting Repositories.

7. Update database statistics, if necessary.
8. Export the source repository to a file.

   It is recommended that you use the Database Configuration Wizard to export the source repository to a file. You use this file later during a migration. For more information, see Exporting Repositories.

   You can also migrate directly from the source database. If you do this, then you do not need to export the source repository to a file.

9. Stop all Siebel Server tasks and disconnect all database access.

   If you do not need to minimize downtime during a migration, then it is recommended that you stop all Siebel Server tasks and disconnect all database access until the migration finishes. This downtime occurs in the Siebel Enterprise where the target repository resides.