Implementing Siebel eBusiness Applications on DB2 UDB for z/OS and OS/390 > Siebel Schema Installation on the DB2 Host > Performing a Custom Installation >

Reviewing the Log Files for UNIX


The database server component installation creates a number of log files, such as srvrupgwiz.log, srvrupgwiz1.log (which increments to additional logs) within the log subdirectory of the siebsrvr installation directory, which you must review for any errors.

When you install your base language pack, it creates a special log file with the name dataimp_prim_lang.log.

The main log file, produced by the Siebel Upgrade Wizard (Srvrupgwiz.log), does not contain errors returned by applications. Additional information about the configuration process can be found in the sw_cfg_utl.log file. Depending on the operation performed, ddl_ctl.log file reflects any errors:

To find additional operation-specific log files, open Srvrupgwiz.log, using any text editor, and search for a ".log" string.

This shows the names of log files, produced during the operation. For example, if the configuration of the Database Server fails, the Srvrupgwiz.log contains the following information:

GenericLog GenericError 1 2002-02-28 15:51:24 (err=1) was returned by application (D:/sea77/siebsrvr/bin/ddlimp.exe ...)

GenericLog GenericError 1 2002-02-28 15:51:24 Execute file action failed (err=Launching the application)

In the previous example, the ddlimp.log file contains a detailed error message:

DDLIMP-ERR-1071: Unable to build ddl statement "add col" (Open unloadtbl.jcl)

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 your 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 only 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. The wizard restarts from the point where it left off.

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 z/OS and OS/390