Siebel Installation Guide for Microsoft Windows > Verifying and Troubleshooting Your Installation >

Verifying Installation for the Siebel Database

After installing the Siebel database on the RDBMS using the Siebel Database Configuration Wizard, review the installation log files and the system preferences for the database code page. This topic has the following information:

• Reviewing the Installation Log Files for the Siebel Database
• Verifying System Preferences and Settings for the Database Code Page

Related Topics

Installing the Siebel Database

Verifying Installation for Siebel Business Applications

Troubleshooting Installation for the Siebel Database

Reviewing the Installation Log Files for the Siebel Database

Installing Siebel database components on the RDBMS 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 might be named upgwiz.log (the most recently created), upgwiz_01.log, upgwiz_02.log, and so.

NOTE:  For information about reviewing log files using the logparse utility, see Siebel Database Upgrade Guide. This utility is located in SIEBSRVR_ROOT\bin.

Some other files generated, by supported RDBMS, are listed as follows.

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

ddl_ctl.log
dataimp_prim.log
dataimp_prim_lang.log
ddlseq.log
ddlora.log
ddlview.log
ddlview_sia.log
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

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

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
grantstat.log
updatestats.log
loadstats.log
set_utc_on.log

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

helpsort.log
ddl_ctl.log
dataimp_prim.log
dataimp_prim_lang.log
pkgseq.log
seedmss.log
ddlms.log
trgreset.log
seedver.log
seedssa.log
ddlview.log
ddlview_sia.log
set_utc_on.log

Verifying System Preferences and Settings for the Database Code Page

After you complete installing Database Configuration Utilities and installing the Siebel database, you must verify system preferences and other settings for the Siebel application that indicate whether you are using Unicode, and indicate the code page that you are using.

For more information about code pages, see Planning RDBMS Installation and Configuration. For Siebel CRM language support, Unicode support, and legacy code page support, see 1513102.1 (Article ID) on My Oracle Support.

The following procedure assumes that you have already installed Siebel Tools.

• For information about installing Siebel Tools, see Installing Siebel Tools.
• For information about starting Siebel Tools, see Verifying Successful Installation of Siebel Tools.

To verify system preferences and settings for the database code page

1. Start Siebel Tools and connect to the Siebel database.
2. Navigate to Screens, System Administration, and then System Preferences.
3. Look for System Preference Name = Enterprise DB Server Code Page. Verify that the value has been set correctly, based on the value that you selected during the installation of the Siebel database components (see Installing the Siebel Database).

   NOTE:  The value of Enterprise DB Server Code Page must be in lowercase, for example, utf-8 or utf-16. An Oracle Database character set might have a different value, although the system preference value must be utf-8. The utf-16 code page is also known as UCS-2, although the system preference value must be utf-16.

   Possible values for the system preference are listed in the following table:

   Language	Database	Value
   All	Oracle Database	utf-8 (for Unicode)
   All	IBM DB2, Microsoft SQL Server	utf-16 (for Unicode)
   Japanese	Oracle Database, IBM DB2	cp932 (or equivalent)
   Western European	All	cp1252 (or equivalent)

4. Verify that the column UNICD_DATATYPS_FLG in the table S_APP_VER is set correctly. The flag value must be in uppercase.

   Possible values for UNICD_DATATYPS_FLG are listed in the following table:

   Code Page	Database	Value
   Non-Unicode code page	All	N
   Unicode	Oracle Database	8
   Unicode	IBM DB2	Y
   Unicode	Microsoft SQL Server	Y