一次ORACLE RAC中连接ScanIP报错ORA-12545的问题解决

最新推荐文章于 2022-05-13 17:02:11 发布

久违的太阳

最新推荐文章于 2022-05-13 17:02:11 发布

阅读量1.2k

点赞数

分类专栏： oracle troubleshoting 文章标签： ORA-12545 local_listener

本文链接：https://blog.csdn.net/su377486/article/details/108016126

版权

oracle troubleshoting 专栏收录该内容

45 篇文章 3 订阅

订阅专栏

客户的RAC的一个节点挂了之后,手工重启,所有资源都恢复正常,本地同网络连接正常,但是下面的其它网络客户端连接scanIP报错

ORA-12545: 因目标主机或对象不存在, 连接失败

C:\Users\Administrator>sqlplus system/manager@172.16.80.24/dbserver

SQL*Plus: Release 10.2.0.1.0 - Production on 星期五 8月 14 23:57:53 2020

Copyright (c) 1982, 2005, Oracle. All rights reserved.

ERROR:
ORA-12545: 因目标主机或对象不存在, 连接失败

这里的原因是节点的LOCAL_LISTENER参数不知道被谁设置为了空.在RAC中,每个节点的LOCAL_LISTENER参数必须指定本节点的vip,remote_listener必须指向scanIP.

MOS的相关文档如下:

ORA-12545 or ORA-12537 While Connecting to RAC Through SCAN name (Doc ID 970619.1)

In this Document

Scalability RAC Community

References

APPLIES TO:

Oracle Database Configuration Assistant - Version 11.2.0.1 and later
Oracle Net Services - Version 11.2.0.4 to 11.2.0.4 [Release 11.2]
Information in this document applies to any platform.
***Checked for relevance on 11-Mar-2013***

SYMPTOMS

Error ORA-12545 or ORA-12537 reported while trying to connect to 11gR2 Real Application Cluster (RAC) database through SCAN name

CHANGES

CAUSE

Client is able to resolve all Fully Qualified Domain Name (FQDN) SCAN and VIP name but not short ones(without domain name) as its in different domain; even though FQDN names were specified during Grid Infrastructure setup, due to bug 9150053 by default DBCA set database parameter local_listener to short node VIP name while database is created.

In following example, eotcs.us.oracle.com is SCAN name and eyrac1fv.us.oracle.com is one of the node VIP name, on client machine:

ping -c 1 <node1>.oracle.com
PING eotcs.us.oracle.com (120.x.x.207) 56(84) bytes of data.
64 bytes from 120.x.x.207: icmp_seq=1 ttl=64 time=0.034 ms

ping -c 1 ping <node1>
ping: unknown host <node1>

ping -c 1 <scan>.oracle.com
PING <scan>.oracle.com (120.x.x.211) 56(84) bytes of data.
64 bytes from 120.x.x.211: icmp_seq=1 ttl=64 time=0.034 ms

ping -c 1 ping <scan>
ping: unknown host <scan>

SOLUTION

bug 9150053 will be fixed in 11.2.0.2 and above, though easy workaround is available:

1. Database level setting:

Modify pfile/spfile parameter local_listener to use FQDN VIP name or VIP.

SQL> alter system set local_listener='(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=<scan>.oracle.com)(PORT=1521))))' sid='<SID1>';

Or

SQL> alter system set local_listener='(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=120.x.x.211)(PORT=1521))))' sid='<SID1>';

And register with listener:

SQL> alter system register;

2. Per client setting:

Specify FQDN SCAN name in client tnsnames.ora and add all node VIP name/IP pairs to hosts file:

grep <scan> /etc/hosts
120.x.x.211 <scan>.oracle.com scan

Or set search domain: in /etc/resolv.conf on Linux/Unix or "Append DNS suffixes" on Windows

Linux/Unix:

grep search /etc/resolv.conf
search us.oracle.com

Windows:

Network Connection => Property for Public Network => Internet Protocol (TCP/IP) => Advanced => DNS => Append these DNS suffices (in order)

Scalability RAC Community

To discuss this topic further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the My Oracle Support Scalability RAC Community.

REFERENCES

BUG:9150053 - ORA-12545 REPORTED WHILE CONNECTING TO 11.2 SCAN ON CLIENT
NOTE:975457.1 - How to Troubleshoot Connectivity Issue with 11gR2 SCAN Name
NOTE:364855.1 - Client Connection to RAC Intermittently Fails-ORA-12545 TNS: Host or Object Does not Exist
NOTE:553328.1 - Troubleshooting Guide for ORA-12545 / TNS-12545 Connect failed because target host or object does not exist
NOTE:291175.1 - Clients Failing to Connect Due to Intermittent ORA-12545 in RAC Environment