5Installing the Siebel Database on the RDBMS

Installing the Siebel Database on the RDBMS

This chapter describes running the Database Configuration Wizard to install the Siebel database and related tasks. This chapter is written for administrators who run the Database Configuration Wizard and for database administrators (DBAs) who perform related tasks on the relational database management system (RDBMS). This chapter includes the following topics:

Note: If your database is IBM DB2 for z/OS, then see Implementing Siebel Business Applications on DB2 for z/OS instead of this chapter. See also the relevant information in Planning RDBMS Installation and Configuration.

About Database Updates for Siebel CRM 20.x Update

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

After performing a new installation of Siebel CRM 17.0 plus Siebel CRM 20.x Update, you use the Database Configuration Wizard task to install a new Siebel database, as described in this chapter. This database contains schema changes, Siebel Repository content, and seed data for Siebel CRM functionality through the current release. The PostInstallDBSetup utility does not have to run this case. The postinstallation task mentioned later in this topic does not apply. See also Roadmap for Installing Siebel CRM for a New Deployment.
After performing a migration installation of Siebel CRM 17.0 plus Siebel CRM 20.x Update, you run Incremental Repository Merge (IRM) to apply the latest database updates. The PostInstallDBSetup utility does not have to run this case. The postinstallation task mentioned later in this topic does not apply. See also Roadmap for Installing Siebel CRM in a Migration Installation Case (Existing Installation of Siebel CRM 16.x or Earlier).
After performing a new installation of Siebel CRM 17.0 plus Siebel CRM 20.x Update in a full upgrade installation case, you perform a full database upgrade to apply the latest database updates. The PostInstallDBSetup utility does not have to run this case. The postinstallation task mentioned later in this topic does not apply. See also Roadmap for Installing Siebel CRM in an Upgrade Case (Existing Database).
When you install Siebel CRM 20.x Update for an existing deployment of Siebel CRM 17.x or later, the installer runs the Post Install DB Setup (PostInstallDBSetup) utility, as described later in this topic. This utility must run for each subsequent update release you install. You can also optionally run the RepositoryUpgrade utility manually, as described later in this topic. See also Roadmap for Installing Siebel CRM 20.x Update for an Existing Installation of Siebel CRM 17.x or Later.

About the PostInstallDBSetup Utility

As of Siebel CRM 20.3 Update, the PostInstallDBSetup utility runs whenever you run the Siebel CRM 20.x Update installer to update the installed Siebel Server and the Database Configuration Utilities. Where applicable, you run PostInstallDBSetup on every Siebel database (that is, both development and runtime repository environments).

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. The utility might run certain other utilities: as of Siebel CRM 20.8 Update, this guide no longer calls out utilities that are run by PostInstallDBSetup. Some utilities that were formerly required for customers to run are now included in the functionality of PostInstallDBSetup.

You must provide valid values 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, as described in Siebel Database Upgrade Guide.

In the new installation or migration installation cases, or if you want to run the utility manually later, then (as of Siebel CRM 20.7 Update) you can check a box to skip running the utility as part of installation. (After installing a new Siebel database or running Incremental Repository Merge at the latest Siebel CRM 20.x Update release level, you do not need to run PostInstallDBSetup manually.)

About the RepositoryUpgrade Utility

When PostInstallDBSetup is executed, it runs the RepositoryUpgrade utility automatically to apply required framework changes. Optionally, after installing Siebel CRM 20.x Update for an existing deployment of Siebel CRM 17.x or later and allowing PostInstallDBSetup to run, you can also 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 already ran the utility for a prior release. For more information about running this utility and about the new features that require repository updates, see Siebel CRM Update Guide and Release Notes on My Oracle Support for your Siebel CRM 20.x Update release.

Related Books

Siebel Database Upgrade Guide

Siebel CRM Update Guide and Release Notes on My Oracle Support

About Installing the Siebel Database

Caution: In an upgrade environment, or in another environment where you have an existing Siebel database, you generally do not perform any of the tasks mentioned in this chapter. For more information, see About Installing in Upgrade Environments and Roadmap for Installing Siebel CRM in an Upgrade Case (Existing Database).

The Siebel database on the RDBMS stores the data used by Siebel CRM. Siebel Server components (particularly Application Object Managers supporting Siebel Web Clients), Siebel Tools, and Siebel Developer Web Clients connect directly to the Siebel database and make changes in real time.

Siebel Mobile Web Clients download a subset of the server data to use locally. The mobile user periodically synchronizes the local database with the Siebel database through the Siebel Remote components on the Siebel Server. The synchronization process updates both the local database and the Siebel database.

The Siebel Database Configuration Utilities (also called the Siebel Database Server) refers to a set of files that you install on a Siebel Server computer, using the Siebel Enterprise Server installer. These files are accessed when you run the Database Configuration Wizard and the Siebel Upgrade Wizard in order to install and configure the Siebel database on the RDBMS.

Note: In the Database Configuration Wizard, the main task that you perform for a new deployment is called installing the Siebel database. Additional tasks described in this chapter are sometimes referred to by using the general phrase configuring the Siebel database.

For instructions on installing Database Configuration Utilities, Siebel Server, and other Siebel Enterprise Server modules, see Installing Siebel CRM Server Modules.

Note: This chapter assumes that you have already created the database instance. It also assumes that you have already installed the Database Configuration Utilities on the same computer as a Siebel Server, and in the same top-level installation directory. You install the Database Configuration Utilities only once, typically with the first Siebel Server that you install.

