Bookshelf v7.5: Reviewing the Log Files for Repository Import on Database Server on DB2

Siebel Server Installation Guide for Microsoft Windows > Installing the Siebel Database Server for DB2 UDB > Configuring the Database Server on DB2 >

Reviewing the Log Files for Repository Import on Database Server on DB2

The repository import process creates a number of log files, such as UpgWiz.log and UpgWiz_01.log (which increments to additional logs) within the SIEBEL_ROOT\siebsrvr\LOG subdirectory, which you must review for any errors. Further log files are created when the upgrade wizard encounters a problem and you attempt a retry.

NOTE: UpgWiz.log is the most recently created log file; UpgWiz_01 is the next most recent, and so on.

When you import a repository with a new language, it creates the following special log files:

update_ver.log
seeduver1.log
imprep_lang.log
restore_ver.log

Acceptable Errors

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.rtf file, which is located in the database server platform subdirectory, for example, db2udb. (If a log file is not listed in the errors.rtf 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.rtf file.

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

If you find errors not listed in the errors.rtf file, correct the condition that caused the errors, and rerun the Upgrade Wizard.

Do not review error numbers alone, since 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 eBusiness Applications.

Troubleshooting Siebel Repository Import for Database Server on DB2

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 tablespace pages and cannot allocate new data pages.

DB2 errors regarding the settings for DB2 configuration parameters such as APP_CTL_HEAP_SZ. These must be reset, in most cases, to higher values, since Siebel Systems' guidelines suggest only minimum values.

The above errors should appear in the log files produced by the repository import process.