Bookshelf Home | Contents | Index | Search | PDF

Siebel Tools Reference > Adding Custom Extensions to the Data Model > Applying the Changes to the Server Database >

Applying Schema Changes Using the Configuration Utility

---

Complete the steps in this section only if you are unable to apply schema changes to the server database as discussed in the previous section.

NOTE:  Stop the Siebel Server before running the Database Server Configuration Utility. Otherwise, the task can fail due to a locking issue.

The Configuration Utility performs the following sequence of steps:

• Exports logical schema definition from the specified repository to the .ddl file.
• Synchronizes the physical schema of the application database with this logical schema definition.
• Propagates new repository schema changes to mobile users (if Siebel Anywhere is being used).

To migrate the schema under Windows

1. If you are not using Siebel Anywhere, stop all processes running on all Siebel Application Servers, including all Siebel Remote Processes, once all mobile user transactions have been merged and routed.

   If you are using Siebel Anywhere, stop all Siebel Application Server processes except the Transaction Preprocessor and Transaction Routers.

2. Launch the Database Server Configuration Utility by choosing Start > Programs > Siebel Enterprise Server version_number > Configure DB Server.

   The Gateway Server Address screen appears.

3. Specify your Gateway Server Address and Enterprise Server Name and click Next.

   The Installation and Configuration Parameters: Siebel Server Directory dialog box appears.

4. In the Siebel Server Directory dialog box, either accept the default value or choose the Browse button to select a directory, and then click Next.

   The Siebel Database Server Directory dialog box appears.

5. Either accept the default value or choose the Browse button to select a directory, and then click Next.

   The RDBMS Platform dialog box appears.

6. Choose your db platform and click Next.

   NOTE:  The default is DB2 UDB.

   The Siebel Database Operation dialog box appears.

7. Choose Run Database Utilities and click Next.

   The Database Utility Selection dialog box appears.

8. Choose Synchronize Schema Definition and click Next.
9. The next dialog boxes are described as follows:
   • Database Encoding: enter whether or not the database is Unicode or Non-Unicode.
   • ODBC Datasource Name dialog box
   • Database User Name dialog box: enter user name and password
   • Database Table Owner dialog box: enter table owner and password
   • Index Table Space Name dialog box:
     • Index 4K tablespace (DB2)
     • 16K/32K tableSpace (DB2)
     • Index tablespace (Oracle)
10. Click Next on these dialog boxes.

    The Repository Name dialog box appears.

11. Enter the repository name you wish to synchronize.

    NOTE:  The default is Siebel Repository.

12. Click Next.

    The Configuration Parameter Review dialog box appears. It lists all the parameters you have chosen.

    NOTE:  Passwords are in asterisks.

13. Click Finish.

    The runnow dialog box asks you to verify your choices.

14. You can either run the ddlsync process now or later. If you choose OK, the Upgrade Wizard is launched. If you choose Cancel, you can run the process later by typing siebupg.exe/m master_ddlsync.ucf from the siebsrvr/bin directory.

    If you choose OK, the following Siebel Upgrade Wizard dialog box appears.

15. If you choose OK in the Siebel Upgrade Wizard dialog box, the ddlsync process starts. Its displays your progress by placing a check after each step is completed. If there are any errors during the process, the Upgrade Wizard stops. You can go to the siebsrvr/log and look at the log files there. Fix the problem and then relaunch the Upgrade Wizard through siebupg.exe/m master_ddlsync.ucf.

    NOTE:  You must verify that there is no driver_ddlsync directory under siebsrvr/upgrade before you launch the Database Server Configuration Utility. This directory keeps a record of where you are in the ddlsync process for restarting. If you have already run ddlsync, you need to delete this directory before running ddlsync again, or you will receive an error message.

To migrate the schema under UNIX

1. Source environment variables from $SIEBEL_ROOT.

   SIEBEL_ROOT should be the path of your Siebel installation directory.

   LANGUAGE should be set to the language in which the Configuration Wizard prompts appear; for example, enu for U.S. English.

   If either of these values is incorrect or empty, reset them using one of the following commands, as appropriate to the shell you use:

   setenv LANGUAGE New Value

   or

   export LANGUAGE|SIEBEL_ROOT=New Value

2. Depending on your shell, enter:

   Korn shell

   export SIEBEL_LOG_EVENTS trace3

   C shell

   setenv SIEBEL_LOG_EVENTS trace3

   NOTE:  Setting trace to 3, creates an appropriate level of detail in the log file for this activity.

3. Navigate to $SIEBEL_ROOT /bin and enter:

   dbsrvr_config.ksh

   This launches the Database Server Configuration Wizard.

4. Review the values of the following environment variables and confirm whether or not the settings are correct by entering either Y or N.

   NOTE:  If either the SIEBEL_ROOT or LANGUAGE value is not set or is incorrect, you must correct them before proceeding.

5. In the Siebel Server Directory dialog box, either accept the default value or choose the Browse button to select a directory, and then click Next.

   The Siebel Database Server Directory dialog box appears.

6. Either accept the default value or choose the Browse button to select a directory, and then click Next.

   The Siebel Database Operation screen appears.

7. Choose Run Database Utilities (5).

   The Database Utility Selection screen appears.

8. Choose Synchronize Schema Definition.

   The RDBMS Platform screen appears.

9. Choose your db platform.

   NOTE:  The default is DB2 UDB.

10. The next screens are described as follows:
    • Database Encoding: enter whether or not the database is Unicode or Non-Unicode.
    • ODBC Datasource Name
    • Database User Name: enter user name and password
    • Database Table Owner: enter table owner and password
    • Index Table Space Name:
      • Index 4K tablespace (DB2)
      • 16K/32K tablespace (DB2)
      • Index tablespace (Oracle)
11. Press Enter on these screens (leave the parameters blank).

    The Repository Name screen appears.

12. Enter the repository name you wish to synchronize, or press Enter to use the default (Siebel Repository).

    The Configuration Parameter Review screen appears. It lists all the parameters you have chosen.

    NOTE:  Passwords are in asterisks.

13. You can either run the ddlsync process now or later. If you enter Y, the Upgrade Wizard is launched. If you enter N, you can run the process later by typing siebupg.exe/m master_ddlsync.ucf from the siebsrvr/bin directory.
14. If you enter Y, the ddlsync process starts. It displays your progress by placing a check after each step is completed. If there are any errors during the process, the Upgrade Wizard stops. You can go to the siebsrvr/log and look at the log files there. Fix the problem and then relaunch the Upgrade Wizard through siebupg.exe/m master_ddlsync.ucf.

    NOTE:  You must verify that there is no driver_ddlsync directory under siebsrvr/upgrade before you launch the Database Server Configuration Utility. This directory keeps a record of where you are in the ddlsync process for restarting. If you have already run ddlsync, you need to delete this directory before running ddlsync again, or you will receive an error message.

Bookshelf Home | Contents | Index | Search | PDF