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

最新推荐文章于 2023-12-07 17:47:25 发布

原创

最新推荐文章于 2023-12-07 17:47:25 发布 · 1.5k 阅读

标签

#ORA-12545 #local_listener

本文详细解析了在Oracle RAC环境中遇到ORA-12545错误的原因及解决方案，指出LOCAL_LISTENER参数设置不当是常见原因，并提供了修改参数及注册监听器的具体步骤。

客户的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 <

最低0.47元/天解锁文章