Oracle prompt alert Log errors:12170 tns-12535/tns-00505:operation Timed out

Customer feedback system frequently reported session timeout, causing application test to not work properly, check alert log to discover
Fatal NI Connect error 12170.

VERSION Information:
TNS for Hpux:version 11.2.0.4.0-production
Oracle bequeath NT Protocol Adapter for Hpux:version 11.2.0.4.0-production
TCP/IP NT Protocol Adapter for Hpux:version 11.2.0.4.0-production
time:29-sep-2014 20:42:56
Tracing not turned on.
Tns error struct:
NS Main ERR code:12535

Tns-12535:tns:operation timed out
NS Secondary Err code:12560
NT Main ERR code:505

Tns-00505:operation timed out
NT Secondary Err code:238
NT OS Err code:0
Client Address: (address= (PROTOCOL=TCP) (host=10.78.199.47) (port=55447))
Mon Sep 29 20:42:56 2014
Although most websites or MOS descriptions, Fatal NI connect error 12,170 is considered using the configuration as follows configuration
# #调整listener. Ora
VI $ORACLE _home/network/admin/listener.ora
Increase:
Diag_adr_enabled_listener=off
inbound_connect_timeout_listener=180

# #调整sqlnet. Ora
VI $ORACLE _home/network/admin/sqlnet.ora
Increase:
Diag_adr_enabled=off
Sqlnet. inbound_connect_timeout=180
These have been configured, but now reported 12170 TNS-12535 TNS-00505 error, by combining MOS discovery, this problem may be due to the application server and the database server firewall policy settings are not suitable for business query requirements, Application Server and Database server firewall timeout (for example, the application server initiates a large query, executes in the database server, has not returned the result, but the network has timed out, terminating the session)
Supplementary knowledge points
The ' NT Secondary ERR code ' identifies the underlying network transport, such as (TCP/IP) timeout limit.
In the identifies Windows underlying transport layer.

The "NT Secondary Err Code" is different based on the operating system:

Linux x86 or Linux x86-64: "NT Secondary err code:110"
HP-UX: "NT Secondary err code:238"
AIX: "NT Secondary err code:78"
Solaris: "NT Secondary err code:145"


The Alert.log message indicates that a connection is terminated after it is established to the instance.
In this case, it is terminated 2 hours and 3 minutes after the listener handed the connection to the database.

This would indicate the issue with a firewall where a maximum idle the time setting be in place.

The connection would not necessarily is "idle". This issue can arise during a long running query
or when using JDBC Thin connection pooling. If There is no data ' in the wire ' for lengthy

Periods of time for any reason, the firewall might terminate the connection.
Solution
The Non-oracle solution would is to or increase the firewall setting for maximum.
In cases where's not feasible, Oracle offers the following suggestion:

The following parameter, set at the **rdbms_home/network/admin/sqlnet.ora, can resolve this kind of problem.
DCD or Sqlnet. Expire_time can mimic data transmission between the server and the client during long periods of idle time.

Sqlnet. Expire_time=n Where <n> is a Non-zero value set in minutes.

The Following:note 257650.1 resolving Problems with Connection Idle Timeout with Firewall
Of course, in addition to the following database to solve, but also in the network firewall level, such as increasing network idle termination time, etc.

Specific reference: Alert Log errors:12170 tns-12535/tns-00505:operation Timed out (Doc ID 1628949.1)
Fatal NI Connect Error 12170, ' tns-12535:tns:operation timed out ' reported in 11g Alert Log (Doc ID 1286376.1)

Contact: Mobile Phone (13429648788) QQ (107644445)
Link:http://www.xifenfei.com/5529.html