1. Known Issues for Oracle Database Exadata Express Cloud Service
  2. Known Issues
  3. Development — ODP.NET

Development — ODP.NET

This section describes issues associated with ODP.NET development.

Topics

Features Not Supported (ODP.NET)

Managed and unmanaged ODP.NET do not support the following features when connecting to Exadata Express:

  • .NET Bulk Copy

  • Advanced Queuing (AQ)

  • Any authentication besides username/password

  • Application Continuity

  • Client Result Cache

  • Continuous Query Notification

  • Data types:

    • BFILE

    • User-defined types when using IN or IN OUT parameter binding

      User-defined types include objects, collections (VARRAY and nested table), and references.

    • VARCHAR2 with increased size limit to 32 KB

      VARCHAR2 of sizes up to 4 KB are supported.

    • XMLType when using IN or IN OUT parameter binding

  • Distributed transactions

  • Fast Application Notification (FAN)

    Features that rely on FAN, such as planned outage, runtime connection load balancing, and fast connection failover are not supported. In ODP.NET 12.1 or earlier, an error is received if FAN is turned on.

  • Sharding

  • Database Resident Connection Pooling

Connection Request Encounters "ORA-28865: SSL connection closed" Error Intermittently

The error ORA-28865: SSL connection closed may be encountered intermittently when trying to establish simultaneous connections or in transient load scenarios.

Workaround

If you’re using ODP.NET, Managed Driver, decrease the Incr Pool Size connection string attribute value one at a time until you no longer see this error when trying to establish connections. Decreasing the Min Pool Size connection string attribute value may also help to reduce the number of connections initially created when a connection pool is created, which reduces the possibility of encountering this error.

If you’re using ODP.NET, Unmanaged Driver, decrease the Min Pool Size connection string attribute value to reduce the number of connections initially created for the connection pool. With ODP.NET, Unmanaged Driver 12.1.0.2 or later, adding the RETRY_COUNT and RETRY_DELAY settings in the descriptors of tnsnames.ora may also help. For RETRY_COUNT, start with a value of 1 and tune upwards as needed. Choose a reasonable value for RETRY_DELAY so the server isn’t throttled with retries.