Importing the Repository and Performing Postinstallation Tasks

This chapter describes how to import the Siebel Repository and describes other postinstallation procedures that you perform to complete the Siebel database installation and configuration process.This chapter contains the following topics:

Process of Completing the Siebel Database Implementation

After completing the Siebel Schema installation, there are still a number of tasks you must perform before your Siebel Business Applications implementation is completed. These tasks are listed as follows:

Importing the Siebel Repository.
Configure the Siebel Server.
For information on this task, see Siebel Installation Guide for the operating system you are using.
Perform the relevant postinstallation tasks (some are mandatory and some optional):

Importing the Siebel Repository

This task is a step in Process of Completing the Siebel Database Implementation.

Importing the Siebel Repository is the final stage in the Siebel Schema installation process. When you import the Siebel Repository, you populate all the repository tables in the Siebel database with Innovation Pack 2017 application objects.

Regardless of how many Siebel Business Applications you are using (for example, Siebel Sales, Siebel Service, Siebel Marketing), you load data into the repository tables only once for each installation.

You can also export the Siebel Repository into a platform-independent file that can be sent to Global Customer Support for analysis in case of problems that cannot be diagnosed by telephone or email. For help with problems relating to your Siebel application, create a service request (SR) on My Oracle Support.

To import the Siebel Repository

Launch the Database Configuration Wizard and follow the steps in Performing a Standard Installation until the Siebel Database Operation screen is displayed (Performing a Standard Installation).
Select the Import/Export Repository option, and click Next.
The following options are available on the Select Repository Operation screen:
- Import Repository. Used to import the Siebel Repository for the first time with a base language.
- Add language to an existing Repository. If you have already imported your Siebel Repository and its base language, select this option to add another language to the repository. For information, see Importing a New Language to Your Repository.
- Export Repository. Exports the Siebel Repository into a platform-independent file that can be sent to Global Customer Support for analysis, if needed.
  
  Note: You can also use the repository export option to replicate repositories.
Select the Import Repository option, and click Next.
On the Import Selection screen, indicate whether you want to import a standard Innovation Pack 2017 or a customized repository, by clicking the appropriate radio button.

Note: Select Import Custom Repository when you are importing a multilingual repository from a test or development environment. This imports all languages to your target repository.
To continue, click Next.
On the Language Selection screen, select the base language in which you want to run the database.
On the ODBC Data Source Name screen, enter the name of the ODBC data source, or enter the database alias you prefer to use for the data source. If you specify a database alias, the alias must have been previously registered within DB2 Connect.
The Siebel Server installation process automatically creates the data source, using the syntax: EnterpriseName DSN. To continue, click Next.
In the Siebel Database User Name screen, enter the database user name, then click Next.
The Database User Name is the ID used to log into the Siebel database. This user ID must be part of the security group with authorization to set the current SQLID to the schema name.
In the Siebel Database Password screen, enter the password associated with the database user name, then click Next to continue.
On the Siebel Schema Qualifier screen, enter the ID that identifies the Siebel Schema owner, and click Next.
The Import Repository Name screen appears.
On the Import Repository Name screen, enter the designated name of the repository you want to import, for example, Siebel Repository, then click Next.
Enter the file and path name of the repository file you want to import, then click Next.
On the Log Output Directory screen, specify where you want the import repository log files to be generated.
By default, the files are created in SIEBSRVR_ROOT\log\imprep (Windows) or SIEBSRVR_ROOT/log/imprep (UNIX).
Save the configuration information you have entered and launch the Siebel Upgrade wizard as described in the following topics:
- Running the Database Configuration Wizard Under Windows
- Running the Database Configuration Wizard Under UNIX
Click OK to begin the repository import.
A window appears, displaying information about the repository import activities.
If the repository import is successful, the Upgrade Wizard displays a message that the repository has been imported. Otherwise, review the log files. For more details on logs, see About the Siebel Log Files and Rerunning the Installation.

Note: If the Siebel Repository import fails midway through the process, you must clean up the data from the failed import by using Siebel Tools to delete the repository.

Granting Table Privileges

This task is a step in the Process of Completing the Siebel Database Implementation.

To grant the Siebel group ID additional, required privileges on EIM tables, the database administrator must edit and execute the grantstat.sql file. This procedure is described in this topic.

