Not able to start/stop listener having client and database on same machine (AIX 6.1)

Hi,

I have database oracle11gR2 11.2.0.1 installed on my machine AIX 6.1 64 bit at location - /home/oracle/app/oracle/product/11.2.0/dbhome_1 and I installed Oracle 11gR2 client 32 bit on the same machine - /home/oracle/app/oracle/product/11.2.0/client_1. Then I export

    enter code here
    ORACLE_HOME= /home/oracle/app/oracle/product/11.2.0/client_1
    ORACLE_SID =orcl
    LIBPATH=$LIBPATH:$ORACLE_HOME/lib and
    PATH =$PATH:$ORACLE_HOME/bin

I also copied the TNSNAMES.ORA from dbhome_1/network/admin to client_1/network/admin

From db_home/bin - Am trying to start and stop the listener it is saying -
    bash-3.2# ./lsnrctl

    LSNRCTL for IBM/AIX RISC System/6000: Version 11.2.0.1.0 - Production on 12-JUN-2013    
    01:55:12


Welcome to LSNRCTL, type "help" for information.

    LSNRCTL> status
    Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
    TNS-12541: TNS:no listener
    TNS-12560: TNS:protocol adapter error
    TNS-00511: No listener
    IBM/AIX RISC System/6000 Error: 79: Connection refused

I also checked -    bash-3.2# ps -ef | grep lsnr
    oracle 12845248 1 0 11:18:12 - 0:10     /home/oracle/app/oracle/product/11.2.0/dbhome_1/bin/tnslsnr LISTENER -inherit
root 15466574 11272326 0 02:06:54 pts/0 0:00 grep lsnr

I need to connect sqlplus / as sysdba which is complaining bash-3.2$ sqlplus / as sysdba

SQL*Plus: Release 11.2.0.1.0 Production on Thu Jun 13 01:05:07 2013

Copyright (c) 1982, 2009, Oracle.  All rights reserved.

    ERROR:
    ORA-12545: Connect failed because target host or object does not exist

My listener.ora file -

# listener.ora Network Configuration File: /home/oracle/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
# Generated by Oracle configuration tools.
    LISTENER =
      (DESCRIPTION_LIST =
        (DESCRIPTION =
          (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
          (ADDRESS = (PROTOCOL = TCP)(HOST =lodibm17.ca.com)(PORT = 1521))
        )
      )

    ADR_BASE_LISTENER = /home/oracle/app/oracle


My tnsnames.ora file  -

# tnsnames.ora Network Configuration File: /home/oracle/app/oracle/product/11.2.0/dbhome_1/network/admin/tnsnames.ora
# Generated by Oracle configuration tools.

    LISTENER_ORCL =
      (ADDRESS = (PROTOCOL = TCP)(HOST =lodibm17.ca.com)(PORT = 1521))


    ORCL =
      (DESCRIPTION =
        (ADDRESS = (PROTOCOL = TCP)(HOST =lodibm17.ca.com)(PORT = 1521))
        (CONNECT_DATA =
          (SERVER = DEDICATED)
          (SERVICE_NAME =orcl.ca.com)
        )
      )

SQlnet.ora
# sqlnet.ora Network Configuration File: /home/oracle/app/oracle/product/11.2.0/dbhome_1/network/admin/sqlnet.ora
# Generated by Oracle configuration tools.

    NAMES.DIRECTORY_PATH= (TNSNAMES, EZCONNECT)

    ADR_BASE = /home/oracle/app/oracle

I also noticed -

tnsping orcl.ca.com

TNS Ping Utility for IBM/AIX RISC System/6000: Version 11.2.0.1.0 - Production on 13-JUN-2013 01:10:24

Copyright (c) 1997, 2009, Oracle. All rights reserved.

Used parameter files:
    /home/oracle/app/oracle/product/11.2.0/client_1/network/admin/sqlnet.ora

Used EZCONNECT adapter to resolve the alias
Attempting to contact (DESCRIPTION=(CONNECT_DATA=(SERVICE_NAME=))(ADDRESS=(PROTOCOL=TCP)(HOST=10.131.91.157)(PORT=1521)))
OK (530 msec)

have one question - the host which tnsping is pinging Attempting to contact (DESCRIPTION=(CONNECT_DATA=(SERVICE_NAME=))(ADDRESS=(PROTOCOL=TCP)(HOST=10.131.91.157)(PORT=1521))), it should be same in tnsnames.ora or listener.ora ?

From which file tnsping is picking up the HOST=10.131.91.157 because in tnsnames.ora/listener.ora the hostname is lodibm17.ca.com (141.202.119.143) is different as it is shown below in /etc/hosts file..

ere is my content of /etc/hosts file on AIX -

127.0.0.1       loopback localhost      # loopback (lo0) name/address
141.202.119.143      lodibm17.ca.com lodibm17

Please help me to resolve the issue
kapil12Asked:
Who is Participating?
 
johnsoneConnect With a Mentor Senior Oracle DBACommented:
Yes, you can do that, but as I pointed out, I believe that become too difficult to manage.  If you need downtime for the listener, then you need to coordinate hundreds of outages, not just single outages.

I was really  trying to point out that the listener is a process that has nothing to do with the client install.  In this case, were both database and client software is on the same machine, it really doesn't make sense to me to be trying to run the listener out of the client software home.
0
 
johnsoneConnect With a Mentor Senior Oracle DBACommented:
First, when you are trying to start the listener, ORACLE_HOME should be set to /home/oracle/app/oracle/product/11.2.0/dbhome_1.  According to your settings, it is set to the client home, which is incorrect.  The listener belongs to the database, not the client.

When trying to make a connection the TNS settings would come from the tnsnames.ora in the $ORACLE_HOME/network/admin directory, or the one in $TNS_ADMIN if that is set.
0
 
kapil12Author Commented:
Yes able to Resolve the by setting ORACLE HOME to dbhome_1 and can able to start and stop the listener and able login sys as sysdba.

But it can't be possible with client ? From client am able to login with system/firewall@orcl. So can we start and stop listener from client ?
0
Get 10% Off Your First Squarespace Website

Ready to showcase your work, publish content or promote your business online? With Squarespace’s award-winning templates and 24/7 customer service, getting started is simple. Head to Squarespace.com and use offer code ‘EXPERTS’ to get 10% off your first purchase.

 
johnsoneConnect With a Mentor Senior Oracle DBACommented:
You cannot start/stop the listener from the client.  It is typically started from the same home as the database.  It definitely should be the same version.

I have seen rare cases where the listener is not on the same machine as the home, but those become a little difficult to manage.  It is better to keep it simple and start the listener from the same home as the database.  In the many installations I have seen over the years, I have only run across it once and in that case there was one listener on a single machine with many databases than ran out of different homes.  Personally, I don't like it and it becomes a nightmare to manage as all databases are tied to that one listener and maintenance windows become difficult to manage.
0
 
Geert GConnect With a Mentor Oracle dbaCommented:
>>The listener belongs to the database, not the client.

Technically, it belongs in the oracle home of the database software install
having a database in that same home isn't actually required for the listener to work

you could have databases running in homeX
and run your listeners in homeY

actually you can have 1 listener for the complete host for hundreds of databases in different homes on that same host
0
 
kapil12Author Commented:
Thanks for the Info. Am successfully able to run from database.
0
 
Geert GOracle dbaCommented:
downtime for a listener ?
never tried reload ?

edit the listener.ora
then from command prompt:

> lsnrctl
lsnrctl> reload
lsnrctl> status

done
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.