Siebel Server Installation Guide for UNIX > Installing the Siebel Database Server for Oracle > Configuring the Siebel Database Server on Oracle >

Reviewing the Log Files for Siebel DB Server Installation on Oracle

The Siebel Database Server component installation creates a number of log files, such as srvrupgwiz.log and srvrupgwiz1.log (which increments to additional logs) within the $SIEBEL_ROOT/log subdirectory, which you must review for any errors.

When you install seed data, tables, and indexes for Oracle, it generates a number of log files.

When you install your primary(base) Language Pack, it creates a special log file with the name dataimp_prim_lang.log.

Acceptable Errors for Siebel DB Server Installation on Oracle

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 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 DB Server Installation on Oracle

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 tarfiles 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 is the language in which your Oracle database runs; for example, FRENCH CANADIAN.

NLS_TERRITORY is the territory or region that applies to your language; for example, CANADA .

NLS_CHARACTERSET is 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:

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


 Siebel Server Installation Guide for UNIX 
 Published: 24 June 2003