Oracle FAQ Your Portal to the Oracle Knowledge Grid

Home -> Community -> Mailing Lists -> Oracle-L -> Subscribe_for_node_down_event


From: Vaidya, Shreepad <>
Date: Mon, 28 May 2007 06:18:34 -0500
Message-ID: <>


If you set SUBSCRIBE_FOR_NODE_DOWN_EVENT_LSNR=OFF In listener.ora (RAC) then TAF will not work. This workaround is ideal for Single instance database.

For RAC workaround suggested by Salem is more effective

                  Thanks and regards

Shreepad Vaidya  

-----Original Message-----

From: [] On Behalf Of
Sent: Monday, May 21, 2007 6:30 PM
To:; Subject: RE: Subscribe_for_node_down_event

I have a note I put in my listener.ora file stating this should be fixed by, or indicating this is a bug, and temp fix is subscribe for node down event set to off.

Since we are at one would think it has been fixed (or is it 11 now).

Joel Patterson
Database Administrator
904 727-2546

-----Original Message-----

[] On Behalf Of William Wagman Sent: Friday, May 18, 2007 5:40 PM
To: oracle-l
Subject: Subscribe_for_node_down_event


On a two node RAC cluster, Oracle Enterprise Edition on RHEL4 64-bit using CRS.

In my listener.log I see numerous occurrences of the message... WARNING: Subscription for node down event still pending In searching for the web I find it commonly suggested that the listener.ora file by updated to include the parameter SUBSCRIBE_FOR_NODE_DOWN_EVENT_LSNR=<some value>

This is where I get lost. I am unable to find any documentation as to what constitutes a node down event and what the ramifications are. What is a node down event?

I have searched the Oracle docs for this parameter, nothing is found. Searching for listener.ora refers me to the net services guide but I am unable to find specific syntax for this parameter, it doesn't even appear in the index. Searching also refers me to the configuring the listener.ora in the various clusterware guides but again, no syntax for the parameter is given nor is it listed in the index. I'm stumped.

What we are seeing is that our application is using web logic and it appears that after a while connections and querying start to slow down and restarting the listener temporarily appears to resolve the issue. Some of the notes about the warning message indicates that the listener encountering some memory issues but I really can't find any explanations of this anywhere.

If anyone can shed any light on this or point me to some documentation on what this means or how to troubleshoot this problem I would be very grateful.


Bill Wagman
Univ. of California at Davis
IET Campus Data Center
(530) 754-6208


-- Received on Mon May 28 2007 - 06:18:34 CDT

Original text of this message