Bookshelf Home | Contents | Index | PDF     

Siebel Installation Guide for UNIX > Verifying and Troubleshooting Your Installation >

Verifying the ODBC Data Source

This topic provides information about verifying the ODBC data source for your enterprise database platform. It includes the following information:

Related Topics

Troubleshooting the ODBC Data Source Connection

Planning RDBMS Installation and Configuration

Verifying the ODBC Data Source for Oracle Database

Configuring the Siebel Enterprise automatically creates an ODBC system data source name (DSN) that the Siebel Server uses to connect to the Siebel database on the RDBMS.

Make sure that a supported version of the Oracle Database Client has been installed and that the Siebel Server service is started prior to verifying the ODBC data source. This topic applies also to virtual ODBC data sources in a clustered environment.

CAUTION:  In general, do not change the default settings that are created automatically with the ODBC data source. However, if you have upgraded from an Oracle Database that does not use CBO, or if you manually created your ODBC, then you must check your ODBC settings, as shown in the following procedure.

To verify the ODBC data source for Oracle Database (on UNIX)

  1. Navigate to the file $SIEBEL_HOME/sys/.odbc.ini, and open this file for editing.
  2. Locate the section of the file containing a reference to ServerName and Driver.

    This section defines the ODBC data source for Siebel Server. A sample section is represented in the following example:

    [EnterpriseName_DSN]
    ServerName=oraDB4
    Driver=$SIEBEL_HOME/lib/SEor827.so
    ColumnsAsChar=1
    ColumnSizeAsCharacter=1

    CAUTION:  The ColumnsAsChar and ColumnSizeAsCharacter parameter settings are required in order for the ODBC driver to behave correctly.

    ServerName is the Oracle connect string that you entered while configuring the Siebel Enterprise. (To verify this connect string, run sqlplus.) The driver must point to $SIEBEL_HOME/lib/SEor827.so, allowing you to verify the existence of this file.

  3. Verify that the SIEBEL_UNIXUNICODE_DB environment variable is set to ORACLE.

    NOTE:  If you use Siebel Marketing, which requires simultaneous heterogeneous database connectivity, then set this variable to ORACLE, regardless of your database platform.

  4. Source the siebenv.csh (for C shell) or siebenv.sh (for Bourne or Korn shell) file.
  5. Test the connection by navigating to $SIEBEL_HOME/bin and entering the command:

    odbcsql /u database_account_name /p password /s ODBC_DSN

    where:

    • database_account_name is a valid database account name.
    • password is the corresponding database account password.
    • ODBC_DSN is the ODBC data source name, in the form SiebelEnterpriseName_DSN. In the data source name, SiebelEnterpriseName is the name of your Siebel Enterprise.

      If you do not receive an error message, then the ODBC connection is working. If your ODBC DSN is not working, then the program exits with an error message. For more information, see Verifying Network Connectivity for the Siebel Server Computer and Troubleshooting the ODBC Data Source Connection.

Verifying the ODBC Data Source for IBM DB2

Configuring the Siebel Enterprise automatically creates an ODBC system data source name (DSN) that the Siebel Server uses to connect to the Siebel database on the RDBMS.

Make sure that the appropriate database client has been installed and that the Siebel Server service is started prior to verifying the ODBC data source. This topic applies also to virtual ODBC data sources in a clustered environment.

CAUTION:  Do not change the default settings that are created automatically with the ODBC data source.

NOTE:  For information about verifying the ODBC data source for IBM DB2 for z/OS, see Implementing Siebel Business Applications on DB2 for z/OS.

To verify the ODBC data source for IBM DB2 (on UNIX)

  1. Open a DB2 Command Window.
  2. Run the following command:

    db2 get cli cfg for section SiebelEnterpriseName_DSN

    In the data source name, SiebelEnterpriseName is the name given the Siebel Enterprise during initial configuration, for example sieb17.

    Entering this command generates the following results:

    Section: SiebelEnterpriseName_DSN
    -------------------------------------------------
    dbalias=SBL
    clipkg=6
    txnisolation=1

    The value for dbalias is the database alias catalogued for your DB2 database server.

    If the SiebelEnterpriseName_DSN section is missing, then run the configdb2 script in $SIEBEL_HOME/bin to set it, and then verify again that the section is present.

    See also Guidelines for Preventing IBM DB2 from Running Out of ODBC Statement Handles.

  3. Verify that the SIEBEL_UNIXUNICODE_DB environment variable is set to DB2.

    NOTE:  If you use Siebel Marketing, which requires simultaneous heterogeneous database connectivity, then set this variable to ORACLE, regardless of your database platform.

  4. Source the siebenv.csh (for C shell) or siebenv.sh (for Bourne or Korn shell) file.
  5. Test the connection by navigating to $SIEBEL_HOME/bin and entering the command:

    odbcsql /u database_account_name /p password /s ODBC_DSN

    where:

    • database_account_name is a valid database account name.
    • password is the corresponding database account password.
    • ODBC_DSN is the ODBC data source name, in the form EnterpriseName_DSN. In the data source name, EnterpriseName is the name of your Siebel Enterprise.

      If you do not receive an error message, then the ODBC connection is working.

      If your ODBC DSN is not working, then the program exits with an error message. For more information, see Verifying Network Connectivity for the Siebel Server Computer and Troubleshooting the ODBC Data Source Connection.

      
Siebel Installation Guide for UNIX Copyright © 2017, Oracle and/or its affiliates. All rights reserved. Legal Notices.