Siebel Installation Guide for Microsoft Windows > Verifying and Troubleshooting Your Installation >

Troubleshooting the ODBC Data Source Connection

This topic describes troubleshooting steps for your ODBC data source connection.

NOTE:  If your database is IBM DB2 for z/OS, then see Implementing Siebel Business Applications on DB2 for z/OS.

This topic has the following information:

• Troubleshooting Connection Problems on Oracle Database
• Troubleshooting Connection Problems on IBM DB2
• Troubleshooting Connection Problems on Microsoft SQL Server

Troubleshooting Connection Problems on Oracle Database

Complete the following instructions to troubleshoot Oracle Database connection problems on Windows. See also Configuring Siebel Server Connectivity to the Siebel Database.

To troubleshoot a failed ODBC connection for Oracle Database

1. Verify that the ODBC driver was correctly installed by reviewing the file structure under SIEBSRVR_ROOT/BIN.
2. If the files have been correctly copied to the BIN subdirectory, then verify that the Oracle connect string that you entered during the Siebel Enterprise configuration was valid.

Troubleshooting Connection Problems on IBM DB2

Complete the following instructions to troubleshoot IBM DB2 connection problems. See also Configuring Siebel Server Connectivity to the Siebel Database.

To troubleshoot a failed ODBC connection for IBM DB2

• Verify that the data source name (SiebelEnterpriseName_DSN) that you entered during the Siebel Server configuration was valid. Also verify that the required IBM DB2 client version is available on the computer and verify that the IBM DB2 catalog step has been completed correctly.

Troubleshooting Connection Problems on Microsoft SQL Server

Complete the following instructions to troubleshoot Microsoft SQL Server connection problems on Windows. See also Configuring Siebel Server Connectivity to the Siebel Database.

To troubleshoot a failed ODBC connection for Microsoft SQL Server

• Verify that the data source name (SiebelEnterpriseName_DSN) that you entered during the Siebel Server configuration was valid. Also verify that the SQL Server database is up and running, and validate the ODBC connectivity.