Deploying Siebel CRM using Case Insensitive (CI) collation (Doc ID 1375507.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Purpose

This Bulletin provides important information if you are planning to deploy Siebel CRM applications using Microsoft SQL Server database and Case Insensitive collation.

While running the Database Server Configuration wizard for Siebel versions 8.1.x and 8.2.x for initial database installation, and choosing Microsoft SQL Server for database platform, the wizard shows 2 options for selecting database collation:

_ Binary Sort Order
_ Case Sensitive

The Database Server Configuration wizard for Siebel versions 8.1.x and 8.2.x does not have the an option for creating a Siebel database using Case Insensitive collation.

According to the Siebel System Requirements and Supported Platforms versions 8.1.x and 8.2.x, three sort order options are supported for Microsoft SQL Server databases:

_ Binary or
_ Dictionary with Case Insensitive and Accent or
_ Dictionary with Case Sensitive

You should apply the steps described below to deploy a Siebel database using Case Insensitive (CI) collation on any version of a SQL Server database.

The same issue arose in IP 16.5, and it failed on:

S_APPL_WTMPL_IT_U1
S_DLL_U1

The customer changed the database collation to Latin1-General, binary sort and was able to import the repository.

<Bug 25292058> : IMPREP_PRIM FAILS WITH CANNOT INSERT DUPLICATE KEY ROW IN OBJECT

Scope

As per Microsoft's documentation "a collation encodes the rules governing the proper use of characters for either a language, such as Greek or Polish, or an alphabet, such as Latin1_General (the Latin alphabet used by western European languages)".On SQL Server the collation defines both the sort order, and the code page used to store non-Unicode character data.

In general Binary sort order may give improved performance. Additionally, Siebel Development environments must always use Binary sort order, due to Siebel Tools requirements. On certain scenarios, however, you may want to use Case Insensitive for a Test or Production environment.

If you use Oracle or DB2 databases different concepts involving character sets apply, and similar issues should not exist.

Details

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