About Database Updates for Siebel CRM

Tasks related to the Siebel database vary, according to your installation case, corresponding to the roadmap topics identified in the following paragraphs.

About the PostInstallDBSetup Utility

The PostInstallDBSetup utility (also called Post Installation Database Update) runs whenever you run the Siebel CRM installer to update the installed Siebel CRM enterprise components. Where applicable, you run PostInstallDBSetup on every Siebel database (that is, both development and runtime repository environments). PostInstallDBSetup was first provided in Siebel CRM 20.3.

PostInstallDBSetup runs several processes to ensure that the customer database schema, manifest, and seed data is up to date for the current monthly update release. Some other utilities that were formerly required for customers to run are now included in the functionality of PostInstallDBSetup.

As noted, PostInstallDBSetup applies to update installations. It does not apply to installation cases where you are installing a new Siebel database or running Incremental Repository Merge.

The Siebel CRM installer screen for collecting database details for PostInstallDBSetup includes a menu with the following options, as appropriate for your use case:

  • Execute. Collects the database details you provide and executes PostInstallDBSetup. Use this option in a typical update installation case. You must provide valid values to be passed to PostInstallDBSetup. If PostInstallDBSetup does not complete correctly or if you provide invalid values, then the utility exits. Where applicable, you must then run PostInstallDBSetup manually. Your Siebel CRM applications will not be in a supported state until PostInstallDBSetup has successfully been run after installation.

  • Defer-Generate DDL files only. Collects the database details you provide and generates a SQL file containing Data Definition Language scripts for running PostInstallDBSetup manually later. The installer does not run PostInstallDBSetup. Use this option in any installation in which you plan to run PostInstallDBSetup manually after completing the installation. Your Siebel CRM applications will not be in a supported state until PostInstallDBSetup has successfully been run after installation.

  • Skip. The installer does not run PostInstallDBSetup and any data you specify is ignored. Use this option in a deployment where you previously updated an installation for the same version in another location and ran PostInstallDBSetup. Also use this option in any other installation case in which PostInstallDBSetup is not used.

For more information about running PostInstallDBSetup manually, see Siebel Database Upgrade Guide.

About the RepositoryUpgrade Utility

Optionally, after installing Siebel CRM as an update for an existing deployment of Siebel CRM 17.x or later and allowing PostInstallDBSetup to run, you can run the RepositoryUpgrade utility manually on the development database to install new features since Siebel CRM 17.0 that require repository updates. This task does not apply in any other installation cases or if you do not require any of these new features. For more information about running this utility and about the new features that require repository updates, see Siebel Database Upgrade Guide and Siebel CRM Update Guide and Release Notes on My Oracle Support for your Siebel CRM release.

Related Topics

Installation-Related Changes in Siebel CRM

About Installing the Siebel Database

About Siebel CRM Releases

About Installing in Upgrade Environments

Related Books

Siebel Database Upgrade Guide

Siebel CRM Update Guide and Release Notes on My Oracle Support