RAC: TCP.VALIDNODE_CHECKING Failing after Listener Reload
Last updated on DECEMBER 12, 2017
Applies to:Oracle Net Services - Version 184.108.40.206 to 220.127.116.11 [Release 12.1]
Information in this document applies to any platform.
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)
Change to the sqlnet.ora file setting for: TCP.INVITED_NODES in $ORACLE_HOME/network/admin/sqlnet.ora in GRID_HOME.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms