11g生产环境监听日志告警问题处理-Subscription?for

1、系统报错
Command:?failed????????stdout:?yes???????????stderr:?no
Before?command?completion,?additional?instructions?may?appear?below.
Initializing?mkcd?log:?/var/adm/ras/mkcd.log...
Verifying?command?parameters...
Creating?image.data?file...
Creating?mksysb?image...
Creating?list?of?files?to?back?up.
.
Backing?up?143824?files..............................
7293?of?143824?files?(5%)..............
0512-005?mksysb:?Backup?Completed.
????????The?backup?command?completed?with?errors.
????????The?messages?displayed?on?Standard?Error?contained?additional
????????information.
cp:?/BACKUPXXaaa_JarMa:?There?is?not?enough?space?in?the?file?system.
backup:?0511-086?Cannot?copy?./opt/oracle/diag/tnslsnr/HISMNG/listener/trace/listener.log?to?a?temporary?location.
backup:?0511-084?An?internal?packing?error?occurred:?incorrect?size
backup:?0511-442?./opt/oracle/diag/tnslsnr/HISMNG/listener/trace/listener.log?will?not?be?backed?up.
ls:?0653-341?The?file?/nas/sysbackup/hismng/mksysb_17957188?does?not?exist.
Populating?the?CD?or?DVD?file?system...
Copying?backup?to?the?CD?or?DVD?file?system...
copy_backup[46]:??total_size?=?fs_size?+?BACKUP_SIZE?+?boot_image_size?+?EFI_PARTITION_SIZE?+?PADDING_128K?:?0403-009?The?sp
ecified?number?is?not?valid?for?this?command.

2、查看监听日志
HISMNG:/opt/oracle/diag/tnslsnr/HISMNG/listener/trace$?tail?-f?listener.log
04-APR-2018?09:10:32?*?(CONNECT_DATA=(CID=(PROGRAM=)(HOST=HISMNG)(USER=oracle))(COMMAND=status)(ARGUMENTS=64)(SERVICE=LISTENER)(VERSION=186647296))?*?status?*?0
04-APR-2018?09:10:32?*?service_register?*?LsnrAgt?*?1195
TNS-01195:?Listener?rejected?registration?of?endpoint?"(ADDRESS=(PROTOCOL=TCP)(HOST=xxxxxxxxxxxxxxx)(PORT=1521)(IP=FIRST))"
WARNING:?Subscription?for?node?down?event?still?pending
04-APR-2018?09:10:33?*?(CONNECT_DATA=(CID=(PROGRAM=)(HOST=HISMNG)(USER=oracle))(COMMAND=status)(ARGUMENTS=64)(SERVICE=LISTENER)(VERSION=186647296))?*?status?*?0
Wed?Apr?04?09:10:53?2018
04-APR-2018?09:10:53?*?service_register?*?mgrdb?*?0
04-APR-2018?09:10:53?*?service_register?*?hisdb?*?0
04-APR-2018?09:10:57?*?service_register?*?+ASM?*?0
04-APR-2018?09:10:59?*?service_update?*?mgrdb?*?0
Wed?Apr?04?09:11:33?2018
WARNING:?Subscription?for?node?down?event?still?pending

3、查看官方文档
WARNING: Subscription for node down event still pending in Listener Log (文档 ID 372959.1)
官方建议关闭到这个feature
These messages are related to the Oracle TNS Listener‘s default subscription to the Oracle Notification Service (ONS). In a non-RAC environment it is recommended to disable this subscription.?? This feature was introduced in Oracle 10g.

4、处理过程
使用grid用户,在listener.ora配置文件中添加一行SUBSCRIBE_FOR_NODE_DOWN_EVENT_LISTENER=OFF
然后reload监听,使配置文件生效。
lsnrctl reload listener
HISMNG:/opt/oracle/diag/tnslsnr/HISMNG/listener/trace$?vi?/opt/oracle/product/11203/db/network/admin/listener.ora
"/opt/oracle/product/11203/db/network/admin/listener.ora"?13?lines,?356?characters?
#?listener.ora?Network?Configuration?File:?/opt/oracle/product/11203/db/network/admin/listener.ora
#?Generated?by?Oracle?configuration?tools.
LISTENER?=
??(DESCRIPTION_LIST?=
????(DESCRIPTION?=
??????(ADDRESS?=?(PROTOCOL?=?IPC)(KEY?=?EXTPROC1521))
??????(ADDRESS?=?(PROTOCOL?=?TCP)(HOST?=?hmboot)(PORT?=?1521))
????)
??)
ADR_BASE_LISTENER?=?/opt/oracle
SUBSCRIBE_FOR_NODE_DOWN_EVENT_LISTENER=OFF???#line?added?by?manual
保存退出!