To edit and run the grantstat.sql script

Navigate to the grantstat.sql script which is located in the DBSRVR_ROOT\db2390 directory (Windows) or the DBSRVR_ROOT/db2390 directory (UNIX).
Edit grantstat.sql by replacing &1 with the Siebel Schema Qualifier ID that you recorded in Deployment Planning Worksheet.
Execute the grantstat.sql script, using the method you prefer.

Validating the Siebel Schema

This task is a step in the Process of Completing the Siebel Database Implementation.

After you install the Siebel database and import the repository, you must compare the physical database schema with the repository to make sure that there are no inconsistencies between them. Use the Siebel Server utility, dbchck.exe (Windows) or dbchck (UNIX), located in the bin subdirectory of your Siebel Server installation directory, to make this comparison.

You can use the dbchck utility to validate data relationships, including foreign keys and the list of values. You can also use this utility when you have made changes to the extensibility of your Siebel database.

The most popular mode in which to run dbchck is using the option /dict /all. This option provides a comprehensive log file that lists all of the discrepancies between the logical data model defined in the repository you specify and the physical database schema in the Siebel database you run the utility against.

To validate the Siebel Schema

From the SIEBSRVR_ROOT\bin directory (Windows) or the SIEBSRVR_ROOT/bin directory (UNIX), locate dbchck.exe (Windows) or dbchck (UNIX).
(Windows only) Delete the dictionary cache file (diccache.dat) before running dbchck, and verify that there are no EIM or Siebel Remote operations running.
The dbchck utility creates a new diccache.dat file before carrying out the integrity check. By deleting the existing diccache.dat file before starting dbchck, you ensure that dbchck validates against the Siebel Repository you specify.

Note: If you stop any EIM or Siebel Remote processes, you can restart them after dbchck has run.
Source environment variables as appropriate for your platform, using either siebenv.bat (Windows) or siebenv.sh or siebenv.csh (for UNIX).
Environment variable scripts are located in the SIEBSRVR_ROOT\bin directory (Windows) or the SIEBSRVR_ROOT/bin directory (UNIX).
Source the database profile.
Run dbchck using the following syntax:
```
dbchck /u SADMIN /p password /t SIEBTO /r "Your Siebel Repository Name" /l 
dbchck.log /dict /all /s ODBC data source
```
where:
- password is the login password to the database.
- Your Siebel Repository Name is the repository you want to compare against the physical data model; in the installation, the default value is:
```
"Siebel Repository"
```
  Note: You must specify your repository name within quotation marks ("") after the repository name parameter ( /r).
- ODBC data source is the ODBC data source applicable to the repository.
- SIEBTO is the Siebel Schema Qualifier.
Note: To view all the dbchck parameters with their descriptions, use option /h.
Any discrepancies found appear on the screen. Detailed information is written to a log file in the SIEBSRVR_ROOT\bin directory (Windows) or the SIEBSRVR_ROOT/ bin directory (UNIX).

Note: The log file name is the name you specified after the log file parameter ( /l). In the previous example, the file is named dbchck.log.
Review the log file generated as a result of running this script. Any discrepancies are flagged as failures. Investigate all discrepancies.

Discrepancies in the dbchck Log

After completion of the dbchck.exe script, the dbchck.log file generated might contain discrepancies noted as failures.

Some errors noted in the dbchck.log file are not acceptable and must be addressed. An example of such an error follows:

Dictionary column FIN_PERIOD_ID not in physical schema! Dictionary different from physical schema for column dictionary: REVISED_COST numeric(22,7) null physical: REVISED_COST decimal(10,0) null

This error is caused by a mismatch in the data type definition of the column in the logical and physical schema. The definition of a column in the logical and physical schema must be synchronized; you can synchronize the logical definition with the physical schema using Siebel Tools. After the synchronization is done, run dbchck.exe again.

Note: LONG columns, defined as LONG VARCHAR columns in the Siebel Repository, are physically created as VARCHAR columns by DB2 for z/OS. The dbchck utility does not generate errors for LONG columns in these circumstances; this is expected behavior on the DB2 for z/OS platform. For additional information, see About Long Columns and Siebel Utilities.

For more information about using the dbchck utility, see the following documents on My Oracle Support:

