问题描述
11.2由于RAC中GRID的分离以及实现了SCAN功能,使得监听的优先级发生了改变。
一个11.2环境的单实例数据库,配置了ASM,随后在同一个服务器上又新建了一个数据库,同样使用这个ASM,但是发现连接这个新的数据库时出现了错误。
[oracle@dbserver1 ~]$ export ORACLE_SID=al32utf8 [oracle@dbserver1 ~]$ sqlplus / AS sysdba SQL*Plus: Release 11.2.0.2.0 Production ON Mon Sep 5 14:04:57 2011 Copyright (c) 1982, 2010, Oracle. ALL rights reserved. Connected TO: Oracle DATABASE 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production WITH the Partitioning, Automatic Storage Management, OLAP, DATA Mining AND REAL Application Testing options SQL> SET pages 100 LINES 120 SQL> SHOW parameter service_names NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ service_names string al32utf8 SQL> conn thams/thams@192.168.20.101/al32utf8 ERROR: ORA-12514: TNS:listener does NOT currently know OF service requested IN CONNECT descriptor Warning: You are no longer connected TO ORACLE.复制
专家解答
用这种简易连接的方式连接这个服务器上第一个创建的数据库实例,没有任何问题。检查监听的状态:
[oracle@dbserver1 ~]$ lsnrctl STATUS LSNRCTL FOR Linux: Version 11.2.0.2.0 - Production ON 05-SEP-2011 17:50:09 Copyright (c) 1991, 2010, Oracle. ALL rights reserved. Connecting TO (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=dbserver1)(PORT=1521))) STATUS OF the LISTENER ------------------------ Alias LISTENER Version TNSLSNR FOR Linux: Version 11.2.0.2.0 - Production START DATE 31-AUG-2011 17:26:15 Uptime 5 days 0 hr. 23 MIN. 53 sec Trace Level off Security ON: LOCAL OS Authentication SNMP OFF Listener Parameter File /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora Listener Log File /u01/app/oracle/diag/tnslsnr/dbserver1/listener/alert/log.xml Listening Endpoints Summary... (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=dbserver1)(PORT=1521))) (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521))) Services Summary... Service "fhacdb1" has 1 instance(s). Instance "fhacdb1", STATUS READY, has 1 handler(s) FOR this service... Service "fhacdbXDB" has 1 instance(s). Instance "fhacdb1", STATUS READY, has 1 handler(s) FOR this service... The command completed successfully复制
可以看到,数据库的监听并没有包含新建的al32utf8的服务,尝试在数据库中进行手工注册操作,错误依旧。
这时想起数据库配置了GRID,切换到grid用户,果然发现了问题所在:
[oracle@dbserver1 ~]$ su - grid Password: [grid@dbserver1 ~]$ lsnrctl STATUS LSNRCTL FOR Linux: Version 11.2.0.2.0 - Production ON 05-SEP-2011 17:50:59 Copyright (c) 1991, 2010, Oracle. ALL rights reserved. Connecting TO (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1522))) STATUS OF the LISTENER ------------------------ Alias LISTENER Version TNSLSNR FOR Linux: Version 11.2.0.2.0 - Production START DATE 04-AUG-2011 16:14:28 Uptime 32 days 1 hr. 36 MIN. 33 sec Trace Level off Security ON: LOCAL OS Authentication SNMP OFF Listener Parameter File /u01/app/grid/product/11.2.0/gridhome_1/network/admin/listener.ora Listener Log File /u01/app/grid/diag/tnslsnr/dbserver1/listener/alert/log.xml Listening Endpoints Summary... (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1522))) (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=dbserver1)(PORT=1522))) Services Summary... Service "+ASM" has 1 instance(s). Instance "+ASM", STATUS READY, has 1 handler(s) FOR this service... Service "al32utf8" has 1 instance(s). Instance "al32utf8", STATUS READY, has 1 handler(s) FOR this service... Service "al32utf8XDB" has 1 instance(s). Instance "al32utf8", STATUS READY, has 1 handler(s) FOR this service... The command completed successfully [grid@dbserver1 ~]$ exit logout [oracle@dbserver1 ~]$ sqlplus /nolog SQL*Plus: Release 11.2.0.2.0 Production ON Mon Sep 5 17:51:20 2011 Copyright (c) 1982, 2010, Oracle. ALL rights reserved. SQL> conn thams/thams@192.168.20.101:1522/al32utf8 Connected. SQL> SELECT name FROM v$database; NAME --------- AL32UTF8 SQL> SELECT instance_name FROM v$instance; INSTANCE_NAME ---------------- al32utf8复制
原来新建的数据库实例注册到grid用户下的监听上了。之所以和另外一个数据库不同,是因为那个数据库是在grid安装之前,因此数据库使用ORACLE_HOME本身的监听。而一旦配置了grid,则grid用户下的监听启动,而Oracle的优先级显然是先找grid下的监听,然后再去考虑ORACLE_HOME下的监听。
当然,对于没有使用grid的情况下,11.2的监听和之前的版本没有什么区别。
「喜欢这篇文章,您的关注和赞赏是给作者最好的鼓励」
关注作者
【版权声明】本文为墨天轮用户原创内容,转载时必须标注文章的来源(墨天轮),文章链接,文章作者等基本信息,否则作者和墨天轮有权追究责任。如果您发现墨天轮中有涉嫌抄袭或者侵权的内容,欢迎发送邮件至:contact@modb.pro进行举报,并提供相关证据,一经查实,墨天轮将立刻删除相关内容。
评论
相关阅读
【纯干货】Oracle 19C RU 19.27 发布,如何快速升级和安装?
Lucifer三思而后行
707次阅读
2025-04-18 14:18:38
Oracle RAC 一键安装翻车?手把手教你如何排错!
Lucifer三思而后行
636次阅读
2025-04-15 17:24:06
Oracle数据库一键巡检并生成HTML结果,免费脚本速来下载!
陈举超
548次阅读
2025-04-20 10:07:02
【活动】分享你的压箱底干货文档,三篇解锁进阶奖励!
墨天轮编辑部
495次阅读
2025-04-17 17:02:24
【ORACLE】记录一些ORACLE的merge into语句的BUG
DarkAthena
490次阅读
2025-04-22 00:20:37
【ORACLE】你以为的真的是你以为的么?--ORA-38104: Columns referenced in the ON Clause cannot be updated
DarkAthena
488次阅读
2025-04-22 00:13:51
一页概览:Oracle GoldenGate
甲骨文云技术
471次阅读
2025-04-30 12:17:56
火焰图--分析复杂SQL执行计划的利器
听见风的声音
419次阅读
2025-04-17 09:30:30
3月“墨力原创作者计划”获奖名单公布
墨天轮编辑部
373次阅读
2025-04-15 14:48:05
OR+DBLINK的关联SQL优化思路
布衣
360次阅读
2025-05-05 19:28:36
TA的专栏
Java中间件
收录0篇内容
热门文章
一次Connection reset by peer的问题排查
2021-12-07 34208浏览
Java8-Stream: no instance(s) of type variable(s) R exist so that void conforms to R
2021-02-19 32441浏览
nginx: [emerg] "user" directive is not allowed here in /etc/nginx/conf.d/nginx.conf:1
2022-02-15 24332浏览
ORA-00904: "POLTYP": invalid identifier
2019-06-19 12945浏览
PageHelper排坑,处理排序失败: net.sf.jsqlparser.JSQLParserException
2022-05-19 12840浏览