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

Guidelines for Migrating a Repository

If you migrate a repository, then it is recommended that you use the following guidelines:

• Isolate development and test environments from the production environment.
• Do not migrate a repository between two databases that use different releases or patch levels. To avoid an inconsistent environment, do not migrate repositories between different versions of Siebel applications.
• If your migration requires special parameter settings that batch files cannot access, or if you must do a file dump, then use the Repository Import and Export Utility. For more information, see Using the Repository Import and Export Utility.
• Use a consistent naming convention for the source repository and the target repository. You can rename the target repository to indicate that you replaced it during a migration. For more information, see Guidelines for Naming a Repository.
• Do not modify ODBC parameters or settings for the data sources that you created when you configured the Siebel Server when you installed Siebel CRM. A repository migration references one ODBC data source for the source database and another ODBC data source for the target database. This requirement applies to all servers and databases. For more information about verifying the ODBC data source, see the Siebel Installation Guide for the operating system you are using.
• Consider time required to export over a WAN. It is more efficient to export the file on the source environment, and then copy the exported file to the target environment. If you migrate a repository over a wide area network (WAN), and if you run the Database Configuration Wizard from the target environment, then Siebel CRM only exports the source repository to a flat file. All other processing occurs on the local area network (LAN) of the target environment.
• If you defined a custom tablespace on IBM DB2 for z/OS, then this tablespace might affect the Database Configuration Wizard. For more information, see Implementing Siebel Business Applications on DB2 for z/OS.