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.
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.
The Easysoft ODBC-Oracle Driver will allow access to Oracle® databases on version 8.1.7 and upwards.
The following Oracle® data types are supported by the Easysoft ODBC-Oracle Driver:
The TIMESTAMP data type is not supported by Oracle® 8 and the retrieval of TIMESTAMP data requires the installation of both Client and Server of version 9 or above.
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.
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.
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.
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.
Driver = Oracle®
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.
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.
If problems occur with metadata, the METADATA_ID parameter needs to be set to 1 in the odbc.ini file.
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 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.
If attempting to fetch LONG data, set the DBI_LONG_SIZE to an appropriate value. See DBI Long Size.
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.
The ODBC calls an application makes can be traced:
The trace filename may also be specified with the SQLSetConnectAttr attribute SQL_ATTR_TRACEFILE.
Add a LOG attribute to the DSN section of the odbc.ini file.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates.