Siebel Anywhere Administration Guide > Performing Additional Siebel Anywhere Tasks > Process of Updating the Siebel Database Schema >

Installing Siebel Database Schema Changes on Siebel Regional Node Servers

In a test environment, install the Siebel Database Schema upgrade kit (and any accompanying upgrade kits) on test Siebel Regional Node Servers. In a production environment, install the Siebel Database Schema upgrade kit (and any accompanying upgrade kits) on production Regional Node Servers. The following procedure describes how to install a Siebel database schema update on a Regional Node Server.

This task is a step in Process of Updating the Siebel Database Schema.

Installing the Siebel Database Schema upgrade kit synchronizes the logical and physical schemas on Regional Node Server databases.

NOTE:  If any of your Mobile Web Client users connect to a Regional Node Server, rather than the HQ Server, then the Regional Node Server must install the Siebel database schema changes before those mobile users can obtain and install the changes.

To install a Siebel Database Schema upgrade kit for regional databases

1. Disconnect all users from the Regional Node Servers and the HQ Server.
2. Stop all tasks on the Siebel Servers except those for the Replication Agent, Transaction Processor, Router, and Merger components.
3. Wait until the replication backlog has been processed.

   Check the download and upload statistics in the Administration - Siebel Remote screen for each Regional Node. The three Last File and Last Transaction numbers match in the lower applet. Make sure that there are no outstanding transactions by checking that the docking\inbox and docking\outbox directories are empty on the regional Siebel Servers.

4. Verify that the server parameter Version Check is set to TRUE on the regional Siebel Server by using one of the following methods:
   • In the Server Parameters view, verify that the server parameter Version Check is set to TRUE on the regional Siebel Server.
   • Use the following commands to start srvrmgr and verify the value of the Version Check parameter:

   srvrmgr /g gateway_host /e enterprise_server /s server_name
   /u user_name /p password

   list param VersionCheck

5. The Replication Agent now performs a version check and shuts down itself and the regional Siebel Server so the Siebel administrator can perform the upgrade manually.
6. Check the appropriate log files (RepAgent.log and syncthrd.log) to verify whether you need to run the Upgrade Wizard.
7. Verify that the Siebel Server is properly shut down. If not, then shut it down manually.
8. Use one of the following methods to run the Upgrade Wizard:
   • In a Windows environment, in the server bin directory, run siebupg.exe to perform the upgrade.
   • In a UNIX environment, in the server bin directory, run srvrupgwiz to perform the upgrade.
9. After the upgrade, bring up the regional Siebel Server.
10. You can change the server parameter Version Check back to False, which is its default value.

    NOTE:  When you install the Siebel Database Schema upgrade kit, the schema changes are applied to the server and the custom version is incremented, which makes the database template obsolete. If there are Mobile Web Client users who connect to the Regional Node Server, then you must run Generate New Database task to create a new database template.

Mobile Web Clients can synchronize and install the Siebel Database Schema upgrade kit in much the same manner as any other upgrade kits by using the Upgrade Wizard.

If the Siebel Business Applications developer created or modified applets or views to display data in new extension columns or new extension tables, then it is necessary to create and distribute the accompanying Siebel Repository File upgrade kit. Installing the combination of the Siebel Database Schema upgrade kit and the Siebel Repository File upgrade kit allows users to view these data after the schema upgrade.

After the Siebel database schema upgrade is finished, distribute the new SRF upgrade kit to its corresponding Mobile Web Clients.