475677.1 (Article ID). This document was formerly published as Siebel FAQ 1128.
477235.1 (Article ID). This document was formerly published as Siebel Troubleshooting Steps 20.

Populating the Siebel File System

This task is a step in the Process of Completing the Siebel Database Implementation.

Specific files required to run the Siebel File System, such as correspondence templates and Siebel Marketing files, are provided with the Database Configuration Utilities software. A directory called DBSRVR_ROOT\files (Windows) or DBSRVR_ROOT/files (UNIX) is created automatically when you install the Database Configuration Utilities.

Populate the appropriate subdirectory of the Siebel File System with these file attachments after installing the Database Configuration Utilities and the Siebel database and before running the Siebel Web Client.

To populate the Siebel File System directory

Copy the files from the DBSRVR_ROOT\files (Windows) or DBSRVR_ROOT/files (UNIX) directory to the att subdirectory of the Siebel File System.
Verify that the files are in the correct directory.

Installing License Keys

This task is a step in the Process of Completing the Siebel Database Implementation.

After you have installed the Siebel database and performed the mandatory postinstallation tasks, you must install the license keys you received with Innovation Pack 2017 to enable you to use the new release.

This topic describes how to install the Siebel license keys so that users can access the Siebel application.

To add new license keys

Start the new-release version of Siebel Tools.
Connect to the Siebel database as the Siebel Administrator.
You are prompted to enter your license key number the first time you log on to Siebel Tools.
Add your new license key information and click OK.

For additional information on installing license keys, see Siebel Installation Guide for the operating system you are using.

Installing Multilingual Seed Data

This task is a step in the Process of Completing the Siebel Database Implementation.

If your organization deploys internationally and, therefore, requires data to be in multiple languages, you must install multilingual seed data (for example, lists of views, responsibilities, or system preferences). You install this seed data by adding new language packs to your database after you install the base language for your database. These language packs populate the List of Values (LOV) with seed data in the new language.

You must successfully install seed data in your base language before you can add seed data in other languages to your database.

Note: You cannot add secondary languages to the Siebel database for an Enterprise Server unless you have already installed the relevant language pack on the associated Siebel Server.

To install multilingual seed data

Install the appropriate Language Pack on the Siebel Server. Follow the instructions for adding a new language to an existing instance as described in Siebel Installation Guide for the operating system you are using.
When installation is completed, launch the Database Configuration Wizard by following the instructions under Performing a Standard Installation.
When the Select Installation Operation screen appears (Performing a Standard Installation), select Add a language to an existing Siebel Database, and then click Next.

Note: To add seed data in a new language to your database, you must have already imported your repository in its base language.
The Base Language screen appears and displays the languages you have installed for your Siebel database.
In the Base Language screen, specify which of the installed languages is the one in which you want to primarily run your database. (This is your base language.)
To continue, click Next.

Note: The Language Selection screen appears only if you have installed the files for multiple Siebel Language Packs. Installation of multiple Language Packs can occur either during your initial installation of Siebel Business Applications or at a later time.
In the Language Selection screen, specify the new language you are adding for this database.
To continue, click Next.
On the ODBC Data Source Name screen, enter the ODBC Data Source Name. The Siebel Server installation process automatically creates the data source, using the format EnterpriseName_DSN. Accept the default name of the ODBC data source or enter the database alias you prefer to use for the data source.

Note: Database aliases must be registered within DB2 Connect. If you define database aliases, you must add the TXNISOLATION parameter to the database alias entry in the db2cli.ini file and set it to have a value of 1. For information on setting values in the db2cli.ini file, refer to the relevant IBM documentation.
On the Siebel Database User Name screen, enter the Database User Name.
Type the ID (for example, SADMIN) used to log into the Siebel database. This user ID must be part of the security group (secondary authorization group) with authorization to set the current SQLID to the schema name.
On the Siebel Database Password screen, enter the password for the ID used to log into the Siebel database.
Retype the password to confirm it, then click Next.
On the Siebel Schema Qualifier screen, enter the character ID that identifies the Siebel Schema owner, for example, SIEBTO.

