Implementing Siebel eBusiness Applications on DB2 UDB for OS/390 and z/OS > Siebel Repository Import, Export, and Postinstallation Tasks >

Reviewing the Log Files for Repository Import


The repository import process creates a number of log files within the subdirectory siebsrvr\log ($SIEBEL_ROOT/log under UNIX) that you must review for any errors. The log file names for subsequent processes include a numeric suffix that increments for additional logs files; for example, UpgWiz.log, UpgWiz_01.log, UpgWiz_02.log (under Windows) or srvrupgwiz.log, srvrupgwiz1.log, srvrupgwiz2.log (under UNIX). Further log files are created when the Upgrade Wizard encounters a problem and the user attempts a retry.

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

For more details on logs, refer to the discussion under Reviewing the Log Files for Windows and Reviewing the Log Files for UNIX.

Acceptable Errors

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.rtf file that is located in the db2390 subdirectory of the dbsrvr installation directory. (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. If you cannot determine the cause of the errors on your own, contact Siebel Technical Support.

Do not review error numbers alone, because error numbers might change after 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, might result in performance problems or anomalous behavior in Siebel eBusiness Applications.


 Implementing Siebel eBusiness Applications on DB2 UDB for OS/390 and z/OS 
 Published: 18 April 2003