Alert logs common monitoring related error three: ORA-609 TNS-12537 and TNS-12547 or TNS-12170 TNS-12535 troubleshooting

Source: Internet
Author: User

1.11G Alert Log Error ORA-609 TNS-12537 and TNS-12547 or TNS-12170 12170, ' TNS-12535, and other solutions to problems:
Troubleshooting guide for TNS-12535 or ORA-12535 or ORA-12170 Errors (document ID 119706.1)
tns-12535/ora-12535 on Connection to Database (document 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 matter of timing between the client and the server. A timing issue between the client and server.
This error is usually due to a firewall or network instability, slow timeout. It may also be the host's TCP queuesize setting setup issue.
You usually also need to troubleshoot the listening 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 have to provide the necessary authentication information to a DA Tabase.
The unit is seconds, and the client needs to submit the required authentication information within the specified time.
Sqlnet.ora:SQLNET. Inbound_connect_timeout
Inbound_connect_timeout_listenername is set to a value of seconds and determines how long a client have to complete its con Nect request to the listener after the network connection have been established.
The unit is seconds, and how long the client needs to complete the connection request after establishing 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)



How to Troubleshoot:
1. Can ping the host host--in the connection string, such as RAC Vip/scan, check firewall, routing, network slow, etc.
2. The OS platform and version of the client and server is supported by Oracle
3. If you are using 9I or previous Oracle Names Server, configure the temporary Tnsnames.ora and write Names in Sqlnet.ora file. Directory_path = (tnsnames)
4. If you are using a shared Server, try to use the server=dedicated
5. High database server load, cpu/memory and other checks
6.10.1, version 10.2 clients may receive ORA-12535 or ORA-12170 when the network is slow, modified as follows:
These parameters is set on the SERVER side:
Listener.ora:INBOUND_CONNECT_TIMEOUT_listenername--for 0 (indefinite)
Sqlnet.ora:SQLNET. Inbound_connect_timeout--120 anti-dos
The database alert log for version 7.11g may also contain a combination of 12535 and/or 12170 errors.
Troubleshoot problems such as excessive connections, connection storms, and so on.
8. Listener load is large, a large number of client connections backlog, the listener can not be processed in time. --or connect the storm
9. The server is in the process of booting:
10.TRACE Trace DOC: Document ID 1116960.1



Workaround:
1.8I and previous versions, configure connect_timeout_<listener_name> and make it a higher value in Listener.ora.
2.9I and later version,connect_timeout_<listener_name> parameter is obsoleted.
It needs to be set according to different versions.

This error will appear in the alert log in 3.11G. This error has no effect on the application, and can usually be ignored.
Oracle has given a damage trick to not let the listener timeout error in the alarm log, back to the 10G form saved in the log of the listener.
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 of the ADR diag for the Listener component, server ' s Listener.ora:
Diag_adr_enabled_listener = OFF
At this point, a listening timeout error appears only in the listening log, note Adr_base_listener =/orabase--delete this entry.
Changes to the Sqlnet file are re-registered for monitoring to take effect.


sqlnet.ora--document ID 1628949.1 can also be set in 4.11G
Sqlnet. Expire_time=n Where <n> is a Non-zero the value set in minutes.

Copyright NOTICE: This article for Bo Master original article, without Bo Master permission not reproduced.

Alert logs common monitoring related error three: ORA-609 TNS-12537 and TNS-12547 or TNS-12170 TNS-12535 troubleshooting

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.