Applies to:
Oracle Net Services - Version 12.1.0.1 to 12.1.0.2 [Release 12.1]
Information in this document applies to any platform.
Symptoms
In a GRID or RAC environment where TCP.VALIDNODE_CHECKING is enabled, please be aware that any change to the TCP.INVITED_NODES or TCP.EXCLUDED_NODES
parameters would require a complete stop and start of the VIP listeners.
The LSNRCTL reload command after a change to TCP.INVITED_NODES is breaking the TCP.VALIDNODE feature. See BUG:22194469 TCP.INVITED_NODES is Disabled after LSNRCTL Reload
This behavior does not impact the SCAN listeners and does not seem to be present when running a local listener in RDBMS_HOME. (Versus GRID)
Changes
Change to the sqlnet.ora file setting for: TCP.INVITED_NODES in $ORACLE_HOME/network/admin/sqlnet.ora in GRID_HOME.
Cause
Cause of this problem is BUG:22194469 (Base bug is BUG:21616075).
Solution
Do NOT execute LSNRCTL reload against the LOCAL listener after making a change to the TCP.VALIDNODE_CHECKING Invited or Excluded nodes list.
And Do NOT execute LSNRCTL reload against the VIP making any change to listener.ora file.
In order to avoid this behavior, you MUST issue a complete LSNRCTL stop and LSNRCTL start after changing any entries in the TCP.EXCLUDED_NODES or
TCP.INVITED_NODES list.
References
BUG:22194469 - TCP.INVITED_NODES IS DISABLED AFTER RELOADING LISTENER