5、查看监听日志文件
再次查看监听日志文件,发现告警已经不再产生,问题得以解决。
HISMNG:/opt/oracle/diag/tnslsnr/HISMNG/listener/trace$?tail?-f?listener.log
Trace?level?is?currently?0
Log?messages?written?to?/opt/oracle/diag/tnslsnr/HISMNG/listener/alert/log.xml
04-APR-2018?09:20:28?*?(CONNECT_DATA=(CID=(PROGRAM=)(HOST=HISMNG)(USER=oracle))(COMMAND=reload)(ARGUMENTS=64)(SERVICE=listener)(VERSION=186647296))?*?reload?*?0
04-APR-2018?09:20:30?*?service_register?*?mgrdb?*?0
04-APR-2018?09:20:30?*?service_register?*?hisdb?*?0
04-APR-2018?09:20:30?*?service_register?*?+ASM?*?0
04-APR-2018?09:20:38?*?service_update?*?mgrdb?*?0
Wed?Apr?04?09:20:38?2018
04-APR-2018?09:20:38?*?service_update?*?hisdb?*?0
04-APR-2018?09:20:47?*?service_update?*?hisdb?*?0
Wed?Apr?04?09:20:59?2018
04-APR-2018?09:20:59?*?service_update?*?hisdb?*?0
04-APR-2018?09:21:02?*?(CONNECT_DATA=(CID=(PROGRAM=)(HOST=HISMNG)(USER=oracle))(COMMAND=status)(ARGUMENTS=64)(SERVICE=LISTENER)(VERSION=186647296))?*?status?*?0
Wed?Apr?04?09:21:38?2018
04-APR-2018?09:21:38?*?service_update?*?hisdb?*?0
Wed?Apr?04?09:22:02?2018
04-APR-2018?09:22:02?*?(CONNECT_DATA=(CID=(PROGRAM=)(HOST=HISMNG)(USER=oracle))(COMMAND=status)(ARGUMENTS=64)(SERVICE=LISTENER)(VERSION=186647296))?*?status?*?0
04-APR-2018?09:22:08?*?service_update?*?hisdb?*?0
Wed?Apr?04?09:22:52?2018
04-APR-2018?09:22:52?*?(CONNECT_DATA=(SID=hisdb)(CID=(PROGRAM=JDBC?Thin?Client)(HOST=__jdbc__)(USER=root)))?*?(ADDRESS=(PROTOCOL=tcp)(HOST=172.16.125.2)(PORT=64960))?*?establish?*?hisdb?*?0
04-APR-2018?09:22:59?*?service_update?*?hisdb?*?0
04-APR-2018?09:23:02?*?(CONNECT_DATA=(CID=(PROGRAM=)(HOST=HISMNG)(USER=oracle))(COMMAND=status)(ARGUMENTS=64)(SERVICE=LISTENER)(VERSION=186647296))?*?status?*?0

原文地址:http://blog.51cto.com/roidba/2094585

时间: 2024-11-09 01:30:18

11g生产环境监听日志告警问题处理-Subscription?for的相关文章

Oracle 11g 监听很慢,由于监听日志文件太大引起的问题(Windows 下)

现象:Windows 操作系统的Oracle 数据库,使用sqlplus 连接(不指定实例名)连接很快,程序连接或使用连接工具或在Net Manager 中测试连接都需要花费约三四十秒的时间(程序连接可能失败). 通过tsping localhost 测试,亦花费三四十秒. 查看监听警告日志(所在位置在文章后面介绍),有信息如下: <msg time='2017-05-16T16:57:51.811+08:00' org_id='oracle' comp_id='tnslsnr' type='U

