Siebel Enterprise Configuration Utility on 8.1.1.8 and later with DB2 may fail. (Doc ID 1539819.1)

Last updated on FEBRUARY 06, 2019

Applies to:

Symptoms

When all three conditions below are met, Siebel Enterprise Configuration Utility for "Configure a New Enterprise in a Gateway Name Server" cannot register ODBC driver successfully. It finishes with the error message "Siebel Configuration Wizard failed with error. Please see the log files for details.", but it does not provide the detailed information.

1) Server database is DB2 9.1 or 9.7. (DB2 9.5 is not supported.)
2) DB2 Client is installed on the folder that contains space, such as "C:\Program Files\IBM\SQLLIB" (This is the default location for DB2 installation.)
3) Siebel Enterprise Configuration Utility (config.bat) is launched on FP 8.1.1.8 or the later version. The same utility on FP 8.1.1.7 or prior (launched as ssincfgw.exe) does not show this behavior.

How to reproduce.
First, the above three conditions must be met. Then do the followings.

1) Launch "Siebel Enterprise Configuration" utility. It is located under "Siebel Enterprise Server Configuration 8.1.1.0.0" program group by default.
Alternately it can be launched as "config.bat -mode enterprise" using command window under SIEBEL_HOME\config folder.
** SIEBEL_HOME is where Siebel Enterprise Server has been installed.
2) Select "Create New Configuration" > "Configure a New Enterprise in a Gateway Name Server".
3) Enter necessary information for each step until it reaches the screen for "RDBMS Platform". Here, select "IBM DB2 UDB for Linux UNIX Windows"
4) Enter necessary information for the rest. Selection of "Enterprise Security Authentication Profile" does not affect the result.
5) At the last screen, "The Siebel Configuration Wizard will execute using the following settings:", click Next.
6) Few seconds later, an error window pops up with the following message.
"Siebel Configuration Wizard failed with error. Please see the log files for details."

With the default command line, there is no detailed message on the screen or log file. But adding -verbose parameter for config.bat ("config.bat -mode enterprise -verbose") records more information on the config_MM-DD-YYYY_TT.MI.SS.log file under SIEBEL_HOME\config\cfg folder.

MM: Month
DD: Day
YYYY: Year
TT: Time
MI: Minute
SS: Second

FINER: 12 ==========>>>>> Executing the type logic for step : CompleteDb2Setup <<<<<============
Mar 22, 2013 2:52:06 PM oracle.siebel.configurator.engine.AccessSCM typeConditionCheck
FINER: =====Condition Step Extension=====
Mar 22, 2013 2:52:06 PM oracle.siebel.configurator.engine.AccessSCM typeConditionCheck
FINER: =====Condition Step Extension Create ODBC Entries=====
Mar 22, 2013 2:52:06 PM oracle.siebel.configurator.engine.AccessSCM typeConditionCheck
FINER: Calling Create ODBC Entries
Mar 22, 2013 2:52:06 PM oracle.siebel.configurator.utility.ConfigUtility CreateODBCEntries
FINER: Create ODBC Entries
Mar 22, 2013 2:52:06 PM oracle.siebel.configurator.utility.ConfigUtility CreateODBCEntries
FINER: Create ODBC Entries Platform: DB2
Mar 22, 2013 2:52:06 PM oracle.siebel.configurator.utility.ConfigUtility CreateODBCEntries
FINER: Create ODBC Entries DriverPath: C:\Program
Mar 22, 2013 2:52:06 PM oracle.siebel.configurator.utility.ConfigUtility CreateODBCEntries


Note: On the second line from the bottom, it shows "DriverPath: C:\Program" instead of "C:\Program Files\IBM\SQLLIB\BIN\DB2CLI.DLL" because the path contains space that is treated as the delimiter.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.