My Oracle Support Banner

11g JDBC Driver Changes Behavior While Using A Firewall Between The Client And The Database Server (ORA-17410) (Doc ID 1325081.1)

Last updated on MAY 06, 2021

Applies to:

JDBC - Version 11.1.0.6 and later
Information in this document applies to any platform.
***Checked for relevance on 29-Oct-2012***

Symptoms

On : 11.2.0.1.0 version, JDBC for Java

Find the next behavior:

11g JDBC driver fails to throw ORA-1013 timeout exception when query timeout is set on the statement object. Instead it throws a ORA-17410 at an indeterminate time.

It should throws the same ora-1013 timeout exception as it was in the previous releases.
This is only happening using the 11g jdbc release.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:

1. Run the next program using the UCP and the 11g driver:


2. The communication between the Database and the client needs to go through a Firewall with the setup to clear the Urgent Bit in the communication.

3. It will not generate the ORA-1013 error, but the ORA-17410: No more data to read from socket error instead. If you use the 10g driver you will get the expected ORA-1013.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.