Note: This ID can be up to eight characters in length, must be in uppercase, must start with a letter, and cannot include any special characters. This value is the SQL Authorization ID stored in the CURRENT SQLID special register.
On the Security Group ID/Grantee screen, type the group ID for which schema access is being granted, for example, SSEROLE. Click Next.
For more information about the group authorization ID privileges, see Security Concepts for a DB2 for z/OS Environment.
The Repository Name screen appears. Type the name of your Siebel Repository or accept the displayed default name.
To continue, click Next.
On the Log Output Directory screen, enter the name of the directory where you want the log files to be generated, and click Next.
By default, the files are created in SIEBSRVR_ROOT\log\install_lang (Windows) or SIEBSRVR_ROOT/log/install_lang (UNIX).
Save the configuration information you have entered and launch the Siebel Upgrade wizard as described in the following topics:
- Running the Database Configuration Wizard Under Windows
- Running the Database Configuration Wizard Under UNIX
The Siebel Upgrade Wizard is launched.
To begin, click OK.
A window appears, displaying information about installation activities. A message appears when the installation is completed.
To verify that the installation was successful, review the log files as described in About the Siebel Log Files.
When you have finished adding a language to your database, you need to import the Siebel Repository for the language you have just added. For information on completing this task, see Importing a New Language to Your Repository.
After you have added a language to the Siebel database, your seed data is multilingual so you must enable the multilingual list of values (MLOV) capability within Siebel Business Applications. You must also enable individual LOVs associated with the language. For information on multilingual deployments, see Siebel Global Deployment Guide and Configuring Siebel Business Applications.

Importing a New Language to Your Repository

This task is a step in the Process of Completing the Siebel Database Implementation.

After you successfully import your Siebel Repository in its base language, you can add additional languages to the repository. By adding a new language to your repository, you populate rows of localizable information, which allows Siebel Business Applications to better operate in the new language.

Regardless of how many Siebel Business Applications you are using (such as Siebel Sales, Siebel Service, Siebel Marketing), you perform this step only once for each language you want to import.

Note: You can only add an additional language to your repository if it has already been deployed and added to your database. For further information on deploying additional languages, see Siebel Installation Guide for the operating system you are using. For information on adding an additional language to your database, see Installing Multilingual Seed Data.

To import a repository in a secondary language

After installing multilingual seed data as described in Installing Multilingual Seed Data, launch the Database Configuration Wizard.
Follow the steps in Importing the Siebel Repository to Step 3 (Select Repository Operation).
Select the Add Language to an existing Repository option and click Next.
In the Language Selection screen, select the new repository language you are adding, and click Next.
On the ODBC Data Source Name screen, enter the name of the ODBC data source, or enter the database alias you prefer to use for the data source. If you specify a database alias, the alias must have been previously registered within DB2 Connect.
The Siebel Server installation process automatically creates the data source, using the syntax EnterpriseName_DSN.
To continue, click Next.
In the Siebel Database User Name screen, enter the database user name, then click Next.
The Database User Name is the ID used to log into the Siebel database. This user ID must be part of the security group with authorization to set the current SQLID to the schema name.
In the Siebel Database Password screen, enter the password associated with the database user name. Reenter the password to confirm it, then click Next.
On the Siebel Schema Qualifier screen, enter the ID that identifies the Siebel Schema owner, for example, SIEBTO, and click Next.
On the Import Repository Name screen, enter the designated name for this Siebel Repository or accept the default.
Enter the localized Repository file name.
If you are importing a secondary language repository on top of your base-language repository, either accept the default installation path and file name for this repository or type another valid installation path.
On the Log Output Directory screen, specify where you want log files to be generated, then click Next.
By default, the files are created in SIEBSRVR_ROOT\log\imprep_lang(Windows) or SIEBSRVR_ROOT/log/imprep_lang (UNIX).
Save the configuration information you have entered and launch the Siebel Upgrade wizard as described in the following topics:
- Running the Database Configuration Wizard Under Windows
- Running the Database Configuration Wizard Under UNIX
To begin, click OK.
A window appears, displaying information about installation activities. A message appears when the installation is completed.
To verify that the installation was successful, review the log files. When you import a repository with a new language, it creates the following log files:
- imprep_prim.log
- imprep_lang.log
For further information on log files, see About the Siebel Log Files.
Click Exit to exit the Database Configuration Utility.