|Bookshelf Home | Contents | Index | PDF|
In general, each customer must follow these general steps for each supported RDBMS platform described in this chapter. For more information, see your third-party vendor documentation, guidelines presented in this chapter for each RDBMS, and other applicable parts of this guide.
CAUTION: Do not perform any tasks mentioned in this chapter in an upgrade environment (or in another environment where you have an existing Siebel Database). In particular, you do not create the database instance on the RDBMS. However, after the upgrade is complete, you may need to modify database parameters for your RDBMS platform to match settings described in this chapter. For more information, see About Installing in Upgrade Environments.
For non-upgrade deployments (where there is no existing Siebel Database), after creating the database instance and installing the Siebel Business Applications software, you use scripts and utilities provided with the Database Configuration Utilities installation to create the Siebel Database—that is, to load the Siebel schema and seed data into the database instance. For details, see Configuring the Siebel Database.
In this guide, DBSRVR_ROOT refers to the installation directory of the Siebel Database Configuration Utilities. For more information, see File and Directory Naming Conventions.
NOTE: In general, it is easier to configure and administer a Siebel Database that does not share a database instance with other applications. This approach is considered a best practice. However, some customers may decide to include multiple applications in a single database instance. The implications of this choice may differ by RDBMS type: for example, the term database instance has a different meaning for an Oracle Database than it does for DB2 UDB. The shared database instance must be configured according to requirements described here.
CAUTION: Changing the Siebel schema requires changing referential integrity rules for business components and Siebel EIM interface tables, using Siebel Tools. Failure to make the appropriate changes in the Siebel schema can lead to data corruption. Changing the Siebel schema also requires changing assignment objects, dock objects (for data access or visibility), import objects, and integration objects, also using Siebel Tools. Failure to make the appropriate changes can lead to functional deficiencies in the application and, in severe cases, may prevent you from starting the application. Customers must always use Siebel Expert Services when planning to modify the standard Siebel schema.
Sample scripts provided with the Database Configuration Utilities installation can optionally be used to create the Siebel Database. These scripts are for testing purposes in small, nonproduction environments only. If you intend to use such a script, first perform the tasks above, through Step 6, but omit Step 4 and Step 5.
|Siebel Installation Guide for Microsoft Windows||Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices.|