Mir Sayeed Hassan – Oracle Blog

Oracle DBA – Tips & Techniques | Learn with real-time examples

  • Translate

  • It’s Me






  • My Certificates

  • Links

    My Acclaim Certification : Credly Profile
    My Oracle ACE Pro Profile

  • Achievements

    Awarded Top 100 Oracle Blogs from Worldwide - #RANK 39
  • VISITORS COUNT

  • Verified International Academic Qualification from World Education Service (WES)

    Verified International Academic Qualification from World Education Service (WES)

  • Jobs

TNS-00583: Valid node checking: unable to parse configuration parameters in Oracle 12c

Posted by Mir Sayeed Hassan on June 14th, 2021

TNS-00583: Valid node checking: unable to parse configuration parameters in Oracle 12c

Check the status of database

SQL> select status,instance_name,open_mode, version from V$database,v$instance;

STATUS INSTANCE_NAME OPEN_MODE VERSION
------------ ---------------- -------------------- -----------------
OPEN oemdb READ WRITE 12.1.0.2.0

Start the listerner

[oracle@oemdb admin]$ lsnrctl start

LSNRCTL for Linux: Version 12.1.0.2.0 - Production on 14-JUN-2021 12:35:46

Copyright (c) 1991, 2014, Oracle. All rights reserved.

Starting /u01/app/oracle/product/12.1.0.2/dbhome_1/bin/tnslsnr: please wait...

TNSLSNR for Linux: Version 12.1.0.2.0 - Production
System parameter file is /u01/app/oracle/product/12.1.0.2/dbhome_1/network/admin/listener.ora
Log messages written to /u01/app/oracle/diag/tnslsnr/oemdb/listener/alert/log.xml
Error listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=10.20.0.71)(PORT=1521)))

TNS-12560: TNS:protocol adapter error
TNS-00583: Valid node checking: unable to parse configuration parameters
Listener failed to start. See the error message(s) above...

Cause:
The listener.ora or sqlnet.ora might contain any special characters or have left justified parenthesis which are not accepted by the Oracle parser.

Verify the listener.ora & sqlnet.ora file

[oracle@oemdb ~]$ cat /u01/app/oracle/product/12.1.0.2/dbhome_1/network/admin/listener.ora
# listener.ora Network Configuration File: /u01/app/oracle/product/12.1.0.2/dbhome_1/network/admin/listener.ora
# Generated by Oracle configuration tools.

LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 10.20.0.71)(PORT = 1521))
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
)
)
[oracle@oemdb ~]$ cat /u01/app/oracle/product/12.1.0.2/dbhome_1/network/admin/sqlnet.ora
SEC_USER_UNAUTHORIZED_ACCESS_BANNER

Solution

– Try to take the backup of existing files listener.ora file & create a new by using the network Manager or Manual.
– Check any invalid or any special parameter assign in sqlnet.ora

In our case., sqlnet.ora contain one paramater, hence resolved by commenting the parameter & restarted the listener successfully.

[oracle@oemdb ~]$ cat /u01/app/oracle/product/12.1.0.2/dbhome_1/network/admin/sqlnet.ora
#SEC_USER_UNAUTHORIZED_ACCESS_BANNER
[oracle@oemdb admin]$ lsnrctl start
[oracle@oemdb admin]$ sqlplus / as sysdba

SQL> alter system register;
System altered.
[oracle@oemdb admin]$ lsnrctl status

LSNRCTL for Linux: Version 12.1.0.2.0 - Production on 14-JUN-2021 12:38:44

Copyright (c) 1991, 2014, Oracle. All rights reserved.

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=10.20.0.71)(PORT=1521)))
STATUS of the LISTENER
------------------------
Alias LISTENER
Version TNSLSNR for Linux: Version 12.1.0.2.0 - Production
Start Date 14-JUN-2021 12:38:31
Uptime 0 days 0 hr. 0 min. 12 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /u01/app/oracle/product/12.1.0.2/dbhome_1/network/admin/listener.ora
Listener Log File /u01/app/oracle/diag/tnslsnr/oemdb/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.20.0.71)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcps)(HOST=oemdb)(PORT=5500))(Security=(my_wallet_directory=/u01/app/oracle/admin/oemdb/xdb_wallet))(Presentation=HTTP)(Session=RAW))
Services Summary...
Service "oemdb" has 1 instance(s).
Instance "oemdb", status READY, has 1 handler(s) for this service...
The command completed successfully

=====Hence tested & verified in our env=====