Database Planning Guidelines

Here are important guidelines to follow when planning the upgrade of your database:

1. Analyze the impact of the upgrade on table customizations that you have made. Determine whether preupgrade data migration is required. Determine what postupgrade schema changes are required.

2. Consider database layout in your planning. Plan to tune the database and database server for the upgrade, because settings and parameters for upgrade differ from those required for Online Transaction Processing (OLTP).

3. If you are migrating multiple languages from a prior version, then plan extra time (one to two weeks) for the repository merge process. The expected merge time might increase with the number of languages in the repository. You also might need to plan for additional installation-related tasks.

4. If your locale specific language values have changed over time, then you must make changes in the upglocale.language_code file to trigger correct data migrations. For example, in a previous German language release, the German value Einzelperson mapped to the ENU value of Individual. In the new release Individuell and not Einzelperson maps to the ENU value Individual. Prior to running the upgrade utility, review the upglocale.language_code files from your present release to that of the upgrade release, to validate, and verify your language strings and to make any necessary changes. Upglocale.language_code files are located at SIEBEL_ROOT/dbsrvr/language_code folder in the new release’s installation directory.

5. For IBM DB2, consider increasing the size of your tablespaces before going live. Make sure that your custom tablespaces are large enough for upgraded tables. See Analyzing IBM DB2 Custom Tablespace Requirements for a Siebel Upgrade.