Siebel Remote and Replication Manager Administration Guide > Upgrading Regional Nodes >

Repository Upgrade Without Siebel Anywhere

This section describes upgrading a repository without the Siebel Anywhere option.

To upgrade a repository without Siebel Anywhere

1. If the Regional Node has mobile users, instruct the mobile users to synchronize with the Regional Node and to stop working on their local databases until further notice.

   NOTE:  After synchronizing, mobile users should not make any changes to their local databases until after their databases have been reinitialized. Changes made after this point will be lost.

2. Wait until the transactions have been applied to the Regional Node.
3. Run Replication Agent to synchronize the Regional Node with the Parent Node. This is usually the Headquarters Node.

   NOTE:  No more changes should be made to the Regional Node until after it has been reinitialized. Changes made after this point will be lost.

4. Wait until the transactions are applied to the Parent Node.
5. If appropriate, disconnect the connected users on the Parent Node.
6. Stop the server components as appropriate.
7. Apply the upgraded repository to the Headquarters Node and synchronize the repository with the physical schema.
8. Allow connected users at the Headquarters Node to reconnect and continue working using the new SRF file.
9. Use Generate New Database to generate a new database template on the Parent Node.
10. On the Parent Node, perform a database extract of the Regional Node.
11. Initialize the Regional Node.
12. Allow connected users at the Regional Node to reconnect and to resume work using the new SRF file.
13. Generate a new database template on the Regional Node.
14. Extract each Mobile Web Client on the Regional Node.
15. Allow mobile users to reinitialize their local databases and to resume work using the new SRF file.