Skip to content
Home » Oracle » How to Resolve ORA-00132: syntax error or unresolved network name

How to Resolve ORA-00132: syntax error or unresolved network name


Found error ORA-00132 in the alert log, when we're starting up a database.

WARNING: Invalid value for listener related parameter MIXED LISTENER
ORA-00141: all addresses specified for parameter LOCAL_LISTENER are invalid
ORA-00132: syntax error or unresolved network name 'LISTENER_ORCL'

ORA-00132 does not prevent us from starting up a database successfully, but we found "The listener supports no services" in the listener's status.

[oracle@test ~]$ lsnrctl status
The listener supports no services
The command completed successfully

Moreover, no one can connect to the database!


First of all, we need to know what value we're using for LOCAL_LISTENER.

SQL> show parameter local_listener

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
local_listener                       string      LISTENER_ORCL

OK, it's a connect identifier defined in tnsnames.ora for local naming.

Let's make a test to see the connectivity of the alias name by tnsping.

[oracle@test ~]$ tnsping LISTENER_ORCL
TNS-03505: Failed to resolve name

After around 80 seconds of waiting, the result TNS-03505 shows us that the connect identifier is an invalid one.

ORA-00132 means that the database can't find the listener to register with its services according to the address specified in LOCAL_LISTENER.


To solve the problem, we take several steps to make it.

Add Connect Identifier

We add the correct connect identifier used for LOCAL_LISTENER in tnsnames.ora.

[oracle@test ~]$ vi $ORACLE_HOME/network/admin/tnsnames.ora
  (ADDRESS = (PROTOCOL = TCP)(HOST = = 1521))

Test Connect Identifier

To test the connectivity of the alias, we use tnsping.

[oracle@test ~]$ tnsping LISTENER_ORCL
Used TNSNAMES adapter to resolve the alias
Attempting to contact (ADDRESS = (PROTOCOL = TCP)(HOST = = 1521))
OK (0 msec)

It looks good.


To notify the database to register with the listener, we can set the parameter LOCAL_LISTENER once again within memory scope, or restart the database.

SQL> alter system set local_listener=LISTENER_ORCL scope=memory;

System altered.

Please note that, ALTER SYSTEM REGISTER has no effect on making the database to register services with the listener in this case.

Leave a Reply

Your email address will not be published. Required fields are marked *