For a new deployment, you must install a Siebel Server and the Database Configuration Utilities on the same computer as the Siebel Gateway. For more information, see Requirements for Siebel Gateway Authentication. For information about the tasks that you must perform in the RDBMS before you install the Database Configuration Utilities, see Configuring the RDBMS.

The Database Configuration Utilities installed software has no runtime role in managing database operations for users running Siebel CRM. Some of the tasks that you can perform with the Database Configuration Wizard are for upgrades only, and are described in Siebel Database Upgrade Guide.

Note: After performing a new database installation, you must activate the license keys, as described in Activating License Keys. Then run the Siebel Management Console as described in this book.

This topic includes the following information:

Related Books

Siebel Database Upgrade Guide

About Installing a Database

When you choose Install Database from the Siebel Database Operation screen in the Database Configuration Wizard, the utility performs several tasks within the database instance that you have already created.

The Database Configuration Wizard is available on the computer on which you installed the Siebel Server and the Database Configuration Utilities.

Before installing the Siebel database, review all of the applicable requirements. The Install Database operation does the following:

Creates the Siebel schema. Tables and indexes are created in their respective specified tablespaces.
Inserts Siebel seed data specific to your database. Seed data is inserted for the primary language only. This task also installs views, packages, and procedures for your database.
Imports the Siebel Repository. The Repository is imported for the primary language only.
Sets system preferences.

This topic is part of About Installing the Siebel Database.

About Adding a Language to an Existing Database

Adding a language to an existing Siebel database installs seed data to support that language. After the database is initially installed with the primary language, each additional language must be installed separately using an add-language operation.

To add a new language to previously installed Siebel CRM, you must have installed its Siebel language pack on the installed Siebel Server, using the Siebel Enterprise Server installer. See also Installing and Deploying Siebel CRM with Multiple Languages.

After adding a language, you must import the Siebel Repository for this language. For more information, see Importing a Siebel Repository Manually into the Siebel Database.

After you have added a language to the Siebel database, your seed data is multilingual. You must enable the multilingual list of values (MLOV) capability for Siebel CRM, and you must enable individual LOVs associated with the language. For more information, see:

Configuring Siebel Business Applications
Siebel Global Deployment Guide
For Siebel CRM language support, Unicode support, and legacy code page support, see 1513102.1 (Article ID) on My Oracle Support.

This topic is part of About Installing the Siebel Database.

Creating Table Owner and Administrator Accounts

Create the table owner and administrator accounts according to the guidelines provided for each database platform identified in this topic. These accounts are created by updating and running the grantusr.sql script. Record all of the relevant data, such as the table owner name and password, in the worksheets provided in Siebel Deployment Planning Worksheet.

Note: For each applicable database platform, if you are planning to use Siebel Marketing, then also grant DROP TABLE, DROP INDEX, CREATE TABLE, and CREATE INDEX rights at the database level within the OLTP schema to the table owner or the database user ID used for Siebel Marketing. For more information, see Siebel Marketing Installation and Administration Guide.

Caution: It is strongly recommended not to change the name of the Siebel administrator account, SADMIN. This account must be created so that you can log in to Siebel applications as the Siebel administrator. For information about changing the password for this account, see Siebel Security Guide. The password for the SADMIN account must not exceed 18 characters.

Before you execute grantusr.sql, confirm that this script will create all of the users that must be created before you install the Siebel database. Optionally, you can also modify the script to define the anonymous users that you will specify when configuring the Siebel Application Interface. For more information, see Requirements for Configuring Anonymous Users for the Siebel Application Interface.

This topic contains the following information:

Running the grantusr.sql Script on an Oracle Database

Before you install the Siebel database, your DBA must review, modify, and execute the grantusr.sql script.

The administrator executes grantusr.sql against the database instance to create the Siebel table owner account, the Siebel administrator account (default: SADMIN), the LDAPUSER account, and the role sse_role and to grant them appropriate privileges. The script also creates the default tablespace. The grantusr.sql script is located in the DBSRVR_ROOT/oracle subdirectory.

After executing grantusr.sql, the DBA must manually create all of the additional tablespaces (for data or indexes) that you require in your Siebel database. To do this, use commands similar to the existing ALTER USER command defined in grantusr.sql for creating the default tablespace. Use commands similar to the following:

ALTER USER TABLE_OWNER quota unlimited on tablespace_name;

where:

TABLE_OWNER is the name of the Siebel table owner account.
tablespace_name is the name that you are using for each particular tablespace. If it is necessary, then the quota value can be adjusted to an appropriate value for each tablespace.

The grantusr.sql script performs the following functions:

Creates the role sse_role and grants CREATE SESSION privilege to this role.
Creates the Siebel table owner account and grants other appropriate privileges to this account.
Creates the accounts SADMIN (the Siebel administrator) and LDAPUSER and grants the role sse_role to them.
Creates the default tablespace.

Passwords are prompted for by the script, rather than defined within the script.

The length and allowable characters for the user name and password depend on the rules of your underlying RDBMS platform. For more information, see Oracle Database documentation.

This topic is part of Creating Table Owner and Administrator Accounts.

To run the grantusr.sql script on an Oracle Database

Execute the grantusr.sql script from SQL*Plus, using an account with DBA privileges, and using the following command:
```
@$SIEBEL_ROOT/dbsrvr/oracle/grantusr.sql
```
Note: You must specify the full path to the grantusr.sql file.
Enter the tablespace name listed in Siebel Deployment Planning Worksheet.

