This post covers the issue that one of our trainees from Oracle AppsDBA (R12.2): Install | Patch | Clone | Maintain training (For FREE Master Class, Click here) was facing while starting the Database listener & also includes the fixes of the Issue.
When he was trying to start the database listener, he was getting the error message: “TNS-12560: TNS: protocol adapter error, TNS-00584: Valid node checking configuration error”
TNS is basically Transparent Network Substrate and mainly used for connection with Oracle Databases. It’s an Oracle computer network technology that supports homogeneous p2p(peer-to-peer) connectivity on top of other networking technologies such as TCP/IP. Oracle use tnsnames.ora to define TNS connectivity with Oracle Database. For more information check Oracle link here.
Now let’s discuss the issue and fix that our trainee was hitting.
One of our trainees was trying to start the database listener using below command:
lsnrctl start <listener_name>
But Database listener was failing with below error messages:
TNSLSNR for Linux: Version 126.96.36.199.0 – Production
System parameter file is /u01/oracle/PRD122_12102/product/12.1.0/network/admin/PRD12111_1702upg24/listener.ora
Log messages written to /u01/oracle/PRD122_12102/product/12.1.0/admin/PRD12111_1705ecloud05/diag/tnslsnr/1705ecloud05/prd12111/alert/log.xml
Error listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=1705ecloud05.k21academy.com)(PORT=1532)))
TNS-12560: TNS:protocol adapter error
TNS-00584: Valid node checking configuration error
Listener failed to start. See the error message(s) above…
The trainee was hitting this issue because of the local hostname mentioned in sqlnet.ora file (located at $ORACLE_HOME/network/admin) was not correct. Oracle no longer allows the listener to startup if an invalid hostname or IP address is specified in the invited_nodes list. The listener will not start if any of the hosts or IP addresses are unreachable.
In sqlnet.ora, you will see below two node validation statements. These two statements mean the user will be able to make the connection to the nodes that are added in the Invited nodes list. You can comment out these node validation lines in sqlnet.ora file ($ORACLE_HOME/network/admin) and after that, you will be able to start the listener.
#tcp.validnode_checking = yes
To fix this issue, correct the name of the local hostname in below node validation line in sqlnet.ora file ($ORACLE_HOME/network/admin) and issue will be resolved. So, ensure that all the hostnames and IP addresses in the invited nodes list are reachable.
tcp.validnode_checking = yes
This post is from Troubleshooting module of our Oracle Apps DBA (R12.2) Training, in which we cover Architecture & Changes in Oracle E-Business Suite R12.2, Staging & Installation, File System & Important Files in R12.2, Start/Stop, Patching, AD Administration, Cloning, Concurrent Managers, AutoConfig, Password Management, and Troubleshooting and much more.
- Local Naming Parameters (tnsnames.ora)
- Listener Fails to Start Using TCP.VALIDNODE_CHECKING: TNS-12532 TNS:Invalid Argument (Doc ID 287500.1)
- Lsnrctl Start Yields: TNS-00583 Valid Node Checking Unable To Parse Configuration Parameters (Doc ID 377599.1)
- [Troubleshooting] Oracle Apps R12.2 Online Patching ADOP : Prepare Phase Issue
- [Solved] RC-20200: Fatal: Could not find Unzip When Installing EBS R12.1
- Oracle AppsDBA (R12): Step by step Activity Guides
- Oracle AppsDBA (R12.2): Install | Patch | Clone | Maintain
Next Task For You
Begin your journey towards becoming an Apps DBA by joining our FREE Masterclass on How To Become an Oracle Apps DBA (R12) & Earn A Lot More In 2020.