Siebel Installation Guide for Microsoft Windows > Configuring Siebel Enterprise Server and Related Components > Verifying the ODBC Data Source >
Verifying the ODBC Data Source for Oracle
This topic is part of Verifying the 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 on the RDBMS. Prior to verifying the Siebel Server ODBC data source, make sure that the Siebel Server service is started.
Information in this topic applies also to virtual ODBC data sources in a clustered environment.
CAUTION: In general, do not change the default settings created automatically with the ODBC data source. However, if you have upgraded from Oracle 8i or 9i (RBO) to Oracle 10g (CBO), or if you manually created your ODBC, it is critical that you check your ODBC settings, as shown in the following procedure.
For more information about the ODBC data source, see Planning RDBMS Installation and Configuration.
To verify the ODBC data source for Oracle (on Windows)
- Navigate to Control Panel, Administrative Tools, then Data Sources (ODBC).
- On the ODBC Data Source Administrator dialog box, select the System DSN tab.
- Review the data source name; its default name is EnterpriseName_DSN, where EnterpriseName is the name you gave the Siebel Enterprise during its configuration.
- Record the name of the ODBC data source in Deployment Planning Worksheet if you have not already done so.
- Select the data source EnterpriseName_DSN, and click Configure.
The ODBC Oracle Driver Setup screen appears.
- To test the connection, click Test Connect.
If the connection is valid, you will see a message box confirming the connection.
If the connection could not be made, see Verifying Network Connectivity for the Siebel Server Machine and Troubleshooting the ODBC Data Source Connection.
- In the Windows registry, locate the following registry entry:
Verify that the following registry keys are set as shown. These values are required in order for the ODBC driver to behave correctly.
PacketSize = 0
EnableScrollableCursors = 0
ColumnsAsChar = 1
ColumnSizeAsCharacter = 1