Running the grantusr.sql Script on IBM DB2

Before you install the Siebel database, your DBA must manually create the Siebel table owner account, the Siebel administrator account (default: SADMIN), and the sse_role group. The DBA must then add the Siebel administrator account to the sse_role group at the operating system level.

You can add users to the sse_role group and permit them to use administrative commands to start, stop or otherwise administer the Siebel Server or components. However, you must change the permissions on the directory to enable write access, using the following command:

chmod -R 775 $SIEBEL_ROOT

Note: On Oracle Solaris, the sse_role group cannot be created using admintool, due to the use of an underscore in the name. Instead, use the command groupadd sse_role to create the sse_role group. Ignore the warning: groupadd: sse_role name should be all lower case or numeric.

Before you install the Siebel database, execute the grantusr.sql script against your database server to grant the appropriate privileges to these users. The grantusr.sql script is located in the DBSRVR_ROOT/db2udb subdirectory.

Your DBA must review and execute this script, which performs the following functions:

Grants the appropriate permissions to the Siebel table owner account that will own all of the database objects for your Siebel deployment.
Creates a role (sse_role) with CREATE SESSION privileges.

You cannot create the LDAPUSER account by running grantusr.sql. This account must belong to the sse_role group and must be created by the DBA or the UNIX network administrator, as appropriate. For more information about authentication using the LDAP security adapter, see Siebel Security Guide.

This topic is part of Creating Table Owner and Administrator Accounts.

To run the grantusr.sql script on IBM DB2

Execute the grantusr.sql script, using an account with DBA privileges.
The usual DB2 System Administration account is called db2inst1 for this procedure.
Enter the following commands:
```
db2 connect to DB2database_alias user instance_owner_username using password
db2 -vf $SIEBEL_ROOT/dbsrvr/db2udb/grantusr.sql
```
where:
- DB2database_alias is the DB2 alias that you use
- instance_owner_username is the login ID of the database instance owner
- password is the password for the database instance owner
- $SIEBEL_ROOT is the full path to the Siebel root directory
The script prompts you for the default tablespace in which your Siebel objects are to be created.
Enter the tablespace name that you recorded in the copy that you made of Siebel Deployment Planning Worksheet.

The length and allowable characters of the account names and passwords depend on the rules of your underlying RDBMS platform. For more information, see IBM DB2 documentation.

Before you install the Siebel database, see Installing the Stored Procedures and User-Defined Functions on IBM DB2.

Installing the Stored Procedures and User-Defined Functions on IBM DB2

On IBM DB2, after installing the Database Configuration Utilities, you must copy stored procedures and user-defined functions (UDFs) from the Database Configuration Utilities installation to the DB2 database server.

Any method that transfers the necessary files to the correct location on the database server is acceptable. To copy the stored procedure code, complete the procedure that follows. Use the steps appropriate to the operating systems for the Database Configuration Utilities and the RDBMS. For information about how to perform basic IBM DB2 tasks, see the Quick Beginnings guide from IBM.

To copy and install the stored procedures and user-defined functions

Log on to the Siebel Server computer on which you installed the Database Configuration Utilities.
Navigate to the following subdirectory in the Database Configuration Utilities installation directory:
```
DBSRVR_ROOT/db2udb/siebproc/DBSRVR_OS 
```
where:
- DBSRVR_ROOT is the Database Configuration Utilities module subdirectory of your Siebel CRM installation directory ($SIEBEL_ROOT/dbsrvr).
- DBSRVR_OS is the string corresponding to the operating system your database server (RDBMS) runs on, such as AIX, HPUX, LINUX, or SOLARIS.
Copy the file siebproc to the function subdirectory within the DB2 instance directory on the RDBMS computer where DB2 is installed.
For example, on AIX, this location might be $INST_HOME/sqllib/function.
Permissions for siebproc must be -rw-r---- (read-write for the owner, read for the group, and neither read nor write for all others). The owner of the file must be the instance owner, and the group must be the group to which the instance owner belongs.
For a 64-bit DB2 database, do one of the following instead:
- For a 64-bit DB2 database running on Itanium architecture, copy the file siebproc64 to the SQLLIB/FUNCTION directory, and rename it to siebproc.
- For a 64-bit DB2 database running on X64 architecture, copy the file siebprocEMT64 to the SQLLIB/FUNCTION directory, and rename it to siebproc.
Proceed to Installing the Siebel Database.

Starting the Siebel Database Configuration Wizard

Use the following procedure to start the Siebel Database Configuration Wizard on UNIX. You start the wizard from the command line.

As part of the following procedure, you must enter the necessary command to source one of the following environment setup files, as appropriate, to configure or validate the environment.

dbenv.csh or dbenv.sh. Before you run the Database Configuration Wizard, you must source either dbenv.csh (for C shell) or dbenv.sh (for Bourne or Korn shell). Before you can source one of these files, you must create them by running the script CreateDbSrvrEnvScript. These environment files are created in the $SIEBSRVR_ROOT installation directory. For more information, see Installing the Siebel Database.

To start the Siebel Database Configuration Wizard at the command line

