WARNING: Subscription for node down event still pending

发表于 2012 年 11 月 26 日 由 惜分飞

联系：手机/微信(+86 17813235971) QQ(107644445)QQ咨询惜分飞

标题：WARNING: Subscription for node down event still pending

作者：惜分飞©版权所有[未经本人同意,不得以任何形式转载,否则有进一步追究法律责任的权利.]

监听日志中出现很多”WARNING: Subscription for node down event still pending”警告

--监听日志中内容
……
26-NOV-2012 09:35:48 * ping * 0
WARNING: Subscription for node down event still pending
……
26-NOV-2012 09:45:49 * ping * 0
WARNING: Subscription for node down event still pending
……

--监听日志大小
$ ls -l /oracle/product/10g/network/log/listener.log
-rw-r-----    1 oracle   dba       229526148 Nov 26 14:20 /oracle/product/10g/network/log/listener.log

--总计条数
$ grep "Subscription for node down event still pending" \
> /oracle/product/10g/network/log/listener.log|wc -l
   77306

数据库版本和平台

SQL> select * from v$version;

BANNER
----------------------------------------------------------------
Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bi
PL/SQL Release 10.2.0.5.0 - Production
CORE    10.2.0.5.0      Production
TNS for IBM/AIX RISC System/6000: Version 10.2.0.5.0 - Productio
NLSRTL Version 10.2.0.5.0 - Production

监听日志配置

$ more /oracle/product/10g/network/admin/listener.ora
SID_LIST_LISTENER =
  (SID_LIST =
    (SID_DESC =
      (SID_NAME = PLSExtProc)
      (ORACLE_HOME = /oracle/product/10g)
      (PROGRAM = extproc)
    )
  )

LISTENER =
  (DESCRIPTION_LIST =
    (DESCRIPTION =
      (ADDRESS = (PROTOCOL = TCP)(HOST = xifenfei)(PORT = 1521))
      (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0))
    )
  )

解决方法

--监听文件中增加
SUBSCRIBE_FOR_NODE_DOWN_EVENT_<listener_name>=OFF

--reload监听
lsnrctl reload

补充说明

SUBSCRIBE_FOR_NODE_DOWN_EVENT_<listener_name>=OFF will prevent the messages 
from being written to the log file and may also prevent the TNS Listener from hanging periodically. 

Setting SUBSCRIBE_FOR_NODE_DOWN_<listener_name> to OFF disables 
a necessary RAC functionality(Oracle Notification Service[ONS],fast application notification[FAN]). 
The above workaround is recommended only for non-RAC environments. 
The issue may be present in all 10g and newer installations.

具体参考:372959.1和340091.1

此条目发表在 Oracle 监听 分类目录。将固定链接加入收藏夹。

《WARNING: Subscription for node down event still pending》有 3 条评论

  1. 惜分飞 说：
    2013 年 2 月 26 日23:27

    alex,

    数据库版本在Version 10.1.0.2.0 to 11.2.0.0中都有可能出现该问题
    至于怎么模拟，我不太清楚

  2. alex 说：
    2013 年 2 月 25 日15:21

    博主你好，请问id 号的错误在所有的非rac oracle版本上都会遇到吗？什么情况下才能产生监听僵死，我遇到这个错误后，就没有办法模拟出来

  3. 惜分飞 说：
    2012 年 11 月 26 日21:19 
    Applies to: 
Oracle Net Services - Version 10.1.0.2.0 to 11.2.0.0 [Release 10.1 to 11.2]
Information in this document applies to any platform.
Checked for relevance on 29-Aug-2012
This issue affects only 10g and newer listeners.

Symptoms
You are receiving the following warning messages in the listener.log file constantly:
'WARNING: Subscription for node down event still pending' 

Changes
This may be a new installation or a recent upgrade to 10g or newer.
Cause
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. 

Solution
Set the following parameter in the listener.ora:

SUBSCRIBE_FOR_NODE_DOWN_EVENT_<listener_name>=OFF

Where <listener_name> should be replaced with the actual listener name configured in the
LISTENER.ORA file.
SUBSCRIBE_FOR_NODE_DOWN_EVENT_<listener_name> parameter is to be placed by itself on an empty line.
It will be necessary to restart or reload the listener following the addition of this parameter.
This will prevent the messages from being written to the log file and may also prevent the TNS
Listener from hanging periodically. See NOTE 340091.1

Please Note: Setting SUBSCRIBE_FOR_NODE_DOWN_<listener_name> to OFF disables a 
necessary RAC functionality. The above workaround is recommended only for non-RAC environments. 
The issue may be present in all 10g and newer installations.
Note: The use of this undocumented parameter may cause problems with 
the use of the Net Manager (NetMgr) configuration utility. See Note 437598.1.