Siebel Server Installation Guide for UNIX > Installing the Siebel Server > Post-Installation Tasks for Siebel Server >

Verifying the Siebel Server ODBC Data Source

The Siebel Server installation program automatically creates an ODBC system data source name (DSN) that it uses to connect to the Siebel Database Server.

To verify the ODBC data source for DB2 UDB

  1. Open the db2cli.ini file in the $SIEBEL_HOME directory and make sure that there is a section called [siebsrvr_enterprise name], where enterprise name is the name given the enterprise during installation; its default name is siebel.
  2. Verify that the following two values are present in the section:

    3. dbalias = aliasname (the database alias cataloged for your DB2 UDB database server)

    txnisolation = 1.

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

    NOTE:  It is not recommended to change the default settings created automatically with the ODBC data source.

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

    4. CAUTION:  If you are using Siebel Marketing, which requires simultaneous heterogeneous database connectivity, you need to set this variable to ORACLE regardless of your database platform.

  4. Test the connection by navigating to $SIEBEL_HOME/bin and entering the command:

    5. odbcsql /u user_name /p password /s ODBC DSNW

    where:

    ODBC DSN is the database connect string.

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

To verify the ODBC data source for Oracle

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

    3. This section defines the ODBC DSN for Siebel Server. A sample section is represented below. The ServerName, Driver, ColumnsAsChar, and ColumnSizeAsCharacter parameters are the most critical for this procedure:

    [SiebSrvr_enterprise name]
    Description=Oracle901
    ServerName=dvlsun6
    Driver=$SIEBEL_HOME/lib/SEor818.so
    ColumnsAsChar=1
    ColumnSizeAsCharacter=1

    The ServerName should be the Oracle connect string you entered while installing the Siebel Server. (To verify this connect string, run sqlplus.) The driver should point to $SIEBEL_HOME/lib/SEor818.so, allowing you to verify the existence of this file.

    CAUTION:  It is critical that ColumnsAsChar and ColumnSizeAsCharacter be set to 1 to make sure that ODBC Driver behaves correctly.

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

    4. CAUTION:  If you are using Siebel Marketing, which requires simultaneous heterogeneous database connectivity, you need to set this variable to ORACLE regardless of your database platform.

  4. Test the connection by navigating to $SIEBEL_HOME/bin and entering the command:

    5. odbcsql /u user_name /p password /s ODBC DSN

    where:

    ODBC DSN is the database connect string.

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

    NOTE:  If your ODBC DSN is not working, the program exits with an error message. Refer to Troubleshooting ODBC Data Source Connection.

Troubleshooting ODBC Data Source Connection

If your connection test for the ODBC data source fails, follow the instructions below to research the cause.

DB2 UDB

Follow the instructions below to troubleshoot connection problems on Solaris, AIX, or HP-UX.

To troubleshoot a failed ODBC connection on Solaris, AIX, or HP-UX

  1. Verify that the database alias entered as part of the Siebel Server configuration is valid, enter:

    2. db2 connect to Database Alias user username using password

    where:

    Database Alias is the alias of the database.

    username is your logon ID.

    password is your logon password.

    Also, refer to your copy of Deployment Planning Worksheets.

  2. If the database alias entered is correct, check the ODBCINI environment variable to verify that it was set by entering the following command:

    3. echo ${ODBCINI}

    The response should be the following:

    $SIEBEL_ROOT/sys/.odbc.ini

  3. If the ODBCINI environment variable was set correctly, verify that the.odbc.ini file has a section similar to the following:

    4. [siebsrvr_enterprise]
    ServerName=Database Alias
    Driver=/instances/v7inst1/sqllib/lib/libdb2.so (Solaris and HP-UX)

    or

    Driver=/instances/v7inst1/sqllib/lib/libdb2.o (AIX)

  4. Make sure that the library file referenced in the Driver key in Step 3 exists.
  5. If the section in the .odbc.ini file, illustrated in Step 3, exists, verify that the LD_LIBRARY_PATH (Solaris), SHLIB_PATH (HP-UX), or LIBPATH (AIX) includes the path for the ODBC driver by entering the following command:

    6. Solaris: echo ${LD_LIBRARY_PATH}

    AIX: echo ${LIBPATH}

    HP-UX: echo $[SHLIB_PATH}

  6. If the response illustrated for your platform in Step 5 was correct and you are verifying a Unicode installation, make sure that the following environment variables are set in accordance with the recommendations from your database platform vendor. These variables should also be set in the siebenv.csh and siebenv.sh scripts.

    7. SIEBEL_UNIXUNICODE_DB=DB2

Oracle

Complete the following instructions to troubleshoot connection problems on Solaris, AIX, and HP-UX.

NOTE:  If you are unable to verify if your ODBC connection to your Oracle database is working, you should verify that the value of the environment variable TNS_ADMIN is the exact path of tnsnames.ora.

To troubleshoot a failed ODBC connection on Solaris, AIX, or HP-UX

  1. Verify that the Oracle connect string entered as part of Siebel Server configuration is valid.
  2. If the connect string entered is correct, check the ODBCINI environment variable to verify that it was set by entering the following command:

    3. echo ${ODBCINI}

    The response should be the following:

    $SIEBEL_ROOT/sys/.odbc.ini

  3. If the ODBCINI environment variable was correctly set, verify that the .odbc.ini file is valid by reviewing it for the presence of the following parameters:

    4. [SiebSrvr_Enterprise Name]
    ServerName=ora901
    Driver=/$SIEBEL_ROOT/lib/SEor818.so
    ColumnsAsChar=1
    ColumnSizeAsCharacter=1

    If these parameters are not present, the file is invalid.

  4. If the .odbc.ini file is valid, verify that the library path includes the path for the ODBC driver on your platform by entering the following command:

    5. Solaris: echo ${LD_LIBRARY_PATH}

    AIX: echo ${LIBPATH}

    HP-UX: echo ${SHLIB_PATH}

    The response should be $SIEBEL_ROOT/lib.

NOTE:  Siebel applications only support an Oracle 32-bit client for Oracle 8i. Therefore, if you have installed an Oracle 64-bit client on your Siebel Server, you need to add $ORACLE_HOME/lib32 instead of $ORACLE_HOME/lib to your LD_LIBRARY_PATH (Solaris), SHLIB_PATH (HP-UX), or LIBPATH (AIX).

  1. If the response illustrated for your platform in Step 4 was correct and you are verifying a Unicode installation, make sure that the following environment variables are set in accordance with the recommendations from your database platform vendor. These variables should also be set in the siebenv.csh and siebenv.sh scripts.

    2. SIEBEL_UNIXUNICODE_DB=ORACLE


 Siebel Server Installation Guide for UNIX 
 Published: 24 June 2003