Open a shell window.
Source an environment setup file, as appropriate:
Before you run the Siebel Database Configuration Wizard, source either dbenv.csh (for C shell) or dbenv.sh (for Bourne or Korn shell). For more information, see Installing the Siebel Database.
Navigate to the config subdirectory within your $SIEBEL_ROOT directory. For Siebel CRM 17.0:
Navigate to a directory like the following, on the Siebel Server computer: /Siebel/config.
To start the Database Configuration Wizard to configure in GUI mode, go to the next step. Use the same commands if you are generating a response file for unattended configuration. To perform an unattended configuration, go to Step 5.
Enter a command similar to the following to start the Database Configuration Wizard:
```
install_path/config/config -mode dbsrvr
```
In this command, install_path is the installation path for the installed Siebel CRM module, such as in the following example command:
```
/Siebel/config/config -mode dbsrvr
```
Additional command-line options that you can use are:
- -skipValidation. Specifies that no validation should be performed of user input. You can use this flag when saving a response file for an unattended configuration, or when previewing wizard screens.
- -verbose. Specifies that more details should be included in configuration log files.
  
  Note: Using the -verbose option is recommended in order to log information about certain issues that might affect your configuration tasks. For example, various 32-bit libraries are required for successful configuration. When you use the -verbose option to generate a finer level of granularity in log messages, the Database Configuration Wizard might log, for example, that a particular required 32-bit library is missing. For more information about required libraries, see the Certifications tab on My Oracle Support.
For an unattended configuration, go to the next step. Otherwise, go to Step 6.
For an unattended configuration, you save and later execute a response file for configuring the Siebel database. Do one of the following:
- If you are generating a response file, then go to Step 6 and continue the configuration process. In the summary screen, choose the option to save a configuration file, then cancel the Database Configuration Wizard. Then, to perform the unattended configuration of the same module, restart the wizard as described in the next paragraph.
- If you are executing a response file that you saved in a previous configuration session, then start the wizard using the -responseFile option, specifying the name of the response file to execute. Use a command similar to the following:
```
install_path/config/config -mode dbsrvr -responseFile file_name
```
  where:
  - install_path is the installation path for the installed Siebel CRM module (see example in Step 4)
  - file_name is the name of the response file that you are executing
Note: For a command like this, the response file would have been saved in a previous configuration session. In unattended mode, wizard screens that would normally display are not displayed, because the applicable data is already stored in the response file.
If you are generating a response file, then go to the next step. If you are executing a response file, then the Database Configuration Wizard runs in unattended mode and completes configuration.
Respond to each prompt in the Database Configuration Wizard, then click Next to go to the next screen or to complete the configuration.
See Installing the Siebel Database.

Note: You can click Cancel to exit the Database Configuration Wizard before you complete the configuration.
After you specify or confirm all of your selections, the summary screen appears.
In the summary screen, do one of the following:
- Click Next again to complete the configuration. Go to the next step.
- Optionally, save a response file in this screen, to use in an unattended configuration, then click Cancel to exit the Database Configuration Wizard without completing configuration.
After configuration is complete, click Exit to exit the Database Configuration Wizard.
To help you to verify that the configuration completed successfully, the log file is referenced at the end of the configuration task.

Installing the Siebel Database

This topic describes how to install the Siebel database on the RDBMS. This task is a step in Roadmap for Installing Siebel CRM for a New Deployment. (Also perform all of the other applicable tasks in this chapter.)

Note: As of Siebel CRM 17.0, installing a new database creates an ODBC data source name that allows you to use database authentication when you run Siebel Management Console, as described in Configuring Siebel CRM Server Modules.

To install Siebel database components

Review About Installing the Siebel Database and Starting the Siebel Database Configuration Wizard.
Before you run the Database Configuration Wizard for the first time, run the CreateDbSrvrEnvScript script to generate the environment setup files dbenv.csh and dbenv.sh.
CreateDbSrvrEnvScript is located in the directory $SIEBSRVR_ROOT/install_script/install. Run CreateDbSrvrEnvScript from this location by using the following command:
```
./CreateDbSrvrEnvScript Siebel_Root_Parent_Directory LANG DB_Platform
```
where:
- Siebel_Root_Parent_Directory is the top-level Siebel Enterprise Server installation directory.
- LANG is the three-letter code for the primary language for the Siebel database that you will install; for example, ITA for Italian.
- DB_Platform is Oracle, Db2Udb, or Db2.390.
For example:
```
./CreateDbSrvrEnvScript /siebel ITA Oracle
```
The dbenv.csh and dbenv.sh environment setup files are created in the Siebel Server installation directory.
Open a shell window.
Navigate to the $SIEBSRVR_ROOT directory and source the environment file by using one of the following commands, depending on the type of shell that you use. Perform this step each time that you run the Database Configuration Wizard. You must have created this file first, by using the script CreateDbSrvrEnvScript, as described in Step 2.
C shell
```
source dbenv.csh
```
Bourne or Korn shell
```
. ./dbenv.sh
```
Note: Make sure that there is a space between the initial period and ./dbenv.sh.
In this path, $SIEBSRVR_ROOT is the location of the Siebel Server root directory. For example, the directory might be /export/home/Siebel/siebsrvr.
Verify whether the values for SIEBEL_ROOT and LANGUAGE are correctly set or are empty by entering:
```
env
```
If the variables are incorrect or missing, then reset them using one of the following commands, as appropriate to the shell that you use.

