Common listener-related errors in ALERT logs 3: troubleshooting of ORA-609 TNS-12537 and TNS-12547 or TNS-12170 TNS-12535 errors, ora-609tns-12535

Source: Internet
Author: User

Common listener-related errors in ALERT logs 3: troubleshooting of ORA-609 TNS-12537 and TNS-12547 or TNS-12170 TNS-12535 errors, ora-609tns-12535
In the ALERT Log in 1.11G, the error ORA-609 TNS-12537 and TNS-12547 or TNS-12170 12170, 'tns-12535 and other problems are solved:
Troubleshooting Guide for TNS-12535 or ORA-12535 or ORA-12170 Errors (Document ID 119706.1)
TNS-12535/ORA-12535 on Connection to Database (Documentation ID 214122.1)
11g: ORA-609 TNS-12537 and TNS-12547 or TNS-12170 in 11g Alert. log (Document ID 1116960.1)
Fatal NI Connect Error 12170, 'tns-12535: TNS: operation timed out 'reported in 11g Alert Log (Document ID 1286376.1)

TNS-12535 or ORA-12535 is essentially a problem of timing between the client and the server. A timing issue between the client and server.
This error usually occurs when the firewall or network is unstable or slow. It may also be caused by tcp queuesize setting settings on the host.
You also need to check the Listener Configuration file:
Listener. ora -->
CONNECT_TIMEOUT _ <listener_name> (8.1.x and lower only)
Or
INBOUND_CONNECT_TIMEOUT _ <listener_name> (9.2 and above)
Sqlnet. ora -->
SQLNET. INBOUND_CONNECT_TIMEOUT (9.2 and up ).


Listener. ora: INBOUND_CONNECT_TIMEOUT_listenername
Set to a value in seconds and determines how long a client has to provide the necessary authentication information to a database.
The Unit is seconds. The client must submit the required authentication information within the specified time.
Sqlnet. ora: SQLNET. INBOUND_CONNECT_TIMEOUT
INBOUND_CONNECT_TIMEOUT_listenername is set to a value in seconds and determines how long a client has to complete its connect request to the listener after the network connection has been established.
The Unit is seconds. How long does it take to complete the connection request after the client establishes a connection with the listener?
For example:
Sqlnet. ora: SQLNET. INBOUND_CONNECT_TIMEOUT = 180
Listener. ora: INBOUND_CONNECT_TIMEOUT_listener_name = 120
Reference: 11g: ORA-609 TNS-12537 and TNS-12547 or TNS-12170 in 11g Alert. log (Document ID 1116960.1)



Troubleshooting:
1. You can PING the HOST in the connection string, for example, rac vip/SCAN, and check firewall, route, and network slowness.
2. the OS platform and version of the client and server are supported by ORACLE.
3. If 9I or the Oracle Names Server is used, configure temporary tnsnames. ora and write NAMES. DIRECTORY_PATH = (TNSNAMES) in sqlnet. ora file)
4. If you are using Shared Server, try to use SERVER = DEDICATED
5. Check for high database server load and CPU/memory
6.10.1, 10.2 clients may receive a ORA-12535 or ORA-12170 when the network is slow, as follows:
These parameters are set on the SERVER side:
Listener. ora: INBOUND_CONNECT_TIMEOUT_listenername -- 0 (indefinite)
Sqlnet. ora: SQLNET. INBOUND_CONNECT_TIMEOUT -- 120 anti-DOS
7.11g Database Alert logs may also contain combinations of 12535 and/or 12170 errors.
Check whether the client issues excessive connections and connection storms.
8. Large listener load, a large number of client connections backlog, the listener cannot be processed in a timely manner. -- Or connection storm
9. The server is starting ..
10. trace doc: Document ID 1116960.1



Solution:
In 1.8I and earlier versions, configure CONNECT_TIMEOUT _ <listener_name> and make it a higher value in listener. ora.
2.9I and later versions, CONNECT_TIMEOUT _ <listener_name> parameter is obsoleted.
It must be set according to different versions.

3.11G, this error will appear in the ALERT Log. This error has basically no impact on the application and can be ignored.
ORACLE gave a penalty to prevent the listener timeout error from appearing in the alarm LOG, and stored it in the LOG of the listener in the form of 10 Gb ..
Fatal NI Connect Error 12170, 'tns-12535: TNS: operation timed out 'reported in 11g Alert Log (Document ID 1286376.1)
Method 1: server's sqlnet. ora:
DIAG_ADR_ENABLED = OFF
Method 2:
Also, to back out the ADR diag for the Listener component, server's listener. ora:
DIAG_ADR_ENABLED_LISTENER = OFF
At this time, the listener timeout error only appears in the listener log. Note that ADR_BASE_LISTENER =/orabase -- deletes this entry.
Modification to the sqlnet file takes effect only after the listener is registered again.


In 4.11G, you can also set sqlnet. ora -- Document ID 1628949.1
SQLNET. EXPIRE_TIME = n Where <n> is a non-zero value set in minutes.

Copyright Disclaimer: This article is an original article by the blogger and cannot be reproduced without the permission of the blogger.

Related Article

E-Commerce Solutions

Leverage the same tools powering the Alibaba Ecosystem

Learn more >

Apsara Conference 2019

The Rise of Data Intelligence, September 25th - 27th, Hangzhou, China

Learn more >

Alibaba Cloud Free Trial

Learn and experience the power of Alibaba Cloud with a free trial worth $300-1200 USD

Learn more >

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.