Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

Causes and Solutions of TNS-12535 TNS-00505 reported in 11gr2 alert Log

2025-01-16 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Database >

Share

Shulou(Shulou.com)06/01 Report--

11GR2 RAC was newly installed before. During the inspection one day, the following error was found in the alert log:

Fatal NI connect error 12170.

VERSION INFORMATION:

TNS for Solaris: Version 11.2.0.3.0-Production

Oracle Bequeath NT Protocol Adapter for Solaris: Version 11.2.0.3.0-Production

TCP/IP NT Protocol Adapter for Solaris: Version 11.2.0.3.0-Production

Time: 16-MAY-2013 04:57:41

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: 145

Nt OS err code: 0

Client address: (ADDRESS= (PROTOCOL=tcp) (HOST=171.17.108.18) (PORT=55532))

Thu May 16 04:58:27 2013

Trigger reason:

It is due to the timeout caused by the abnormal disconnection of the program. If 11g R1 has the above error message, it will be written to sqlnet.log,11g R2 and written to alert.log.

In fact, this error is a normal phenomenon.

If you analyze the reasons for these errors at a deeper level, the details are as follows:

The whole step of a client connection:

1. The client initiates a connection connection listening

2. Listen to start a dedicated process (the server process, that is, the LOCA=NO process) to receive the connection

3. After the exclusive process is started, the listener will pass the connection to the exclusive process

4. The dedicated process shakes hands with the client through this connection

5. The information exchange between the exclusive process and the client needs to establish a session

6. Open session

When the client is closed in steps 3 to 4 above, the error we see will be reported when the exclusive process tries to contact the client and finds that the connection has been closed!

If you do not want this information to be printed in the alert log, set it as follows:

Set up in sqlnet.ora

DIAG_ADR_ENABLED = OFF

Set up in listener.ora

DIAG_ADR_ENABLED_ = OFF

Restart monitoring

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Database

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report