For example, the SIEBEL_ROOT value might resemble /export/home/Siebel/siebsrvr, while the value for LANGUAGE might be ENU, FRA, JPN, CHS, or another code representing the language in which you are running the Database Configuration Wizard.
C shell
```
setenv SIEBEL_ROOT New_Value 
```
```
setenv LANGUAGE New_Value 
```
Bourne or Korn shell
```
export SIEBEL_ROOT=New_Value 
```
```
export LANGUAGE=New_Value 
```
Navigate to the config subdirectory of the $SIEBEL_ROOT directory. For example, navigate to a location like /Siebel/config.
Start the Database Configuration Wizard, as described in Starting the Siebel Database Configuration Wizard. Enter a command similar to the following:
```
install_path/config/config -mode dbsrvr
```
In this path, install_path is the installation path for the installed Siebel Enterprise Server software.
The Database Configuration Wizard validates the existence of the$SIEBEL_ROOT directory.
Specify the following, and click Next:
Siebel Server Directory. Specify the existing installation location of Siebel Server. This location is also referred to as the $SIEBSRVR_ROOT directory. For example, this directory might be /export/home/Siebel/siebsrvr.
Siebel Database Server Directory. Specify the existing installation location of Siebel Database Configuration Utilities. This location is also referred to as the DBSRVR_ROOT directory. For example, this directory might be /export/home/Siebel/dbsrvr.
On the RDBMS Platform screen, select one of the following platforms, and click Next:
IBM DB2 UDB for Linux UNIX Windows
IBM DB2 UDB for z/OS
Oracle Database Enterprise Edition
On the Siebel Database Operation screen, select Install Database from the list, and click Next.
On the Select Installation Operation screen, select Install Siebel Database to install a new Siebel database, or select Add a Language to an Existing Siebel Database, and then click Next.
The Install Siebel Database option creates the Siebel schema and inserts seed data and Siebel Repository data for the primary language at the end of the Configuration Wizard session.
If you instead selected Add a Language to an Existing Siebel Database, then go to Step 19. You must have included the language when you installed the Siebel Server and Database Configuration Utilities. For more information, see Installing and Deploying Siebel CRM with Multiple Languages.
On the next screen, confirm that you want to install a new Siebel database, or indicate that you already have a Siebel database.
On the Siebel User/Role Creation screen, confirm that you (or a database administrator) have already run the grantusr.sql script to set up table owner and administrator accounts.

Note: The table owner and administrator accounts must be in place or you will not be able to complete the installation of the tables, indexes, and seed data in the Siebel database. For more information, see Creating Table Owner and Administrator Accounts.
- If you already ran grantusr.sql, then select the corresponding option, and click Next.
- If you did not already run grantusr.sql, then exit the Database Configuration Wizard, and run the script now. When the script has finished executing, restart the Database Configuration Wizard.
(Oracle Database only) Specify the following, and click Next:
Siebel Database Table Owner. Type the name of the Siebel database table owner or the account that will own the Siebel objects.
Oracle SQLNet Connect String. Provide the name of the Oracle schema qualifier or table owner name and the SQLNet connect string for Oracle Database.
(IBM DB2 or IBM DB2 for z/OS only) Specify the following, and click Next:
DB2 Instance Path. Provide the IBM DB2 client installation path, such as /home/sblqa1, where sblqa1 contains the sqllib subdirectory.
(IBM DB2 only) Specify the following, and click Next:
Siebel Database Table Owner. Type the name of the Siebel database table owner or the account that will own the Siebel objects.
IBM DB2 Database Alias. Provide the name of the IBM DB2 UDB schema qualifier or table owner name and the database alias for IBM DB2.
(IBM DB2 for z/OS only) Specify the following, and click Next:
Siebel Database Table Owner. Type the name of the Siebel database table owner or the account that will own the Siebel objects.
IBM DB2 Database Alias. Provide the name of the IBM DB2 UDB schema qualifier or table owner name and the database alias for IBM DB2.
Current IBM DB2 SQL ID / Group Name. Provide the name of the IBM DB2 UDB SQL ID or group name.
On the Database Encoding screen, identify the appropriate database encoding method, and click Next:
UNICODE Database
Non-UNICODE Database

Caution: Choose the correct option for your database to prevent installing the wrong data types. The database cannot create Unicode data types on a non-Unicode page setting, so check this setting carefully before choosing this option.

Note: Before you select languages in the next two steps, review the information about code pages in Planning RDBMS Installation and Configuration.
On the Base Language screen, specify which language serves as the primary language (base language) for the Siebel database.

Note: If you installed a single Siebel language pack on the Siebel Server where you also installed Database Configuration Utilities, then that language is assumed for a new database installation. Neither the Base Language nor the Language Selection screen appears. Go to Step 21.
The languages listed in this screen are those for which you previously installed Siebel language packs on the Siebel Server where you also installed Database Configuration Utilities. Do one of the following, and click Next:
- If you are installing a new Siebel database, then specify the language that will be the primary language. Seed data and Siebel Repository data will be installed for this language. Go to Step 21. (The Language Selection screen does not appear in this case.)
- If you are adding a language to an existing Siebel database, then specify the language that you already installed as the primary language. Go to the next step to specify the additional language to install, from the Language Selection screen.
(Add Language case only) On the Language Selection screen, select the language that you want to install in the Siebel database, for an Add Language operation.

