Siebel Installation Guide for UNIX: Servers, Mobile Web Clients, Tools > Installing the Siebel Database Server > Configuring the Siebel Database Server >

Reviewing the Log Files for the DB Server Installation

The Siebel Database Server component installation creates several log files within the $SIEBEL_ROOT/log subdirectory. You must review the files in this subdirectory for any errors.

For example, log files created may be named srvrupgwiz1.log (the most recently created), srvrupgwiz1_01.log, srvrupgwiz1_02.log, and so.

NOTE:  For information about reviewing log files using the logparse utility, see the Upgrade Guide.

Some other files generated for selected supported RDBMS are listed below.

DB2 UDB. For DB2 UDB, the following log files are also generated when you create seed data, tables, and indexes:

ddl_ctl.log
dataimp_prim.log
dataimp_prim_lang.log
db2ddl.log
siebproc.log
seeddb2.log
seedver.log
seedssa.log
ddlview.log
ddlview_sia.log (for SIA)
grantstat.log
updatestats.log
loadstats.log
set_utc_on.log

Oracle. For Oracle, the following log files are also generated when you create seed data, tables, and indexes:

ddl_ctl.log
dataimp_prim.log
dataimp_prim_lang.log
ddlseq.log
ddlora.log
ddlview.log
ddlview_sia.log (for SIA)
seedssa.log
seedver.log
pkgseq.log
pkgldel.log
seedora.log
pkgvis.log
trgreset.log
ifstrg.log
ifindxstrg.log
set_utc_on.log
month_fn.log

Acceptable Errors for the DB Server Installation

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 installation subdirectory for your database platform, 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.The wizard will restart from the point where it left off.

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 eBusiness Applications.

Troubleshooting the DB Server Installation

Typically, problems during database installation result from insufficient storage space having been allocated, or from the installer having improper user privileges.

Providing a Rollback Segment on Oracle

To avoid certain types of errors after importing the repository, make sure that your database administrator provides only one large rollback segment online in your Oracle database.

Importing the Repository to a Target Database Host on Oracle

Some organizations download tar files onto one machine and, for convenience, install seed data and import the repository from this source machine to another target server where the database resides. If your organization does this, and your platform is Solaris, you must set the following UNIX environment variables for Oracle on the source machine or your repository import will fail:

NLS_LANGUAGE_NLS_TERRITORY.NLS_CHARACTERSET

where:

NLS_LANGUAGE = The language in which your Oracle database runs; for example, CANADIAN FRENCH

NLS_TERRITORY = The territory or region that applies to your language; for example, CANADA

NLS_CHARACTERSET = The character set (also called a code page) that applies to your platform and locale; for example, WE8MSWIN1252 (Western European on Sun Solaris)

To obtain the correct values for these variables, do one of the following:

• Query the v$nlsparameters table.
• Ask your Oracle administrator.

CAUTION:  The source node from which you install and execute must house a Siebel Server.