2.3.2 Adding a Data Source Definition in Linux

Table of Contents Previous Next


2 EDB-ODBC Overview : 2.3 EDB-ODBC Connection Properties : 2.3.2 Adding a Data Source Definition in Linux

The Linux ODBC Administrator is a graphical tool that is distributed with unixODBC; you can use the ODBC Administrator to manage ODBC drivers and named resources. To add the ODBC Administrator to your system, open a terminal window, assume superuser privileges, and enter:
To invoke the ODBC Administrator (shown in Figure 2.9), open a terminal window and enter ODBCConfig.
linone
When you install the Advanced Server Connectors component, the EDB-ODBC driver is added to the list of drivers in the ODBC Administrator. Click Advanced, and then select the Drivers tab to verify that the enterprisedb driver appears in the list (see Figure 2.10).
linone
If the EDB-ODBC driver does not appear in the list of drivers, you can add it using the ODBC Administrator. To add a driver definition, select the Drivers tab, and click Add. The Driver Properties (new) window opens, as shown in Figure 2.11.
Screenshot-Driver Properties (new)-1
Figure 2.11 – The Driver Properties window.
Complete the Driver Properties window to register the EDB-ODBC driver with the driver manager:
Add the path to the location of the EDB-ODBC driver in the Driver field. By default, the complete path to the driver is:
Add the path to the location of the EDB-ODBC driver setup file in the Setup field. By default, the complete path to the driver setup file is:
When you’ve described the driver properties for the EDB-ODBC driver, click OK. The ODBC Data Source Administrator window now includes the EDB-ODBC driver in the list of available ODBC drivers (Figure 2.12).
Screenshot-ODBC Administrator
Choose the User tab to add a named data source that is available only to the current user (the data source will be stored in ~user/.odbc.ini).
Choose the System tab add a named data source that is available to all users. All system data sources are stored in a single file (usually /etc/odbc.ini).
Choose the File tab to add a named data source that is available to all users, but that is stored in a file of your choosing.
Select the appropriate tab and click Add. The Create a New Data Source… window opens, as shown in Figure 2.13.
Screenshot-Create New Data Source
Select the EDB-ODBC driver from the list, and click OK to open the Data Source Properties window.
Complete the Data Source Properties (new) window (shown in Figure 2.14), specifying the connection properties for the EDB-ODBC driver.
Screenshot-Data Source Properties (new)
Figure 2.14 – The Data Source Properties window.
The unixODBC driver includes a trace utility that records the sequence of calls made an ODBC application to a log file. Specify 지원 in the Trace field to turn the trace utility on. Note that using the trace utility can slow down an application.
Use the TraceFile field to specify a file to receive information returned by the Trace utility.
Use the Protocol field to specify a front-end/back-end protocol version; the default value is 6.4. You can optionally select from protocol versions 7.4, 6.4, 6.3 or 6.2.
Use the ReadOnly field to specify 지원 to prevent the driver from executing the following commands: INSERT, UPDATE, DELETE, CREATE, ALTER, DROP, GRANT, REVOKE or LOCK. Enabling the Read Only option also prevents any calls that use the ODBC procedure call escape syntax (call=procedure-name?). By default, ReadOnly is set to No.
Use the RowVersioning field to specify 지원 if the driver should include the xmin column when reporting the columns in a table. The xmin column is the ID of the transaction that created the row. You must use row versioning if you plan to create cursors where SQL_CONCURRENCY = SQL_CONCUR_ROWVER. By default, Row Versioning is set to No.
Use the ShowSystemTables field to specify 지원 if the driver should include system tables in the result set of the SQLTables() function. By default, this field is set to No.
Use the ShowOidColumn field to specify 지원 if the driver should include the OID column in the result set of the SQLColumns() function. If ShowOidColumn is set to No, the OID column is hidden from SQLColumns(). By default, this option is set to No.
Use the FakeOidIndex field to specify Yes if the SQLStatistics() function should report that a unique index exists on each OID column. This is useful when your application needs a unique identifier and your table doesn’t include one. The default value is No.
Use the ConnSettings field to specify a list of parameter assignments that the driver will use when opening this connection.
Screenshot-ODBC Administrator-1

2 EDB-ODBC Overview : 2.3 EDB-ODBC Connection Properties : 2.3.2 Adding a Data Source Definition in Linux

Table of Contents Previous Next