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 Server Configuration Wizard. See one of the following, depending on your platform:
  • Running the Siebel Database Configuration Wizard Under Windows
  • Running the Siebel Database Configuration Wizard Under 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 30 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 30. 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		Exports the schema definition to $DbsrvrRoot/$DatabasePlatform/schema.ddl file. 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		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	custom_manifest.xml manifest_extensions.map	NOTE:  This step applies only to upgrades with custom Siebel Open UI manifest files for Siebel CRM Version 8.1.1.9 and later, and Version 8.2.2.2 and later. 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 in Siebel CRM Version 8.1.1.11.	None.
    Upgrade history	store_history.sql	Stores the upgrade history in the S_INST_UPG_HIST table.	None.