How To Create a Local Installation of the Siebel ODBC DSN for Use With Clustering (Doc ID 1958429.1)

Last updated on JANUARY 31, 2017

Applies to:

Siebel CRM - Version 8.1.1 [21112] to 16.9 [IP2016] [Release V8 to V16]
Microsoft Windows x64 (64-bit)

Goal

In order to facilitate a clustered environment setup and avoid startup issues with either the Gateway Server or Siebel Server when they are installed on different cluster disk upon a cluster resource failure, it is recommended to create a local installation of the ODBC DSN that is not dependent on the ODCB driver that resides by default beneath the Siebel installation directory structure.

Please note that all Siebel Servers installed into an Enterprise Server use the same ODBC data source, including the Gateway Server service since the Siebel version 8.1.x.
By default, the name for the ODBC data source is <enterprise_name>_DSN; this is the format used since the Siebel version 8.0.x.

See: <Note: 985591.1> for further details about symptoms and another possible solution.

Note: This document is only applicable for Oracle Database Server.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms