ORA-00119: invalid specification for system parameter LOCAL_LISTENER - Page 2
DBAsupport.com Forums - Powered by vBulletin
Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 24

Thread: ORA-00119: invalid specification for system parameter LOCAL_LISTENER

  1. #11
    Join Date
    Sep 2016
    Posts
    14
    My recommendation would be first to try use localhost in TNSNAMES.ORA and LISTENER.ORA (and without any indication for the SERVICE_NAME in listener.ora), just to see if in this config you can start the listener, check listener status and services, tnsping the hoststring and connect using @hoststring from the server itself : if this donīt work you have a serious issue in your network config for this server, something is really blocking the listener process from communicating even with the localhost ip/hostname....
    If the config using localhost works (it would be the common result), then you can go for some config for ip / host resolution... As I said before, we donīt know if you are using some kind of DNS or not, and we donīt know Anything about your netowirk config but Yes - for a test, you could be giving the IP and the hostname resolution inside /etc/hosts - to do so, the sintax would be :

    IPAddress Hostname Alias

    so, if your IP is 192.168.1.122 and the qualified hostname is oradev.attlocal.net , the entry could be :

    192.168.1.122 oradev.attlocal.net oradev

    after that, if you see the correct IP in your NIC via ifconfig, AND if the :

    ping oradev
    ping oradev.attlocal.net
    ping 192.168.1.122
    traceroute oradev.attlocal.net

    commands result ok, you can go ahead and use this IP or this hostname in listener.ora and tnsnames.ora, yes....

    []s

    J. Laurindo Chiappa
    Quote Originally Posted by Janning View Post
    hi,

    I'd like to put the values in the host file first and try that (I don't need to make it static, I have the router assigning 192.168.1.122)
    I assume I only need to add the below line to the host?

    Change the current:
    127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
    ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6

    to be

    127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
    ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
    192.168.1.122 oradev.attlocal.net

  2. #12
    Join Date
    Sep 2016
    Posts
    13
    uname -a gives:

    [oracle@oradev ~]$ uname -a
    Linux oradev 3.8.13-118.11.2.el7uek.x86_64 #2 SMP Wed Sep 21 11:23:36 PDT 2016 x86_64 x86_64 x86_64 GNU/Linux


    I do need to connect externally. I put the values in the host file and the listener does start, but I can not connect by

    http://www.aanning.com:7172/apex/apex_admin

    This did work for 9 months (I do have all the proper ports forwarded to this box and the www.aanning.com is set up correct too)

  3. #13
    Join Date
    Sep 2016
    Posts
    14
    I repeat my recommendation - letīs do a step-by-step approach, one babystep after another.... So, first letīs try to confirm that network acess INSIDE the VM is ok, as the first step, okdoc ??
    ONLY when this is confirmed, we can try to look for the access from the host to the VM, right ??

    Donīt try to embrace all the world, letīs try a step-by-step approach...

    []s

    Chiappa

  4. #14
    Join Date
    Sep 2016
    Posts
    13
    On the Linux/oracle box:

    http://www.aanning.com:7172
    hrrp://192.168.1.122:7172

    The above two do not work....(APEX) I have to assume this is a different listener? I've never had to start it before.


    [oracle@oradev ~]$ lsnrctl status

    LSNRCTL for Linux: Version 12.1.0.2.0 - Production on 04-OCT-2016 14:42:25

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

    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=oradev.attlocal.net)(PORT=1522)))
    STATUS of the LISTENER
    ------------------------
    Alias LISTENER
    Version TNSLSNR for Linux: Version 12.1.0.2.0 - Production
    Start Date 03-OCT-2016 20:11:19
    Uptime 0 days 18 hr. 31 min. 6 sec
    Trace Level off
    Security ON: Local OS Authentication
    SNMP OFF
    Listener Parameter File /u01/app/oracle/product/12.1.0/dbhome_1/network/admin/listener.ora
    Listener Log File /u01/app/oracle/diag/tnslsnr/oradev/listener/alert/log.xml
    Listening Endpoints Summary...
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oradev)(PORT=1522)))
    (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1522)))
    Services Summary...
    Service "orcl" has 1 instance(s).
    Instance "orcl", status UNKNOWN, has 1 handler(s) for this service...
    The command completed successfully



    [oracle@oradev ~]$ lsnrctl service

    LSNRCTL for Linux: Version 12.1.0.2.0 - Production on 04-OCT-2016 14:44:09

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

    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=oradev.attlocal.net)(PORT=1522)))
    Services Summary...
    Service "orcl" has 1 instance(s).
    Instance "orcl", status UNKNOWN, has 1 handler(s) for this service...
    Handler(s):
    "DEDICATED" established:1 refused:0
    LOCAL SERVER
    The command completed successfully
    [oracle@oradev ~]$

  5. #15
    Join Date
    Sep 2016
    Posts
    14
    You donīt say but I see that you (probably) opted for including the IP and hostname in the /etc/hosts... Equally you donīt show it but I will Assume the ping ip/ping host/ifconfig/telnet in port 1522 were done with success, too...

    Ok : about APEX acess (talking yet about inside-the-VM accesses), first we need to know the APEX version and what type of gateway/server soiftware (ie, EPG, APEX Listener, http server, etc) you are using with it.... The most common option is the EPG(ie, the Embedded PL/SQL Gateway), which depends on the XDB component.
    If EPG is the gateway/serversoftware in use (** confirm this ** in your database, only you can say it), you must see a line :

    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=nameorIPofthelost)(PORT=portinuse))(Presentation=HTTP)(Ses sion=RAW))

    in the output for lsnrctl status...

    ** IF ** you are using EPG and you donīt see that, the reason could be the Listener not being started before the database (close the database, stop the listener, start the listener and only after this the database, if this was the case), or the XDB not starting OK (see the alert.log for messages abot XDB status)... https://mikesmithers.wordpress.com/2...database-does/ is a ref about this in XE database but in 12c it is not so different...

    Regards,

    Chiappa

    Quote Originally Posted by Janning View Post
    On the Linux/oracle box:

    http://www.aanning.com:7172
    hrrp://192.168.1.122:7172

    The above two do not work....(APEX) I have to assume this is a different listener? I've never had to start it before.


    [oracle@oradev ~]$ lsnrctl status

    LSNRCTL for Linux: Version 12.1.0.2.0 - Production on 04-OCT-2016 14:42:25

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

    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=oradev.attlocal.net)(PORT=1522)))
    STATUS of the LISTENER
    ------------------------
    Alias LISTENER
    Version TNSLSNR for Linux: Version 12.1.0.2.0 - Production
    Start Date 03-OCT-2016 20:11:19
    Uptime 0 days 18 hr. 31 min. 6 sec
    Trace Level off
    Security ON: Local OS Authentication
    SNMP OFF
    Listener Parameter File /u01/app/oracle/product/12.1.0/dbhome_1/network/admin/listener.ora
    Listener Log File /u01/app/oracle/diag/tnslsnr/oradev/listener/alert/log.xml
    Listening Endpoints Summary...
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oradev)(PORT=1522)))
    (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1522)))
    Services Summary...
    Service "orcl" has 1 instance(s).
    Instance "orcl", status UNKNOWN, has 1 handler(s) for this service...
    The command completed successfully



    [oracle@oradev ~]$ lsnrctl service

    LSNRCTL for Linux: Version 12.1.0.2.0 - Production on 04-OCT-2016 14:44:09

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

    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=oradev.attlocal.net)(PORT=1522)))
    Services Summary...
    Service "orcl" has 1 instance(s).
    Instance "orcl", status UNKNOWN, has 1 handler(s) for this service...
    Handler(s):
    "DEDICATED" established:1 refused:0
    LOCAL SERVER
    The command completed successfully
    [oracle@oradev ~]$

  6. #16
    Join Date
    Sep 2016
    Posts
    13
    Hi,,

    I didn't set up the APEX, another guy no longer here did, but it was working on port 7172

    http://www.aanning.com:7172/apex/f?p...20614507862358

    is the link I used for 9 months


    [oracle@oradev ~]$ lsnrctl status

    LSNRCTL for Linux: Version 12.1.0.2.0 - Production on 05-OCT-2016 13:45:11

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

    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=oradev.attlocal.net)(PORT=1522)))
    STATUS of the LISTENER
    ------------------------
    Alias LISTENER
    Version TNSLSNR for Linux: Version 12.1.0.2.0 - Production
    Start Date 03-OCT-2016 20:11:19
    Uptime 1 days 17 hr. 33 min. 52 sec
    Trace Level off
    Security ON: Local OS Authentication
    SNMP OFF
    Listener Parameter File /u01/app/oracle/product/12.1.0/dbhome_1/network/admin/listener.ora
    Listener Log File /u01/app/oracle/diag/tnslsnr/oradev/listener/alert/log.xml
    Listening Endpoints Summary...
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oradev)(PORT=1522)))
    (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1522)))
    Services Summary...
    Service "orcl" has 1 instance(s).
    Instance "orcl", status UNKNOWN, has 1 handler(s) for this service...
    The command completed successfully

  7. #17
    Join Date
    Sep 2016
    Posts
    13

  8. #18
    Join Date
    Sep 2016
    Posts
    14
    Well, if you canīt say what APEX version is installed and what is the config, it is a big problem, I think - it is not possible to us, far from there, continue without guess ...

    Anyway, I will try a (last) wild guess : the most common config is EPG, and with this config the XML DB component connect to the listener and add a http line/protocol to attend the http requestes received, my guess will be that due to the inability to start the listener after the network changes caused by vmmare new version, the XML DB was not able to connect .... ====>>> THIS is the Root Cause, imho, of your "problems" related in this thread, ie, the Fact that hostname/ipresolution donīt worked well after the vmware upgrade/new install, and WE THINK this was fixed (inside the VM, for now) putting the ip and hostname in the /etc/hosts...

    You donīt show to us but I will assume that tnsping a hosstring entry inside TNSNAMES.ORA is OK, the LOCAL_LISTENER parameter is correct, and a connection via sqlplus user/senha@hoststring is ok...

    If so, Try this :

    a) get the current config/port in APEX executing in sqlplus :

    select dbms_xdb.gethttpport from dual;

    and confirm the port 7172 as being in use

    b) shutdown the database

    c) shutdown the listener

    d) start the listener

    e) start the database

    f) see in alert.log and confirm the sucesfull start of xml db component

    ==> wait some minutes and you must see the database registered on the listener, and the http entry


    If this not occurs, then probably you is using some other config in your APEX, in this case I recommend a new APEX installation/config...

    Regards,

    J. Laurindo Chiappa

    Quote Originally Posted by Janning View Post

  9. #19
    Join Date
    Sep 2016
    Posts
    13
    Hi,

    Sorry, the data base is 12c enterprise, lastest verstion as of Dec 2015
    APEX was the lastest version as of Dec 2015 version 5.x, not sure exactly which one, but for sure 5
    Yes I did add to the host file:

    192.168.1.122 oradev.attlocal.net

    select dbms_xdb.gethttpport from dual yields :
    SQL> select dbms_xdb.gethttpport from dual;

    GETHTTPPORT
    -----------
    7172


    I shutdown all and rebooted linux then restarted the dB and listener?

    I did a search for the file "alert.log" from the root, and nothing came up

    Trying sites
    http://oradev.attlocal.net:7172/apex
    http://192.168.1.122:7172/apex

    I get unable to connect

  10. #20
    Join Date
    Sep 2016
    Posts
    14
    See, the complete file name is not "alert.log" , but alertXXX.log, where XXX is your instance - if your instance is, say, ORCL, the alert log file will exist in the form alertORCL.log , thatīs it - common Oracle concept here - sorry for not being clear about it...

    No need for a server reboot, only a db shutdown, listener stop, listener start and only after this the database startup - if after this sequence of operations the http protocol is not in the output of listener status, or your APEX is not using EPG or you have some config failuire in APEX - in any case I would recommend to you an APEX removal and reinstall / reconfig of APEX...

    Regards,

    J. Laurindo Chiappa
    Quote Originally Posted by Janning View Post
    Hi,

    Sorry, the data base is 12c enterprise, lastest verstion as of Dec 2015
    APEX was the lastest version as of Dec 2015 version 5.x, not sure exactly which one, but for sure 5
    Yes I did add to the host file:

    192.168.1.122 oradev.attlocal.net

    select dbms_xdb.gethttpport from dual yields :
    SQL> select dbms_xdb.gethttpport from dual;

    GETHTTPPORT
    -----------
    7172


    I shutdown all and rebooted linux then restarted the dB and listener?

    I did a search for the file "alert.log" from the root, and nothing came up

    Trying sites
    http://oradev.attlocal.net:7172/apex
    http://192.168.1.122:7172/apex

    I get unable to connect

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


Click Here to Expand Forum to Full Width