Bookshelf Home | Contents | Index | PDF     

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:

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.

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
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.
  1. Drop temporary indexes created for merge performance

drop_temp_indexes_merge.sql

Removes all the temporary indexes created to improve the merge performance.

None
  1. 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
  1. Sync physical and logical tables

schema.ddl

Applies the schema.ddl and synchronizes the tables.

None
  1. Sync physical and logical indexes

schema.ddl

Applies the schema.ddl and synchronizes the indexes.

None
  1. 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
  1. 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
  1. 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
  1. 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
  1. Migrate SWT from files into the Siebel database

SWTMigration.jar

This step migrates Siebel Web template data from files into the Siebel database.

For more information, see About Migrating Siebel Web Template Data.

None
  1. 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
  1. 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
  1. Upgrade history

store_history.sql

Stores the upgrade history in the S_INST_UPG_HIST table.

None
      
Siebel Database Upgrade Guide Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Legal Notices.