Due to business needs, you need to use a whitelist to restrict the addresses of users logging on to the database, and decide to use the database whitelist function!
Due to business needs, you need to use a whitelist to restrict the addresses of users logging on to the database, and decide to use the database whitelist function!
Due to business needs, you need to use a whitelist to restrict the addresses of users logging on to the database, and decide to use the database whitelist function!
Generally, you only need to add the following content to sqlnet. ora to the instance database startup whitelist:
TCP. VALIDNODE_CHECKING = yes (enable IP address restriction ),
TCP. INVITED_NODES = (192.168.1.103, ip2, ip3,...,... local IP address...) -- whitelist, must be a local IP address; otherwise, the listener will fail,
TCP. EXCLUDED_NODES = (192.168.1.102) -- blacklist
Because the environment is a RAC environment, the operations are slightly different.
1 sqlnet is not found in the $ ORACLE_HOME/NETWORK/ADMIN directory of an Oracle user. ora file. You must use the GUID to log on to sqlnet under $ ORACLE_HOME/NETWORK/ADMIN. add and modify the ora file.
2. A local IP address must be added to the whitelist. Because it is a RAC environment, you must add all the real IP addresses, private IP addresses, VIP addresses, and scan ip addresses of the connected segments to the whitelist.
3. You cannot use lsnrctl reload like a single machine at startup. You need to use srvctl to stop listener-n Node 1 and srvctl start listener-n Node 1. After a node is modified, modify another node to prevent business impact.
--------------------------------------------------------------------------------
Installing Oracle 12C in Linux-6-64
Install Oracle 11gR2 (x64) in CentOS 6.4)
Steps for installing Oracle 11gR2 in vmwarevm
Install Oracle 11g XE R2 In Debian
--------------------------------------------------------------------------------