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

Updating Siebel Remote Databases

This task is a step in Process of Migrating a Repository.

If your environment includes Remote users, then you must update Siebel Remote databases. For more information about performing the steps in this topic, see Siebel Remote and Replication Manager Administration Guide.

To update Siebel Remote databases

1. Stop and restart Siebel Remote server components.
2. Wait for the Transaction Processor (TxnProc) and the Transaction Router (TxnRoute) server components to finish processing all pending transactions.
3. Regenerate the local database templates.

   Use the Generate New Database server component (GenNewDb) to regenerate the local database template file. This step updates this template file so that it uses the same schema and version that the server database uses.

4. Reextract the local database for all Remote users.

   If you do not use Siebel Anywhere to update Remote clients, then you must use the Database Extract (DbXtract) server component to extract the local database for all remote users.

   If you do not extract these databases, then Remote users can synchronize but Siebel CRM will not create any error message even though these databases might not include the migration modifications. This configuration allows users who use Siebel Anywhere to upgrade their Remote databases to continue working.

Using Siebel Anywhere to Update Remote Databases

You can use Siebel Anywhere to update some Remote databases. Importing a repository and then synchronizing the schema definition in a target environment is equivalent to migrating the repository. The Remote users must synchronize the next time they log in to their local database after the migration finishes. Synchronizing downloads new schema modifications from the Siebel Server to the local database that the Remote user uses. Before synchronization occurs, you must rename the older repository to a temporary name and rename the imported repository to the correct name. If a Remote user does not synchronize, then the data that the local database contains does not match the data that the server database contains. For more information, see Siebel Anywhere Administration Guide.