Shulou(Shulou.com)05/31 Report--

This article mainly explains "how to solve the failure of connecting to the database through scanip". Interested friends may wish to have a look. The method introduced in this paper is simple, fast and practical. Next, let the editor take you to learn how to solve the failure of connecting to the database through scanip.

Checked the cluster status and monitoring logs, and did not see any anomalies. It is said that it was normal before, but if you find an exception today, log in to * * ora-12537connection closed using plsql developer, and log in normally using other ip.

There are other instances on the library, and there is no problem logging in using scanip, indicating that there is still a problem with the configuration of this library.

It is said on the Internet that configuring the local_listener parameter can solve this problem; after checking that the local_listener of the library is empty, the parameter of other instances is configured with vip information.

Node 1:

Alter system set local_listener=' (DESCRIPTION= (ADDRESS_LIST= (ADDRESS= (PROTOCOL=TCP) (HOST=172.16.32.23) (PORT=1521) 'scope=both sid='hhtrep1'

Alter system register

Node 2:

Alter system set local_listener=' (DESCRIPTION= (ADDRESS_LIST= (ADDRESS= (PROTOCOL=TCP) (HOST=172.16.32.24) (PORT=1521) 'scope=both sid='hhtrep2'

Alter system register

The problem is solved, but why local_listener affects scanip connections, you still need to query the documents yourself.

At this point, I believe you have a deeper understanding of "how to solve the failure of connecting to the database through scanip". You might as well do it in practice. Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!

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.