Development Environment Upgrades

For a development environment upgrade, you run the utility twice, once in each of the following modes:

1. upgrep. This mode makes the following changes:

   • Removes 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.

     Note: Indexes that have been previously deactivated will be recreated during the upgrep phase. Check to determine whether these indexes are required following the development upgrade. If they are not, then they might be deactivated again. To deactivate indexes, contact your Oracle sales representative for Oracle Advanced Customer Services to request assistance from Oracle’s Application Expert Services.

   • Imports seed data.

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

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

   • Updates primary children foreign key references.

   • Performs miscellaneous file actions.

2. upgphys. This mode makes the following changes:

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

   • Deduplicates intersection tables.

   • Exports repository object definitions to a file, custrep.dat.

   • Exports the logical schema definition to a set of *ddl files.

     These files are used as input to the test environment and production environment upgrades.

   • Renames the New Customer Repository to Siebel Repository.

   • Updates the schema version in S_APP_VER.