Bookshelf Home | Contents | Index | Search | PDF |
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
- 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.
- Wait until the transactions have been applied to the Regional Node.
- 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.
- Wait until the transactions are applied to the Parent Node.
- If appropriate, disconnect the connected users on the Parent Node.
- Stop the server components as appropriate.
- Apply the upgraded repository to the Headquarters Node and synchronize the repository with the physical schema.
- Allow connected users at the Headquarters Node to reconnect and continue working using the new SRF file.
- Use Generate New Database to generate a new database template on the Parent Node.
- On the Parent Node, perform a database extract of the Regional Node.
- Initialize the Regional Node.
- Allow connected users at the Regional Node to reconnect and to resume work using the new SRF file.
- Generate a new database template on the Regional Node.
- Extract each Mobile Web Client on the Regional Node.
- Allow mobile users to reinitialize their local databases and to resume work using the new SRF file.
Bookshelf Home | Contents | Index | Search | PDF |
Siebel Remote and Replication Manager Administration Guide Published: 19 November 2003 |