Siebel Installation Guide for UNIX > Verifying and Troubleshooting Your Installation >

Troubleshooting Installation for the Siebel Database

These topics provide suggestions for troubleshooting problems that you might encounter when installing and configuring the Siebel database.

Troubleshooting Installation for the Siebel Database

Typically, problems during database installation result from insufficient storage space having been allocated, or from the installer having improper user privileges.

Acceptable Errors for Installation of the Siebel Database

The log files might include errors that are expected and benign. Compare any error messages found in the log files to the sample error messages in the errors.txt file, which is located in the installation subdirectory for your database, for example, oracle. If a log file is not listed in the errors.txt file, then there are no acceptable error messages for that log file. No further action is required if the log files contain errors listed in the errors.txt file.

NOTE:  Only one of each type of error occurring in a particular log file appears in the errors.txt file.

If you find errors that are not listed in the errors.txt file, then correct the condition that caused the errors, and rerun the Upgrade Wizard. The wizard restarts from the point where it left off.

Do not review only the error numbers because these might have changed following installation of a new driver version. Instead, compare the error descriptions to find out which are acceptable errors for this database.

CAUTION:  Although other errors are rarely encountered, this review is critical. Certain errors, such as a failure to create indexes, might result in performance problems or anomalous behavior in Siebel Business Applications.

You can view a log summary generated using the logparse utility. For more information, see Siebel Database Upgrade Guide.

Troubleshooting Siebel Repository Import for the Siebel Database

Typical problems that can occur at this stage are shown in Table 15. These errors might appear in the log files produced by the Siebel Repository import process.

Table 15. Troubleshooting Siebel Repository Import for the Siebel Database

Cannot import a Siebel Repository

Importing a Siebel Repository with the same name as an existing Siebel Repository

Choose a unique name for the new Siebel Repository.

Database runs out of tablespace pages and cannot allocate new data pages

Insufficient tablespace size

Increase the tablespace sizes.

(IBM DB2 only) Errors regarding the settings for DB2 configuration parameters, such as APP_CTL_HEAP_SZ

Values too low

Reset the DB2 configuration parameters to higher values. Guidelines for Siebel Business Applications suggest using only minimum values.

Siebel Installation Guide for UNIX Copyright © 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices.