Perform Upgrade Tasks (Development Environment)

This phase merges your customizations into the new release. This phase also upgrades the development environment database and includes these tasks:

• Prepare application data. These tasks prepare test data for migration.

• Upgrade database (upgrep). Run the Database Configuration Wizard in upgrep mode, selecting the zSeries Staging of Files for Upgrade option. This generates the files required to build the staging database and generate the upgrade files required to perform the in-place upgrade of the database.

• Perform the in-place upgrade of the database. During this phase, a basic upgrade of the Siebel database schema is performed and repositories are loaded to prepare for the repository merge.

The upgrep mode makes the following changes:

• Drops interface tables and database triggers

• Populates columns that must change from NULL to NOT NULL

• Creates new tables. Merges existing tables.

• Prepares for index creation. Verifies that there are no unique key violations.

• Creates indexes

• Imports seed data

• Imports the Prior Siebel Repository, the New Siebel Repository, and the New Customer Repository

• Makes modifications to repository objects to prepare for the repository merge

• Updates primary children foreign key references

• Performs miscellaneous file actions

• Merge repository. You use Siebel Tools to merge your existing repository with the repository in the new release. During the repository merge, objects from the Prior Siebel Repository, the Prior Customer Repository, and the New Siebel Repository are compared to identify the total set of object differences. The process also determines how conflicts between repository changes are resolved as they are merged into the New Customer Repository.

• Run postmerge utilities. You use Siebel Tools to run a set of utilities that examine the merged repository. The utilities analyze your customizations to applets and views, and apply changes to them as required to conform to the user interface in the new release.

• Upgrade database (upgphys). You run the Database Configuration Wizard in upgphys mode. It further upgrades the Siebel database with changes resulting from the repository merge and completes the database upgrade.

  The Database Configuration Wizard also generates the customer repository definition file and logical schema definition file that are used as input to the production test environment and production upgrades.

  Specifically, this mode performs the following tasks:

  • Synchronizes the Siebel database schema to the logical schema definition in the merged repository.

    Note: During the synchronization process, custom columns in the Siebel Schema that are not in the Siebel Repository are not removed but custom indexes in the Siebel Schema that are not in the Siebel Repository are removed.

  • Exports repository object definitions to a file, custrep.dat, and exports the logical schema definition to a file, schema.ddl

    These two files are used as input to the production upgrades.

  • Renames the New Customer Repository to Siebel Repository

  • Updates the schema version in S_APP_VER