WARNING: Subscription for node down event still pending
FranklinFaces.com
FranklinFaces.com - Oracle & SQL Server Database Forums for all IT Professionals
 Home          Members     Calendar     Who's On

Welcome Guest ( Login | Register )
        



WARNING: Subscription for node down event... Expand / Collapse
Message
Posted 1/18/2009 9:51:41 AM Post #57
 

Supreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme Being
Thread: WARNING: Subscription for node down event still pending? Urgent!

"WARNING: Subscription for node down event still pending"

any help on this ...very urgent please
this is running on linux fedora and 10g .. never ever had this problem before.

Posted 1/18/2009 9:52:17 AM Post #58
 

Supreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme Being
btw this happens only when i restart my listener using lsnrctl
Posted 1/18/2009 9:53:53 AM Post #59
 

Supreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme Being
This is another difference when it was working, log look liked this
16-JAN-2009 15:57:52 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SID=vipdb)) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.1.2)(PORT=1521)) * establish * vidpdb * 0
1

Now it is

WARNING: Subscription for node down event still pending
16-JAN-2007 08:08:49 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=localhost.localdomain)(USER=oracle))(COMMAND=status)(ARGUMENTS=64)(SERVICE=LISTENER)(VERSION=169869568)) * status

Posted 1/18/2009 9:56:30 AM Post #60
 

Supreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme Being
I figured out the solution and it was very tricky and unique.

Problem occurred when my local ip changed from 192.168.1.2 to 1.92.168.1.4

So I changed the following info:
I changed from old to new ip in my init.ora
I changed ip from old to new in listener.ora
I changed ip from old to new in tnsnames.ora

So when I was trying to connect using sqlplus , it was not connecting

Reason: I had my sqlnet.ora restricted to 192.168.1.3,192.168.1.2
so I just added 192.168.1.4 and everything worked fine now.

Thank you.
Posted 6/10/2010 12:48:21 PM Post #199
 

Supreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme Being
These messages are related to the Oracle10g TNS Listener's default subscription to the Oracle Notification Service (ONS). In a non-RAC environment it is recommended to disable this subscription.

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.

This will prevent the messages from being written to the log file, but also prevent the 10g TNS
Listener from hanging periodically.

Hope this works for you.

Thanks,

« Prev Topic | Next Topic »


Reading This Topic Expand / Collapse
Active Users: 0 (0 guests, 0 members, 0 anonymous members)
No members currently viewing this topic.
Forum Moderators: silencer

Permissions Expand / Collapse

All times are GMT -5:00, Time now is 7:26am

Powered By InstantForum.NET v4.1.4 © 2010
Execution: 0.070. 9 queries. Compression Disabled.