How to Enable VNCR on RAC Database to Register only Local Instances
(Doc ID 1914282.1)
Last updated on NOVEMBER 07, 2018
Applies to:Oracle Net Services - Version 220.127.116.11 to 18.104.22.168 [Release 11.2 to 12.2]
Oracle Database - Enterprise Edition - Version 22.214.171.124 to 126.96.36.199 [Release 11.2 to 12.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
Explains the VNCR or Validnode checking registration option that was introduced in 188.8.131.52 and enhanced in 184.108.40.206.
Starting with 220.127.116.11 we have the option of using VNCR to protect the listener from having remote/unknown instances registering to it.
See <Note 1600630.1> Valid Node Checking For Registration (VNCR)
On 18.104.22.168 RAC databases, the parameter VALID_NODE_CHECKING_REGISTRATION_listener_name is set to off.
However, sometimes this allows other instances in the same subnet to register against these listeners. We want to prevent that and allow only local instances to that RAC database to be registered with these listeners.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document