ODAC (V9.5.15) study notes (16) Direct access mode

Direct mode is one of the biggest features of ODAC, which means that no Oracle client installation is required, Odac crosses the OCI (Oracle call Interface) and communicates directly with the Oracle server using the TCP/IP protocol. This makes the ODAC program very easy to deploy and has very high performance.

To set the direct access mode, you only need to set the connection component's selection direct to True

Session.Options.Direct: = True;

Other parameters are set with normal mode. The advantage of using direct access mode is that there is no need to install an Oracle client, deployment is more convenient and resource consumption is reduced, but there are also limitations, including:

1. Only use the TCP/IP protocol.

2. Individual data types are not supported, including object, ARRAY, REF, XML, binary_double, binary_float, etc.

3. The Rowsaffected property result cannot be returned when using returning in SQL.

4. Toraloader Direct import data is not supported.

5. The NLS conversion of the client is not supported.

6. The Transparent application redundancy mode (Transparent application failover, TAF) is not supported.

7. SQL statement buffering mode (statement caching) is not supported.

8. The operating System identity authentication function (OS authentication feature) is not supported.

9. The Change message notification component (TORACHANGENOTIFICATION) is not supported.

10. It is recommended that each thread use separate Torasession components under multi-threading, which does not guarantee the stability of a torasession under multithreading.

ODAC (V9.5.15) study notes (16) Direct access mode