Error "IO Exception : End of TNS data channel" When Connecting with Multiple ADDRESS_LIST. (Doc ID 750796.1)
To Bottom
Modified:28-Aug-2012Type:PROBLEMStatus:PUBLISHEDPriority:3
Comments (0)
In this Document
Symptoms
Changes
Cause
Solution
References
Applies to:
JDBC - Version10.2.0.3 and later
Information in this document applies to any platform.
***Checked for relevance on 28-Aug-2012***
Symptoms
When connecting using a JDBC/thin 10.2.0.3driver using the following URL:
String thinConn = "jdbc:oracle:thin:@( DESCRIPTION = ( ADDRESS_LIST= (ADDRESS = (PROTOCOL=TCP)(HOST=host1)(PORT=1521) )
(ADDRESS = (PROTOCOL=TCP)(HOST=host2)(PORT=1521) )
(LOAD_BALANCE=true)(FAILOVER=true)
)
( ADDRESS_LIST = (ADDRESS = (PROTOCOL=TCP)(HOST=host3)(PORT=1521) )
(ADDRESS = (PROTOCOL=TCP)(HOST=host4)(PORT=1521) )
(LOAD_BALANCE=true)(FAILOVER=true)
)
(CONNECT_DATA=(SERVICE_NAME=orcl)(SERVER=DEDICATED)))\n";
you get the following error:
Error : IO Exception : End of TNS data channel
The same connection works fine with JDBC 10.2.0.4
Changes
Using multiple ADDRESS_LIST clauses isuseful in a DataGuard environment, when both the primary and secondarydatabases are RAC.
Cause
This is caused by internal BUG 12029725 -JavaNet throws exception with nested/multiple ADDRESS_LIST clauses
as explained in:
Note4570363.8- BUG 12029725 - JavaNet throws exception with nested/multipleADDRESS_LIST clauses
Solution
Use the JDBC/thin driver version10.2.0.4.0 or later. The latest versions can be downloaded here.
OR
use only one ADDRESS_LIST clause
References
NOTE:401436.1- 10.2.0.4 Patch Set - List of Bug Fixes by Problem Type
NOTE:4570363.8- Bug 4570363 - JavaNet throws exception with nested/multiple ADDRESS_LISTclauses
BUG:4570363- I/O EXCEPTION WHEN CONNECTING WITH NET KEYWORD OF NESTED ADDRESS_LIST CLAUSE
Related
…
Products
…
· Middleware > Developer Tools > Java Development > JDBC > Thin JDBC driver
Keywords