Upgrading a Custom Database Schema

To upgrade a custom database schema, perform the following tasks:

• Execute the Siebel Database Configuration Wizard by specifying the following parameter values:

  Parameter	Value
  Environment Type	Development
  Upgrade Options	Upgrade Custom Database Schema (upgphys)

  For more information about parameters, see Preparing to Run the Siebel Database Configuration Wizard.

  For more information about 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

• Before running upgphys, Full Publish must be executed. For more information about Full Publish, see Generating the Runtime Repository Data.

Note: Before you upgrade a custom database schema using the upgphys process, it is strongly recommended to back up the entire database. If this upgrade operation fails, then you can restore the database to its preupgrade state, and rerun the upgrade operation.

The following table 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.

Step	Script or Input File	Description	Solution
1. 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. Oracle recommends verifying if the Full Publish logs were successful. For more information about Full Publish, see Using Siebel Tools. Caution: Full Publish logs must be verified before running upgphys.
2. Drop temporary indexes created for merge performance	drop_temp_indexes_merge.sql	Removes all the temporary indexes created to improve the merge performance.	None
3. 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 test and production environments.	None
4. Sync physical and logical tables	schema.ddl	Applies the schema.ddl and synchronizes the tables.	None
5. Sync physical and logical indexes	schema.ddl	Applies the schema.ddl and synchronizes the indexes.	None
6. 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. This step also exports the entire New Customer Repository to: $DbsrvrRoot/$DatabasePlatform/custrep.dat	None
7. Encryption Upgrade - Physical	EncryptionUpgrade.jar,	This step updates the physical layer data for columns which are encrypted with the RC2 algorithm. This updates the data to AES algorithm.	None.
8. Encryption Upgrade	EncryptionUpgrade.exe	Updates the physical layer data for columns which are encrypted with the RC2 algorithm. This updates the data to the AES algorithm.	None
9. Enable Workspace	EnableWorkspace.exe	Enables the Workspace on the New Customer Repository for repository content.	None
10. Export repository to a file	None	Exports the New Customer Repository to: $DbsrvrRoot/$DatabasePlatform/custrep.dat This step exports the Design Time Repository (DR) to the custrep_dev.dat file and Runtime Repository (RR) to the custrep.dat file. The custrep.dat file contains only the required repository data and is used as an input to the test and production environments.	None
11. Import New Customer Repository as Siebel Repository	custrep_dev.dat	Truncates the repository tables and imports the previously exported New Customer Repository as Siebel Repository. This step imports the Design Time Repository (DR) from the custrep_dev.dat file.	None
12. Enable Workspace	EnableWorkspace.exe	Enables the Workspace on the New Customer Repository for Seed data (List of Values).	None
13. 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 Siebel Open UI XML Manifest Data from Previous Release to New Manifest Data in the Database.	None
14. Create list import package for Siebel Marketing	mktg_listimp_pkg_spec.sql mktg_listimp_pkg_body.sql	(Oracle Database only) This step creates a package to support the Siebel Marketing list import functionality for Oracle Database 12c. For more information, see Siebel Marketing Installation and Administration Guide.	None
15. Verify repository after upgrade	dbchck dictutl mlovupgd SeedConflict.jar	The repository is optionally verified after you complete the upgphys process. This step is executed if you selected the option Verify Repository After Upgrade in the Database Configuration Wizard. For more information, see Verifying the Repository After Upgrade.	None
16. Upgrade history	store_history.sql	Stores the upgrade history in the S_INST_UPG_HIST table.	None