Siebel Installation Guide for UNIX > Configuring the Siebel Database > Importing a Siebel Repository into the Siebel Database >

Reviewing the Log Files for Repository Import for the Siebel Database

This topic is part of Importing a Siebel Repository into the Siebel Database.

The repository import process creates several log files within the $SIEBEL_ROOT/log subdirectory. Review the files in this subdirectory for any errors.

For more information, see Reviewing the Log Files for Siebel Database Installation.

Acceptable Errors for Repository Import for the Siebel Database

The log files may 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 database server platform subdirectory, 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 not listed in the errors.txt file, correct the condition that caused the errors, and rerun the Upgrade Wizard. Do not review only the error numbers, because these may have changed following installation of a new driver version. Instead, compare the actual error descriptions to find out which are acceptable errors for this platform.

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

Troubleshooting Siebel Repository Import for the Siebel Database

Typical problems that may occur at this stage consist of the following:

• Importing a repository with the same name as an existing repository.
• Database runs out of table space pages and cannot allocate new data pages which can be resolved by increasing the table space sizes.
• (DB2 UDB only) Errors regarding the settings for DB2 configuration parameters, such as APP_CTL_HEAP_SZ. These must be reset, in most cases, to higher values, because Oracle guidelines suggest only minimum values.

The preceding errors may appear in the log files produced by the repository import process.