Note: For a new database install case, this screen does not appear. Go to the next step.
The languages listed in this screen are those for which you previously installed Siebel language packs on the Siebel Server where you also installed Database Configuration Utilities.
Select the language that you want to add. Seed data will be installed for this language. You must import the Siebel Repository for this language separately (using the Add Language to an Existing Repository task), as described in Importing a Siebel Repository Manually into the Siebel Database.
Some of the remaining screens do not apply for an add-language operation. Go to the next applicable step.
Specify the following, and click Next:
Database User Name. Type the user name of the Siebel administrator; for example, sadmin.
Database Password. Type the password for the Siebel administrator.
Database Password (confirm). Retype the password to confirm it.
Specify the following, and click Next:
Database Table Owner. Type the name of the Siebel database table owner or the account that will own the Siebel objects.
Database Table Owner Password. Type the password for the Siebel database table owner.
Database Table Owner Password (confirm). Retype the password to confirm it.
(Oracle Database only) On the Register External Oracle DB ODBC Driver screen, specify this option if you will use the Siebel Connector for Oracle Applications to exchange data with your back office system, and your back office system stores data in an Oracle Database.
(IBM DB2 only) Specify the following, and click Next:
Index Table Space Name. Type the name for your index tablespace; for example, SBL_INDX. (Tablespace names must not contain spaces; underscores are allowed.)
4K Table Space Name. Type the name for your 4-KB tablespace; for example, TBS_4K. (Tablespace names must not contain spaces; underscores are allowed.)
16K Table Space Name. Type the name for your 16-KB tablespace; for example, TBS_16K. (Tablespace names must not contain spaces; underscores are allowed.)
32K Table Space Name. Type the name for your 32-KB tablespace; for example, TBS_32K. (Tablespace names must not contain spaces; underscores are allowed.)
(Oracle Database only) Specify the following, and click Next:
Index Table Space Name. Type the name for your index tablespace; for example, INDEX01. (Tablespace names must not contain spaces; underscores are allowed.)
Table Space Name. Type the name for your tablespace; for example, DATA01. (Tablespace names must not contain spaces; underscores are allowed.)
(Oracle Database only) On the Siebel License Key Option screen, specify that you will provide the license key data later, and click Next.
The license keys for Siebel CRM base applications must be activated using the License Key Activation utility, as described in Activating License Keys.
(Oracle Database only) On the Oracle Parallel Index screen, specify the statement describing your database environment, and click Next:
- Does not use the Oracle Parallel Indexing option
- Uses the Oracle Parallel Indexing option
If you have a single-CPU environment, then choose the first option. If you have a multiple-CPU environment, then choose the first or second option, depending on whether you are running your Oracle Database with parallel indexing on.
Specify the following, and click Next:
Security Group ID / Grantee. Type the name for your security group. Specify SSE_ROLE.
On the Log Output Directory screen, accept the default log directory or enter a new directory name, and click Next.
By default, logging occurs in the $SIEBSRVR_ROOT/log/operation/output directory. In this path, operation corresponds to the operation that you are performing, such as install for an Install Database operation or install_lang for an Add Language operation.
Click Help to view the following message, which asks if you are ready to apply configuration changes to the Siebel database now, using the Siebel Upgrade Wizard, or will do so later:
```
Configuration is complete: your output will be saved under $SiebelRoot/siebsrvr/
bin/master_<process>.ucf. Would you like to deploy the process you configured to 
the database now or later?
```
Note: Check the Siebel CRM Update Guide and Release Notes on My Oracle Support for the current release. If this document describes any tasks that you must perform to modify the generated SQL files, then modify the generated SQL files as necessary before you execute the SQL in the Siebel Upgrade Wizard.
Choose one of the following, and click Next:
- Yes apply configuration changes now. Choose this option if you want the generated SQL files to be executed in the Siebel Upgrade Wizard.
- No I will apply configuration changes later. Choose this option if you do not want the generated SQL files to be executed in the Siebel Upgrade Wizard. In this case, you must run the Upgrade Wizard manually at a later time in order to execute the generated SQL files.
If you choose to apply configuration changes later, then the command line to apply the configuration later is:
```
$SIEBEL_ROOT/siebsrvr/bin/srvrupgwiz /m master_operation.ucf
```
For the purposes of this procedure, operation is either install or install_lang.
Review the values that you entered on the previous screens in the Database Configuration Wizard:
- If you have to change any values, then click Back and Next to access the screens on which to change entries, and then to return to this screen.
- Alternatively, you can click Cancel to cancel the Database Configuration Wizard session, then restart the wizard and enter different values.
- When you have verified your input, click Next. Doing so generates SQL files that you will then apply to the database. When all of the SQL files have been generated, a message appears, stating The configuration changes were applied successfully. Click OK.
If you chose No in Step 30, then the Siebel Upgrade Wizard does not appear. You must run it manually, after reviewing the generated SQL files.
If you chose Yes in Step 30, then the Siebel Upgrade Wizard appears.

Note: When you run the Siebel Upgrade Wizard, if a program or system error occurs, then you can rerun the wizard, starting at the point at which the wizard failed. For more information, see Siebel Database Upgrade Guide.
When the Siebel Upgrade Wizard finishes running, the Siebel Upgrade Wizard Complete screen appears. You have now finished installing the Siebel database components.
After the Siebel Upgrade Wizard has finished running, click Exit to exit the Database Configuration Wizard.

Activating License Keys

License keys for Siebel CRM base applications that are provided in seed data in the Siebel database, or that were provided in prior releases, are inactive by default. License keys entered by customers for previous releases are unchanged. The License Key Activation utility is provided for activating or deactivating the license keys that you require. You run this utility to add any additional license keys after installing a new Siebel database, running Incremental Repository Merge (for migration installations), or completing a full database upgrade.

You can find license key information for Siebel CRM at Oracle’s license codes site. For the Siebel license keys, see

http://licensecodes.oracle.com/siebel.html

The License Key Activation utility is supported on all operating systems and databases for Siebel CRM.

This task is a step in Roadmap for Installing Siebel CRM for a New Deployment.

To start the License Key Activation utility

On the computer where you installed Siebel Server, navigate to the following location:
```
SIEBSRVR_ROOT/bin
```
Run the following program, according to your operating system:
- Windows: licensekeymodule.bat
- UNIX: licensekeymodule.sh
Enter valid data for the following fields:
- Siebel Server Location. The installation path for this Siebel Server.
- ODBC DSN. The ODBC data source for the Siebel database.
- Table Owner. The table owner for the Siebel database.
- Username. The user name for logging into the Siebel database.
- Password. The password for this user.
- DB Platform. The RDBMS platform, either ORACLE, DB2UDB, or DB2390.
- Log folder. The folder in which the log file licenseKeys.log is created. This log file shows database connection information for troubleshooting purposes, and lists all of the license keys that were activated or deactivated in each session.
Click Login.
The license key activation screen appears, which lists Siebel CRM license keys.
For each license key module whose activation status you want to change, click the Active Flag check box to activate or deactivate this license key.
To apply your selections to the Siebel database, click Apply. Or, to reset any changes you have made in this screen, or since you last clicked Apply, click Reset.

Caution: After you have clicked Apply, the Reset button does not reset activation settings to their original state. However, you can change the activation status and click Apply again.
To exit the utility, click the X in the top right corner.

Related Books

Siebel Database Upgrade Guide

Setting Up Your Environment to Support Global Time Zone

Global deployments typically span multiple time zones, making it difficult to manage time-sensitive information that must be exchanged among customers and employees working around the world. You can use the Global Time Zone feature to monitor the transfer of tasks between sites in different time zones.

The Global Time Zone feature converts and stores date and time data, using the Universal Time Coordinated (UTC) standard. UTC is equivalent to Greenwich Mean Time, but without daylight savings time.

Caution: Oracle does not support new Siebel CRM deployments that do not use UTC. For existing deployments, if you do not want to deploy with UTC or are not ready to do so, then you must review the documentation for this feature, which is primarily located in Siebel Global Deployment Guide.

Make sure that the time is synchronized on all of your computers by using a common NNTP server for time synchronization.

If you intend to operate your deployment with the Global Time Zone feature enabled, then you can optionally set the operating system of your database servers to UTC time, or its equivalent.

For restrictions on using the Global Time Zone feature on IBM DB2 for z/OS, see Implementing Siebel Business Applications on DB2 for z/OS.

Note: The Global Time Zone parameter (Universal Time Coordinated system preference) is enabled (set to TRUE) by default. If you do not want to enable the Global Time Zone feature, then you must reset this system preference to FALSE by navigating to the Administration - Application screen, and then the System Preferences view.

Related Books

Siebel Global Deployment Guide

Implementing Siebel Business Applications on DB2 for z/OS

Populating the Siebel File System

After you complete installing Database Configuration Utilities and installing the Siebel database, you must populate the Siebel File System. Specific files needed to use the Siebel File System, such as correspondence templates and Siebel Marketing files, are provided with the Database Configuration Utilities software. A subdirectory called files is created when you install the Database Configuration Utilities.

The Siebel administrator must populate the att directory in the File System with these files after installing the Database Configuration Utilities, and before running the Siebel Web Client.

For detailed information about creating the Siebel File System, including setting the necessary permissions, see Creating the Siebel File System.

To populate the Siebel File System directory

Copy the appropriate files from the files subdirectory of the Database Configuration Utilities software to the att subdirectory of the Siebel File System.
Verify that the files are in the correct location.

Importing a Siebel Repository Manually into the Siebel Database

Installing the Siebel database, as described in Installing the Siebel Database, automatically imports the Siebel Repository for the primary language (only). For each nonprimary language in a multilingual deployment, a separate step to manually import the Siebel Repository is needed.

The content in this topic is provided for customers with multilingual deployments or who have some reason to manually import a Siebel Repository.

You can import the Siebel Repository using the Database Configuration Wizard. This task populates the Siebel Repository tables in the Siebel database with new object definitions. You import the Siebel Repository separately for each nonprimary language in a multilingual deployment. This task does not apply to the Siebel Repository for the primary language.

Regardless of how many Siebel applications that you are using (for example, Siebel Call Center, Siebel Sales, Siebel Service, and Siebel Marketing), you load the Siebel Repository tables only once for each language.

Note: When you import data into the Siebel Repository tables, a commit is performed once for each table into which Siebel Repository data is imported. Alternatively, you can adjust the commit frequency by including the command-line option /z size_of_array when the repimexp utility is invoked. The transaction will not be committed until all of the data in the array has been inserted. (However, if the table contains fewer records than the specified array size would allow, then the transaction is committed after all of the data has been inserted.)

Some steps in the procedure in this topic pertain to the task of adding a language to an existing Siebel Repository, also using the Database Configuration Wizard. By adding a new language to a Siebel Repository, you populate rows of localized user interface strings for Siebel Repository objects, which allows Siebel CRM to display the UI in the new language.

In order to add a new language to an existing Siebel Repository, you must have installed its Siebel language pack on the Siebel Server using the Siebel Enterprise Server installer. Also, you must have added the language to the Siebel database. For more information, see Installing the Siebel Database and Installing and Deploying Siebel CRM with Multiple Languages.

To import the Siebel Repository

