Last updated on JULY 31, 2017
Applies to:JDBC - Version 126.96.36.199 to 188.8.131.52.0 [Release 11.1 to 11.2]
Oracle Net Services - Version 184.108.40.206 to 220.127.116.11 [Release 11.2]
Information in this document applies to any platform.
JDBC thin 11g connections using Single Client Access Name (SCAN) fail with errors:
ORA-12520: TNS:listener could not find available handler for requested type of server
ORA-12516: TNS : listener could not find instance with matching protocol stack
when client and database are on different networks and Network Address Translation (NAT) router is used for translation.
JDBC OCI and SQL*Plus connections work fine. JDBC connections using the HOST vip names work fine over the NAT router, only connections using SCAN fail. JDBC thin connections using SCAN without NAT router work without any problems
Network Devices like NAT, Load Balancers and usage of Domain Name Server (DNS) aliases for the SCAN name cause this failure.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms