Siebel Database Upgrade Guide > Performing the Siebel Incremental Repository Merge >

Upgrading a Custom Database Schema

To upgrade a custom database schema, perform the following task. For information on the following:

• Parameters. See Preparing to Run the Siebel Database Configuration Wizard.
• Running the Database Configuration Wizard. See one of the following, depending on your platform:
  • Running the Siebel Database Configuration Wizard on Windows
  • Running the Siebel Database Configuration Wizard on UNIX

To upgrade a custom Siebel database schema

• Execute the Siebel Database Configuration Wizard by specifying the following parameter values:
  • Environment Type: Development
  • Upgrade Options: Upgrade Custom Database Schema (upgphys)

    Table 31 shows the different steps executed by the upgphys process. The Script or Input File column in the table lists the SQL file or input file that is executed in each step. The Description column provides a brief explanation of what the SQL file or input file does. The SQL files used for an upgrade and the contents of the SQL files vary depending on the upgrade mode and database.

    Table 31. Steps That the upgphys Process Executes

    Step	Script or Input File	Description	Solution
    Check whether the merge and conflict resolution steps are complete	verify_irm.sql	Verifies whether the merge and conflict resolution steps are complete.	If this step stops because of an error, then the conflict resolution has not been completed. For information on resolving the conflict, see Reviewing Siebel Repository Object Property Conflicts. After you resolve the conflict, restart the Siebel Upgrade Wizard, and click No when asked if you want to continue. Then start the Siebel Upgrade Wizard again from the beginning.
    Drop temporary indexes created for merge performance	drop_temp_indexes_merge.sql	Removes all the temporary indexes created to improve the merge performance.	None
    Export schema definition	None	Exports the schema definition to the file DBSRVR_ROOT/platform/schema.ddl. This file is used as an input to the production test and production environments.	None
    Sync physical and logical tables	schema.ddl	Applies the schema.ddl and synchronizes the tables.	None
    Sync physical and logical indexes	schema.ddl	Applies the schema.ddl and synchronizes the indexes.	None
    Export repository to a file	None	Exports the New Customer Repository to: $DbsrvrRoot/$DatabasePlatform/custrep.dat This file is used as an input to the production test and production environments.	None
    Import New Customer Repository as Siebel Repository	custrep.dat	Truncates the repository tables and imports the previously exported New Customer Repository as Siebel Repository.	None
    Migrate custom manifest data from XML files to the database NOTE:  This step applies only to upgrades with custom Siebel Open UI manifest files for Siebel CRM version 8.1.1.9 or 8.1.1.10, and version 8.2.2.2 or 8.2.2.3.	custom_manifest.xml manifest_extensions.map	This step migrates Siebel Open UI custom manifest data from XML files to the database. For more information, see About Migrating the XML Manifest Data for Siebel Open UI from Previous Releases to the New Manifest Data in the Database.	None
    Migrate query search controls of list applets into the Siebel database	SrchCntrlMigration.jar	This step migrates query search controls of list applets from files into the Siebel database.	None
    Verify repository after upgrade	dbchck dictutl mlovupgd SeedConflict.jar	This step is optional in upgphys and is executed if the option Verify Repository After Upgrade is selected during database configuration. This verification can also be done after completing upgphys by selecting the Verify Repository After Upgrade option in the Database Configuration Wizard. The following are the verification steps executed: dbchck: Provides a report of the schema differences between the physical database and the repository definition. Unacceptable errors can occur if data types are mismatched. Acceptable errors occur if a schema object (such as a table or an index) is intentionally external to the repository. dictutl: Verifies that all dock objects and rule definitions are correct. mlovupgd: Validates the repository for data inconsistencies. Errors are logged into the log file and upgrade wizard continues with the next steps. SeedConflict: Generates the seed conflict report in HTML format. The report contains details of all the records with unique constraint violations.	None
    Upgrade history	store_history.sql	Stores the upgrade history in the S_INST_UPG_HIST table.	None