This discussion is archived
1 2 Previous Next 25 Replies Latest reply: Oct 12, 2012 6:21 AM by user12048358 Go to original post RSS
  • 15. Re: Users can not connect to the DB
    sb92075 Guru
    Currently Being Moderated
    user12048358 wrote:
    hi vreddy;

    this is the output for the command cat listener.ora

    IPLAB_LIST =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC))
    (ADDRESS = (PROTOCOL = TCP)(HOST = 170.20.221.64)(PORT = 51584))
    )

    SID_LIST_IPLAB_LIST =
    (SID_LIST =
    (SID_DESC =
    (SID_NAME = PLSExtProc)
    (ORACLE_HOME = /home/oracle/product/10.2.0)
    (PROGRAM = extproc)
    )
    (SID_DESC =
    (ORACLE_HOME = /home/oracle/product/10.2.0)
    (SID_NAME = IPLAB)
    )
    (SID_DESC =
    (ORACLE_HOME = /home/oracle/product/10.2.0)
    (SID_NAME = IPBLB)
    )
    )
    to my untrained eye, above does not appear to be valid.
  • 16. Re: Users can not connect to the DB
    user12048358 Newbie
    Currently Being Moderated
    hi sb92075;

    It was working for the last 2 years.
  • 17. Re: Users can not connect to the DB
    vlethakula Expert
    Currently Being Moderated
    Ok, you have non default listener

    start your non default listener, as you are referring this port in tnsnames.ora

    lsnrctl start IPLAB_LIST
  • 18. Re: Users can not connect to the DB
    Osama_Mustafa Oracle ACE
    Currently Being Moderated
    It was working for the last 2 years.
    Well , its not now .your configuration is wrong ,

    Recreate them (tnsnames.ora,listener.ora) again using netca
  • 19. Re: Users can not connect to the DB
    user12048358 Newbie
    Currently Being Moderated
    Hi vreddy;

    Apparently the listener is running already.
    this is the result for the command proposed;

    lsnrctl start IPLAB_LIST

    LSNRCTL for IBM/AIX RISC System/6000: Version 10.2.0.3.0 - Production on 10-OCT-2012 05:53:44

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

    TNS-01106: Listener using listener name LISTENER has already been started
    Still when I try to connect I get this error message;

    ERROR:
    ORA-12154: TNS:could not resolve the connect identifier specified

    Regards

    Al
  • 20. Re: Users can not connect to the DB
    EdStevens Guru
    Currently Being Moderated
    user12048358 wrote:
    Hi vreddy;

    Apparently the listener is running already.
    this is the result for the command proposed;

    lsnrctl start IPLAB_LIST

    LSNRCTL for IBM/AIX RISC System/6000: Version 10.2.0.3.0 - Production on 10-OCT-2012 05:53:44

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

    TNS-01106: Listener using listener name LISTENER has already been started
    Still when I try to connect I get this error message;

    ERROR:
    ORA-12154: TNS:could not resolve the connect identifier specified

    Regards

    Al
    ORA-12154 has nothing to do with the listener. The request never left the client.
    See http://edstevensdba.wordpress.com/2011/02/26/ora-12154tns-03505/
  • 21. Re: Users can not connect to the DB
    jgarry Guru
    Currently Being Moderated
    If you showed us listener.ora rather than another tnsnames.ora, someone probably overwrote the former with the latter. See if you have any backups that might clarify a different listener.ora.

    See http://docs.oracle.com/cd/B19306_01/network.102/b14212/listenercfg.htm#i490318
  • 22. Re: Users can not connect to the DB
    vlethakula Expert
    Currently Being Moderated
    Try,
    lsnrctl stop LISTENER
    lsnrctl start IPLAB_LIST
    And then ps -ef|grep -i tns

    Edited by: vreddy on Oct 10, 2012 12:34 PM
  • 23. Re: Users can not connect to the DB
    user12048358 Newbie
    Currently Being Moderated
    hi jgarry;

    Previously I was executing the netca to reconfigurate de listener.

    Then I try to connect to the DB, and now I get this error:
    export ORACLE_SID=ESLTST
    sqlplus /nolog
    SQL*Plus: Release 10.2.0.3.0 - Production on Wed Oct 10 16:55:29 2012

    Copyright (c) 1982, 2006, Oracle. All Rights Reserved.

    SQL> conn /as sysdba
    Connected to an idle instance.
    SQL> startup
    ORA-00119: invalid specification for system parameter LOCAL_LISTENER
    ORA-00132: syntax error or unresolved network name 'LISTENER_ESLTST

    Soi, after read the link you provide me, I try this:
    LOCAL_LISTENER=LISTENER_ESLTST
    export ORACLE_SID=ESLTST
    sqlplus /nolog
    SQL*Plus: Release 10.2.0.3.0 - Production on Wed Oct 10 16:55:29 2012

    Copyright (c) 1982, 2006, Oracle. All Rights Reserved.

    SQL> conn /as sysdba
    Connected to an idle instance.
    SQL> startup
    ORA-00119: invalid specification for system parameter LOCAL_LISTENER
    ORA-00132: syntax error or unresolved network name 'LISTENER_ESLTEST
    But continue with the same problem.

    Here is listener.ora file as now;

    SID_LIST_IPLAB_LIST =
    (SID_LIST =
    (SID_DESC =
    (SID_NAME = PLSExtProc)
    (ORACLE_HOME = /home/oracle/product/10.2.0)
    (PROGRAM = extproc)
    )
    (SID_DESC =
    (ORACLE_HOME = /home/oracle/product/10.2.0)
    (SID_NAME = IPLAB)
    )
    (SID_DESC =
    (ORACLE_HOME = /home/oracle/product/10.2.0)
    (SID_NAME = IPSBLB)
    )
    )

    IPLAB_LIST =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC))
    (ADDRESS = (PROTOCOL = TCP)(HOST = 170.20.221.64)(PORT = 1521))
    )

    LISTENER_ESLTST =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 170.20.221.64)(PORT = 1521))
    )
    )

    So, I stop and restart the listener, but the problem continues.

    Thanks for the ideas.

    Regards

    Al

    Edited by: user12048358 on Oct 10, 2012 5:18 PM
  • 24. Re: Users can not connect to the DB
    Osama_Mustafa Oracle ACE
    Currently Being Moderated
    SQL> startup
    ORA-00119: invalid specification for system parameter LOCAL_LISTENER
    ORA-00132: syntax error or unresolved network name 'LISTENER_ELSTEST
    Check
    Instance Fails to Start and Throws Errors ORA-00119 & ORA-00132 [ID 359386.1]
    Database Startup Fails With ORA-00119 [ID 471767.1]

    You could set your local_listener parameter with string connection not listener name , check from NAMES.DEFAULT_DOMAIN parameter in database .
  • 25. Re: Users can not connect to the DB
    user12048358 Newbie
    Currently Being Moderated
    Hi Osama;

    Finally I could solve the problem.

    First, I execute netca, as you proposed previously and configurate the listener.

    Then;

    The following parameter was added to the LISTENER.ORA:

    SUBSCRIBE_FOR_NODE_DOWN_EVENT_<listener name> = off


    Locate the ons.config file in the 10g(RDBMS) home and rename it to something else.

    For example:
    cd $ORACLE_HOME/opmn/conf
    mv ons.config ons.config.orig


    The 10g listener needs to be restarted after these changes

    After this, everything was OK.

    Best Regards

    Al
1 2 Previous Next

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points