Home > oracle > Oracle 11g Release 2: ORA-00119: invalid specification for system parameter LOCAL_LISTENER

Oracle 11g Release 2: ORA-00119: invalid specification for system parameter LOCAL_LISTENER

I’ve recently installed an Oracle 11g Release 2 database ( and when I bounce the database (using the shutdown and startup commands), the database is unable to start:

SQL> startup
ORA-00119: invalid specification for system parameter LOCAL_LISTENER
ORA-00132: syntax error or unresolved network name 'LISTENER_LAB11'

This is due to the lack of a LOCAL_LISTENER, that must be defined in the TNSNAMES.ORA, according to the Oracle Database Reference 11gR2:

LOCAL_LISTENER specifies a network name that resolves to an address or address list of Oracle Net local listeners (that is, listeners that are running on the same machine as this instance). The address or address list is specified in the TNSNAMES.ORA file or other address repository as configured for your system.

So, in your TNSNAMES.ORA (not in LISTENER.ORA) you must define this entry for the local listener:

 (ADDRESS = (PROTOCOL = TCP)(HOST = toralin1)(PORT = 1523))

And now you can startup the database. Be sure to set the .WORLD if you have the parameter names.default_domain set at sqlnet.ora.

You can learn more about the LOCAL_LISTENER in this excellent post of Ed Stevens: Exploring the LOCAL_LISTENER parameter

  1. Trupti Harne
    May 30, 2018 at 11:45

    Thank you very much for the solution


  2. James Anning
    September 25, 2016 at 6:01


    Let me start by saying, I’m not really a beginner at all this, but by no means an expert. I have Oracle 12c enterprise set up on a Oracle Enterprise Linux ver 7 box.
    This has always worked fine, start Linux, from a terminal window
    [oracle@oradev ~]$ sqlplus /nologSQL> conn SYS as SYSDBA
    Enter password: xxxxx
    lsnrctl start

    All was well. I have this running on VMware® Workstation 12 Pro, 12.5.0 build-4352439. I recently updated VMware…now when I get to
    startup I get:
    SQL> startup
    ORA-00119: invalid specification for system parameter LOCAL_LISTENER
    ORA-00130: invalid listener address ‘(ADDRESS=(PROTOCOL=TCP)(HOST=oradev.attlocal.net)(PORT=1522))’

    Please advise?


    • October 26, 2016 at 8:07

      Hi James, excuse me for the late reply.
      Have you checked hosts file and firewall?
      Could you post your listener.ora, tnsnames.ora and sqlnet.ora (if present)?
      From your linux guest, are you able to ping to the gust name (te one from the hosts file)?


  3. SRK
    July 18, 2015 at 20:06

    Thankyou for the solution, now its clear.


  4. jean-michel A.
    March 2, 2015 at 19:14

    Thank you very much Miquel.
    I did not know what to do with those ORA-0119 and 132 errors.
    You gave me the solution.
    Is it a specificity of the 11G ?

    Greetings from France.

    Jean-michel, Nemours


  5. August 29, 2014 at 0:21

    Your suggestion was interesting; but, it was not the solution for me. I also checked the spfile and the parameter wasn’t there. Then I built a skinny pfile and tried to startup the DB, same error… and then I remembered. I had spun up a new instance (on AWS) and I had a new IP address… making the changes in the tnsnames.ora and listener.ora file was not enough. I totally forgot about /etc/hosts. Once this hosts IP address was changed there, the database started up normally.


    • August 29, 2014 at 17:47

      Thanks for your comment David. I’m sure it will be useful to other people.


  6. FK
    July 30, 2014 at 22:02

    hi Miquel,

    Thanks for sharing; your blog solved a riddle for me ! God bless you!



  7. Peter
    July 1, 2014 at 9:14

    Miquel – You saved me. Dunno how many blogs and posts i browsed. Making the entry of listener in tnsnames.ora solved my problem. God bless you.!!! 🙂


  8. Robert
    November 8, 2013 at 14:25

    I found it a bit more flexible to delete the parameter from the SPFILE.

    SQL>Create pfile from spfile;

    –delete the LOCAL_LISTENER parameter from the pfile.

    SQL> Create spfile from pfile;

    Good to know there are other options for dealing with this error though!


  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: