DRCP: ORA-12170 With Combination RAC, DRCP and a Firewall

(Doc ID 953277.1)

Last updated on MAY 02, 2017

Applies to:

Oracle Net Services - Version to [Release 11.1 to 11.2]
Information in this document applies to any platform.
This document is limited to situations where DRCP or Database Resident Connection Pooling is used with a Firewall in place.
Checked for relevance on 2-MAY-2017


Clients configured to use DRCP, connecting to a RAC cluster through a firewall may experience connection timeouts or failures.  The following error would be returned:

ORA-12170: TNS:Connect timeout occurred

A level 16 Oracle Net client trace shows the following stack:

(3086485728) [29-SEP-2009 08:38:04:300] nioqper: error from nscall
(3086485728) [29-SEP-2009 08:38:04:301] nioqper: ns main err code: 12535
(3086485728) [29-SEP-2009 08:38:04:301] nioqper: ns (2) err code: 12560
(3086485728) [29-SEP-2009 08:38:04:301] nioqper: nt main err code: 505
(3086485728) [29-SEP-2009 08:38:04:301] nioqper: nt (2) err code: 110
(3086485728) [29-SEP-2009 08:38:04:301] nioqper: nt OS err code: 0

These errors are all indicative of a timeout.

TNS-12535 TNS: Operation timed out



This is likely a new implementation of Database Resident Connection Pooling or DRCP.  It may also be the case that a firewall has recently been inserted between DRCP clients and the database server.

Note that since the creation of this document, a new feature has been introduced in version 12.
Please see this document as well:  <NOTE:1333553.1> - 12g: How to Configure DRCP Broker to Use a Specific Listening IP Address


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