TOC PREV NEXT INDEX



Easysoft ODBC-Oracle Driver User Guide - Technical Reference

Technical Reference for the Easysoft ODBC-Oracle Driver

This section contains extra information relating to the deployment of the Easysoft ODBC-Oracle Driver.

Appendix Guide

Oracle® Client software

Obtaining the Oracle® Client software

Contact your Oracle® Database Administrator if the Oracle® Client software is not installed.

Alternatively, an Oracle® distribution can be downloaded from http://technet.oracle.com (registration is required).


Caution!

Easysoft advise that Oracle® Client software is installed from a distribution CD if fast internet access is unavailable, as the download may require significant temporary disk space.


Installing the Oracle® Client software

There are instructions on how to run the Oracle® installer on the Oracle® site (http://technet.oracle.com).

During the install choose the client software option and follow the instructions on the screen.

ODBC Conformance

The Easysoft ODBC-Oracle Driver is an ODBC 3.5 driver and uses the driver manager to provide the deprecated and old ODBC 2 functions:

SQLBrowseConnect

SQLBulkOperations

SQLCopyDesc

SQLDescribeParam (not supported by default but see Describe Parameters)

SQLSetPos

Cursor support in the Easysoft ODBC-Oracle Driver is restricted to FORWARD_ONLY and STATIC.

Oracle® 8, 9 and 10g

The Easysoft ODBC-Oracle Driver will work with both 8i, 9i and 10g versions of Oracle®.

No changes to the driver setup are required if upgrading the Oracle® Client software.

Restrictions

The Easysoft ODBC-Oracle Driver will allow access to Oracle® databases on version 8.1.7 and upwards.

Supported Data Types

The following Oracle® data types are supported by the Easysoft ODBC-Oracle Driver:

Advanced Security

The Oracle® Advanced Security option is an Oracle® client or server add-on that combines network encryption, database encryption and strong authentication to protect sensitive data stored in Oracle® databases. The Advanced Security option:

Oracle® Advanced Security requires Net8 or Oracle® Net to transmit data securely. The Easysoft ODBC-Oracle Driver uses the Oracle® client which uses these protocols to communicate with the Oracle® database server over the network. Applications that access Oracle® by using the Easysoft ODBC-Oracle Driver can therefore take advantage of the Oracle® Advanced Security option.

For information about configuring the Oracle® client and server for use with the Oracle® Advanced Security option, see the Oracle® Advanced Security Administrator's Guide. No additional Easysoft ODBC-Oracle Driver configuration is necessary.

RAC

The Easysoft ODBC-Oracle Driver will allow access to Oracle® RAC environments. The Oracle® client must be configured correctly to take full advantage of the RAC features. Please consult you Oracle® documentation for more details.

Network Protocols

The Easysoft ODBC-Oracle Driver supports both IPC and TCP/IP network protocols.

XA Support

The Easysoft ODBC-Oracle Driver can be configured to take part in a distributed XA transaction. To do this, add a data source that contains entries that correspond with the xa_open string used by the XA Transaction Manager to connect to the Oracle® database server.

For example, the following sample xa_open string opens an XA connection to an Oracle® database named "payroll." It also specifies the Net8 link and the username and password used to log onto the Oracle® server.

Oracle_XA+sqlnet=ninetwo.oracle+SesTm=35+Acc=P/system/manager+Threads=true+DB=payroll

To make this XA connection available for use by the Easysoft ODBC-Oracle Driver, the data source used to access Oracle® needs to contain the following corresponding entries.

[ORACLE-XA]

Driver = Oracle®

Database =ninetwo.oracle

User =system

Password =manager

XA_Enlist = 1

XA_Connection_String =payroll

In addition, the XA_Enlist attribute must be set to 1. When this setting is present, the Easysoft ODBC-Oracle Driver accesses Oracle® by using the Oracle® XA library. Note that the data source can then only be used to access an Oracle® database as an XA resource under the control of a Transaction Manager. If you need to access the same database with a non-XA connection, configure a separate data source without the XA_Enlist attribute.

The XA_Connection_String attribute is only required if the DB field is present in the xa_open string. The XA_Connection_String attribute value must be the same as that of the DB field.

A tutorial that provides more information about using the Easysoft ODBC-Oracle Driver in the context of an XA transaction is available from the Easysoft ODBC-Oracle Driver section of the Easysoft web site. The tutorial includes a code sample that shows the point at which an ODBC connection needs to be created and closed to participate in a distributed transaction.

Application Specific Issues

StarOffice 5.2

If problems occur with metadata, the METADATA_ID parameter needs to be set to 1 in the odbc.ini file.

OpenOffice 1.0

For Open Office 1.0 you need to check the No Metadata Schema check box in the dialogue or set METADATA_DONT_DO_SCHEMA to 1 in your odbc.ini file.

PHP4

PHP4 calls the SQLDescribeParams ODBC function when processing SQL statements that have parameters.

The Easysoft ODBC-Oracle Driver correctly reports that it does not support the SQLDescribeParams function, but PHP4 ignores this and continues with undefined results. See Describe Parameters.

Perl DBI

If attempting to fetch LONG data, set the DBI_LONG_SIZE to an appropriate value. See DBI Long Size.

Threading

The Easysoft ODBC-Oracle Driver is thread safe in accordance with the ODBC 3.5 specification and can be used behind threaded applications with confidence. Usually applications use one connection handle and multiple threads executing SQL statements on that connection.

Tracing

The ODBC calls an application makes can be traced:

Within the driver manager by an application

An application can turn tracing on in the driver manager via the ODBC API SQLSetConnectAttr (...,SQL_ATTR_TRACE,...).

The trace filename may also be specified with the SQLSetConnectAttr attribute SQL_ATTR_TRACEFILE.

From within the driver manager

Tracing in the driver manager is platform-specific:

Start the ODBC driver manager administration interface via Start Menu > Control Panel > ODBC Data Sources.

Click on Tracing, ensure the specified filename is valid and click Start Tracing Now.

For the unixODBC driver manager, add two attributes to the [ODBC] section (create one if none exists) in odbcinst.ini.

Trace = Yes|No

TraceFile = /path/filename

e.g.

[ODBC]

Trace = Yes

TraceFile = /tmp/sql.log

Ensure that the user who is running the application to be traced has write permission to TraceFile (and to the directory containing it), or no tracing information will be produced.

From within the Easysoft ODBC-Oracle Driver

Tracing in the Easysoft ODBC-Oracle Driver is platform-specific:

Update the Registry by running regedit and edit the key:

HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\DSN-NAME

where DSN-NAME is the name of the Easysoft ODBC-Oracle Driver data source.

Add a LOG string value and set it to the path and file name of the log file (e.g. \temp\oracle.log).

Add a LOG attribute to the DSN section of the odbc.ini file.

e.g.

[ORACLE]

.

.

.

LOG = /tmp/oracle.log

The LOG value is the path and file name of the log file (e.g. /tmp/oracle.log).


Copyright Notice
TOC PREV NEXT INDEX


Oracle is a registered trademark of Oracle Corporation and/or its affiliates.