『ORACLE』 清理监听日志(11g)

停止监听服务进程(tnslsnr)记录日志.lsnrctl  set log_status off; 将监听日志文件(listener.log)复制一份,以listener.log.yyyymmdd格式命名cp listener.log listener.log.20170521 将监听日志文件(listener.log)清空. cat /dev/null > listener.log 开启监听服务进程(tnslsnr)记录日志lsnrctl set log_status on; 对于这种lis

ORACLE清理、截断监听日志文件(listener.log)

在ORACLE数据库中,如果不对监听日志文件(listener.log)进行截断,那么监听日志文件(listener.log)会变得越来越大,想必不少人听说过关于"LISTENER.LOG日志大小不能超过2GB,超过会导致LISTENER监听器无法处理新的连接",当然这个不是真理,不会绝对出现,只是发生在老旧的32bit Linux或Unix系统下面,真实的原因是一些32bit OS自带的文件系统不支持2GB以上的文件,导致监听服务进程(tnslsnr)append write日志文件

有关监听日志的清理问题

近日,有开发人员向我反馈:“代码时有连不上数据库的情况发生”.在了解了一些基本信息之后,希望能通过查看监听日志获取问题线索.首先是通过如下方式确定监听日志的存放路径: LSNRCTL for Linux: Version 10.2.0.4.0 - Production on 21-JUN-2016 21:19:56 Copyright (c) 1991, 2007, Oracle. All rights reserved. Connecting to (ADDRESS=(PROTOCOL=tcp

我所不知道的的监听日志问题

今天,有开发人员向我反馈:“代码时有连不上数据库的情况发生”.在了解了一些基本情况之后,希望能通过查看监听日志获取问题线索.首先是通过如下方式确定监听日志的存放路径: LSNRCTL for Linux: Version 10.2.0.4.0 - Production on 21-JUN-2016 21:19:56 Copyright (c) 1991, 2007, Oracle. All rights reserved. Connecting to (ADDRESS=(PROTOCOL=tcp

Oracle 11g ORA-12514:TNS:监听程序当前无法识别连接描述符中请求的服务

最近在装ORACLE的时候爆出了一个问题, Oracle 11g ORA-12514:TNS:监听程序当前无法识别连接描述符中请求的服务 以前装ORACLE好多遍了网上搜了好多方法还是解决不了,最后通过自己的摸索找到了一个不显眼的原因, 打开Oracle - OraDb11g_home1/配置和移植工具/  下面的Net Manager,配置好服务名后,打开监听程序右上角选择数据库服务 一开始的数据库服务中配置是有问题的,一般一开始这个目录是空的需要自己手动添加更改,如下图一开始我的Net Ma

oracle 登录数据库时报 无监听 的一种解决方式(监听日志文件达到4g默认上限)

问题:登录服务器时 报无监听服务 检查步骤: 1.进入sqlplus查看数据库的状态,显示当前数据库的状态为OPEN 脚本:select status from v$Instance; 2.检查数据库的监听服务,登录的时候发现进入监听程序的速度非常慢 脚本:lsnrctl status 3.查看监听日志的大小,位置如下: $ORACLE_BASE\diag\tnslsnr\<hostname>\listener\trace\ 5.重启启动监听即可: lsnrctl stop  停止 lsnrc

Shell: extract more from listener.log (分析oracle监听日志)

最近遇到了两起数据库连接数不足的问题, 通常都会预留一些会话增加的情况, 但在一些特殊情况下如连接风暴(logon storm), 如果在监听中没有做rate限流,对数据库来说巨大的冲击可能会导致数据库Hang 或 ora-20 或ora-18 错误. 对于Hang并伴有进程数不足的情况,AWR.ASH 都可能无法升成,甚至数据库都无法登录或做SSD 都不成功, 这时候LISTENER.LOG 就成了"破案"时关键的线索. 下面记录分享一些分析listener.log的一些脚本.(No

oracle 11g 修改默认监听端口1521

OS: Oracle Linux Server release 5.7 DB: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production 1.查看监听状态: SQL> !lsnrctl status LSNRCTL for Linux: Version 11.2.0.3.0 - Production on 12-NOV-2013 01:36:29 Copyright (c) 1991, 2011, O