Bookshelf Home | Contents | Index | PDF | ![]() ![]() |
Siebel Installation Guide for Microsoft Windows > Verifying and Troubleshooting Your Installation > Verifying Installation for the Siebel DatabaseAfter 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:
Related TopicsReviewing the Installation Log Files for the Siebel DatabaseInstalling Siebel database components on the RDBMS creates several log files within the 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 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 IBM DB2. For IBM DB2, the following log files are also generated when you create tables, indexes, and seed data: ddl_ctl.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 Verifying System Preferences and Settings for the Database Code PageAfter 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.
To verify system preferences and settings for the database code page
|
![]() ![]() |
Siebel Installation Guide for Microsoft Windows | Copyright © 2017, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |