Troubleshooting Database Configuration

Important issues to note before configuring your database for the Siebel CRM monthly update are:

1. On all database platforms, the ODBC Data Source Name that you provide during installation (that is, when prompted by the installer wizard for Siebel Enterprise Server installer) must match the [Datasources] and [ConnectString] information provided in the siebel.cfg file, located in C:\siebel\siebsrvr\bin or equivalent location.

   For example, the following setting during installation:

   ODBC Data source name: Siebel_DSN

   must match the following in the siebel.cfg file for all database platforms:

   [DataSources]
   ServerDataSrc = Server
   
   [ServerDataSrc]
   ConnectString = siebel_DSN

   Before installing Siebel CRM monthly updates and in order to ensure successful patch application, you must verify that all respective files are available for your database (MSSQL, Oracle, or DB2UDB & DB2390). In the case of Oracle database, certain changes are also required. For more information, see the following topics:

   • Verify Files for MSSQL Database
   • Verify Files for Oracle Database
   • Verify Files for DB2UDB & DB2390

2. For all database types, the CurrentSQLID parameter must be set correctly in the [ServerDataSrc] section of the siebel.cfg file.

   [ServerDataSrc]
   CurrentSQLID = SSE_ROLE

3. (Specific to Oracle Database) Add the following registry entry in the Windows registry:

   [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ODBC\ODBC.INI\<Data Source Name>]_

   Verify that the following registry keys are set as shown:

   ColumnsAsChar = 1
   ColumnSizeAsCharacter = 1

   These values are required for the ODBC driver to behave correctly.

4. If execution of the PostInstallDBSetup utility fails, then rerun the PostInstallDBSetup executable using the following command from the command line:

   PostInstallDBSetup.exe -i Setup.ini -p xxxx -z xxxx

   For more information, see Rerunning Post Installation Database Update.

Verify Files for MSSQL Database

Before installing Siebel CRM monthly updates and in order to ensure successful patch application, you must verify that the following files are available for MSSQL database:

• ODBCAD32.exe

• siebel.cfg

The following table includes more information about these files.

Files	File Location	MSSQL Database
ODBC Datasource	Windows: C:\Windows\SysWOW64\odbcad32.exe	Connects to siebel_DSN.
Siebel.cfg	Windows: C:\siebel\siebsrvr\bin\enu	[DataSources] ServerDataSrc = Server [ServerDataSrc] ConnectString = siebel_DSN

The Microsoft JDBC Driver has been updated to version 12.8.x and this version of the driver has, by default, enabled the (Transport Layer Security) TLS protocol. It has its Encrypt setting set to True. If your database and gateway security profile already use the TLS protocol, there is no issue. If, however, your database uses TCP you must do one of the following to allow the Siebel application to communicate with your database over TLS. Oracle recommends option 1.

1. Setup a TLS port on your database and create or update the Gateway Security Profile via DB Advanced mode in the Siebel Management Console (SMC) to use this TLS port and not the TCP port previously used.

   1. Import a trusted root CA certificate of DB server to your Gateway Trust Store JKS file.

   2. Restart Internal Tomcat.

2. Create or update your Gateway Security Profile in the SMC over safe mode and add trustServerCertificate=true with a JDBC connection string in DB Advanced mode (Not recommended).

   For example: [host]:[port];databaseName=[databaseName];trustServerCertificate=true;

3. Restart Internal Tomcat.

Note: Enable Safe mode in SMC before applying this patch and Launch SMC in safe mode to Update the Gateway Security Profile.

Verify Files for Oracle Database

Before installing Siebel CRM monthly updates and in order to ensure successful patch application, you must verify that the following files are available and that all required changes have been made for Oracle database:

• ODBCAD32.exe

• tnsnames.ora

• siebel.cfg

The following table includes more information about these files.

Files	File Location	Oracle Database
tnsnames.ora	Windows: <Oracle client location> UNIX: <Root directory>	A hostname_instance section is created by default in the tnsnames.ora file. Copy and paste the hostname_instance section and create a new section with, for example, the name siebel_DSN. Note that the siebel_DSN name should be the same across all files for the Oracle database. siebel_DSN = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (COMMUNITY = siebel.com) (PROTOCOL = TCP) (HOST = hostname) (PORT = 1551) ) ) (CONNECT_DATA = (SID = instance) ) )
ODBC Datasource	Windows: C:\Windows\SysWOW64\odbcad32.exe UNIX: /<BuildLocation>/ses/siebsrvr/sys/.odbc.ini	Connects to siebel_DSN on Windows and UNIX. In the [Siebel_DSN] section, set ServerName = siebel_DSN, which is defined in tnsnames.ora. UNIX file content: [siebel_DSN] Driver = /export/home/sblqa/2303/ses/siebsrvr/lib/SEor827.so ColumnSizeAsCharacter = 1 ColumnsAsChar = 1 ArraySize = 160000 ServerName = siebel_DSN
Siebel.cfg	Windows: C:\siebel\siebsrvr\bin\enu UNIX: /<BuildLocation>/ses/siebsrvr/bin/enu	In the [ServerDataSrc] section, set ConnectString = siebel_DSN. [DataSources] ServerDataSrc = Server [ServerDataSrc] ConnectString = siebel_DSN

Verify Files for DB2UDB & DB2390

Before installing Siebel CRM monthly updates and in order to ensure successful patch application, you must verify that the following files are available for DB2UDB & DB2390 databases:

• ODBC Datasource

• Siebel.cfg

• db2cli.ini

The following table includes more information about these files.

Files	File Location	DB2UDB & DB2390 Databases
ODBC Datasource	Windows: C:\Windows\SysWOW64\odbcad32.exe UNIX: /<BuildLocation>/ses/siebsrvr/sys/.odbc.ini	Connects to siebel_DSN on Windows and UNIX with ServerName = <DBNAME>. UNIX file content: [siebel_DSN] Driver = /export/home/sblqa1/sqllib/lib/libdb2.a ServerName = <DBNAME>
Siebel.cfg	Windows: C:\siebel\siebsrvr\bin\enu UNIX: /<BuildLocation>/ses/siebsrvr/bin/enu	[DataSources] ServerDataSrc = Server [ServerDataSrc] ConnectString = siebel_DSN
db2cli.ini	Windows: C:\ProgramData\IBM\DB2\<DB2COPY> UNIX: /<Build location>/ses/siebsrvr	Connects to siebel_DSN on Windows and UNIX with dbalias = <DBNAME>. [siebel_DSN] dbalias = <DBNAME> txnisolation = 1