Implementing Siebel Business Applications on DB2 UDB for z/OS > Installing the Siebel Database on the DB2 Host >

Reviewing the Log Files For Errors

This task is a step in Roadmap for Installing the Siebel Database.

Review the Siebel database installation and configuration log files to verify that the process you ran completed correctly, and to identify errors that must be resolved. The log files might include errors that are expected and benign. You must compare any error messages found in the log files to the sample error messages listed in the errors file, and correct any non-benign errors. For additional information about the log files, see About the Siebel Log Files.

To manually review the log files for unacceptable errors

1. Print the errors file. The errors file lists the benign and expected errors you might find in the log files; you can ignore these errors. The errors file is located in the installation subdirectory:

   Windows: DBSRVR_ROOT\DB2390\errors.rtf or errors.htm

   UNIX: DBSRVR_ROOT/DB2390/errors.txt

2. Sort the log files in the following directory by date.

   Windows: SIEBSRVR_ROOT\LOG\process\output

   UNIX: SIEBSRVR_ROOT/LOG/process/output

3. Open each log file, starting with the earliest, and search for errors. Starting with the earliest log file can shorten your research time.

   Log files are identified by the .log extension. Errors are either tagged with the word error or enclosed in square brackets [...].

4. For each error found, compare the error description against the list of acceptable errors documented in the errors file.

   Identify errors as follows:

   • If you find the error in the errors file, errors of that type are acceptable and no action is required. Continue to review the errors found in the log file.
   • If a log file is not listed in the errors file, there are no acceptable error messages for that log file.
   • If you find an error that is not listed in the errors file, it is unacceptable. You must correct the condition that caused the error before you run the Siebel Upgrade Wizard again.
5. Repeat Step 4 for each log file.

For help with determining the cause of an error, create a service request (SR) on OracleMetaLink 3.

When reviewing error messages, be aware that error numbers can change after the installation of a new driver version. Compare the error descriptions to find out which are acceptable errors for the z/OS platform.

CAUTION:  Although you are unlikely to encounter errors other than those listed in the errors file (see Step 1), it is critical that you review the error messages. Certain errors, such as a failure to create indexes, can result in performance problems or anomalous behavior in Siebel Business Applications.

About Identifying Errors Returned By Applications

The process log files produced by the Siebel Upgrade Wizard (upgwiz.log on Windows and srvrupgwiz.log on UNIX) do not contain information on errors returned by applications. Review the end of the log file for details about the latest failure. If the step that failed was not a native SQL step (which would be listed in the log file), then it occurred as part of an external utility for which you need to review a corresponding log file, identified by the /L parameter.

To find additional operation-specific log files, open upgwiz.log or srvrupgwiz.log using a text editor and search for a ".log" string or a "/L" string. The log file shows the names of log files produced during the installation operation; for example, if the configuration of the Siebel Database fails, the upgwiz.log file contains the following information:

GenericLog GenericError 1 2006-02-28 15:51:24 (err=1) was returned by application (C:\sba80\siebsrvr\bin\ddlimp.exe ...)

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

In an example such as the previous one, the ddlimp.log file contains a detailed error message:

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