Start the Database Configuration Wizard, as described in Installing the Siebel Database. Respond to the wizard prompts in the same way that you did for that procedure, up to the Siebel Database Operation screen.
On the Siebel Database Operation screen, select Import/Export Repository, and click Next.
On the Select Repository Operation screen, choose one of the following options:
Import Repository. This option imports the Siebel Repository for the first time with a primary (base) language. Click Next and go to the next step. This task does not apply if you are importing Siebel Repository data into an existing Siebel Repository for any nonprimary language.
Add Language to an Existing Repository. This option adds a new language to your existing Siebel Repository (imports Siebel Repository data for that language). Click Next and go to Importing a Siebel Repository Manually into the Siebel Database.
Export Repository. This option exports the Siebel Repository data into a platform-independent file that can be sent to Oracle Global Customer Support for analysis, if needed. This task is not described in this book. For more information, see Using Siebel Tools and other documentation.
On the Import Selection screen, specify that you want to import the standard Siebel Repository, and click Next.
On the Language Selection screen, specify the language. For an import Siebel Repository operation, this is the primary language (base language), the first language installed in Installing the Siebel Database. For an Add Language operation, this is the language that you want to add to the Siebel Repository.
The languages listed in this screen are those for which you previously installed Siebel language packs on the Siebel Server.
On the ODBC Data Source Name screen, indicate the name for the ODBC data source, such as sieb17_DSN, and click Next.
For more information about the ODBC data source, see Planning RDBMS Installation and Configuration.
On the Database User Name screen, indicate the following about your database, and click Next:
Database User Name. Type the user name of the Siebel administrator, for example, sadmin for Oracle Database and IBM DB2.
Database Password. Type the password for the Siebel administrator.
Database Password (confirm). Retype the password to confirm it.
On the Database Table Owner screen, indicate the following about your database, and click Next:
Database Table Owner. The Siebel database table owner, or the account that will own the Siebel objects.
Database Table Owner Password. Type the Siebel database table owner password.
Database Table Owner Password (confirm). Retype the password to confirm it.
On the Import Repository Name screen, type the following values, and click Next:
Import Repository Name. Accept the default name (Siebel Repository) or type another valid name.
Repository File Name/Localized Repository File Name. If you are importing your Siebel Repository for the first time, then this field is named Repository File Name. If you are adding a language to an existing Siebel Repository, then this field is named Localized Repository File Name. Accept the default installation path and file name for this Siebel Repository, or type another valid installation path.
For Oracle Database, go to the next step. For IBM DB2, go to Step 11.
(Oracle Database only) In the Oracle Parallel Index screen, specify the appropriate environment for your installation, and click Next:
- I am not running with Parallel Indexing On
- I am running with Parallel Indexing On
If you have a single-CPU environment, then choose the first option. If you have a multiple-CPU environment, then choose the first or second option, depending on whether you are running your Oracle Database with parallel indexing on.
In the Log Output Directory screen, accept the default log directory, or enter a new directory name, and click OK.
By default, logging occurs in the $SIEBSRVR_ROOT/log/operation/output directory. In this path, operation corresponds to the operation that you are performing, such as imprep for Import Repository or imprep_lang for Add Language to an Existing Repository.
The Configuration Parameter Review screen appears.
Review the configuration values that you entered on the previous Configuration Wizard screens:
- If you want to change any values, then click Previous or Next to access the screens on which to change entries, and then to return to this screen.
- When you have verified the configuration values, click Finish. A message box appears with the prompt:
```
To apply the configuration now, press OK.
To apply the configuration later, press Cancel.
The command line to apply the configuration later is
$SIEBEL_ROOT/siebsrvr/bin/srvrupgwiz /m master_operation.ucf
```
  For the purposes of this procedure, operation is either imprep or imprep_lang.
The Siebel Upgrade Wizard appears, displaying the items to be executed or imported.

Note: If a program or system error occurs and you have to rerun the Siebel Upgrade Wizard, then you can do so starting at the point at which the wizard failed. For more information, see Siebel Database Upgrade Guide.
To begin, click OK.
A window appears, displaying information about Siebel Upgrade Wizard activities to import the Siebel Repository. The Upgrade Wizard displays a message when the operation is complete.

Related Books

Using Siebel Tools

Siebel Database Upgrade Guide

5Installing the Siebel Database on the RDBMS

Installing the Siebel Database on the RDBMS

About Database Updates for Siebel CRM 20.x Update

About the PostInstallDBSetup Utility

About the RepositoryUpgrade Utility

Related Topics

Related Books

About Installing the Siebel Database

Related Topics

Related Books

About Installing a Database

About Adding a Language to an Existing Database

Creating Table Owner and Administrator Accounts

Running the grantusr.sql Script on an Oracle Database

To run the grantusr.sql script on an Oracle Database

Running the grantusr.sql Script on IBM DB2

To run the grantusr.sql script on IBM DB2

Installing the Stored Procedures and User-Defined Functions on IBM DB2

To copy and install the stored procedures and user-defined functions

Starting the Siebel Database Configuration Wizard

To start the Siebel Database Configuration Wizard at the command line

Installing the Siebel Database

To install Siebel database components

Related Topics

Activating License Keys

To start the License Key Activation utility

Related Books

Setting Up Your Environment to Support Global Time Zone

Related Books

Populating the Siebel File System

To populate the Siebel File System directory

Importing a Siebel Repository Manually into the Siebel Database

To import the Siebel Repository

Related Topics

Related Books