listener question

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

obakesan - 29 Jul 2008 15:02 GMT

Hi

when I start my listener I get the following appear on the screen

Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1)))

(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=localhost.localdomain)(PORT=1521)))
Services Summary...
Service "PLSExtProc" has 1 instance(s).

however in my tnsnames.ora file and my listner.ora files I have a different
host

tnsnames.ora:

ORCL =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = oracle.koti)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = orcl)
)
)

and listener.ora:

LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
(ADDRESS = (PROTOCOL = TCP)(HOST = oracle.koti)(PORT = 1521))
)
)

is this just a text file that can be edited or have I made some errors?

thanks

See Ya
(when bandwidth gets better ;-)

Chris Eastwood
Photographer, Programmer Motorcyclist and dingbat
blog: http://cjeastwd.blogspot.com/

please remove undies for reply

Reply to this Message

bdbafh - 29 Jul 2008 15:19 GMT

> Hi
>
[quoted text clipped - 43 lines]
>
> please remove undies for reply

Hi Chris.

Its customary in this newsgroup to list the Oracle edition, version,
OS info.
I would guess that you're running 10.2.0.1 on a 32 bit Linux OS.

Yes, the configuration files

listener.ora
sqlnet.ora
tnsnames.ora

are indeed text files that can be edited directly.

One can also launch the Net Manager utility to made changes that will
be relatively certain to be in proper form so as to not through
errors.

$ netmgr

If you are not using an external procedure listener, that entry can be
removed.
That functionality increases the exposure surface ... and some people
take issue with the "enabled by default" attitude of the dbca and pre-
fabbed starter databases in general.

localhost.localdomain should resolve to the ip address of the host
using TCP (check it with a ping).
If you don't have execute privs on the ping utility, the utility
tnsping can be used.
If one is only supporting local connections, bequeath or IPC can also
be used.
Bequeathed connections do not involve connecting via a TNS Listener.

After you startup the database instance (which appears to be "ORCL"),
do you see the service registered with the listener?

$ lsnrctl status

If so, then you don't likely have any issues.

So ... fire up netmgr, delete the entry for the PLS external procedure
listener, check the entry for the service that you want to support,
save the configuration and restart the listener.
You'll need to wait for the database instance to re-register itself
with the listener, usually less than 3 minutes.
you can also manually register the service with the listener via
sqlplus:

$ export ORACLE_SID=orcl
$ sqlplus / as sysdba
SQL> alter system register;
SQL> quit

hth.

-bdbafh

Reply to this Message

obakesan - 30 Jul 2008 13:51 GMT

Hi

In article
<2c780294-def6-42b0-b3d9-5df5fd9a1e0f@m36g2000hse.googlegroups.com>, bdbafh
[snip]

>> Listening Endpoints Summary...
>> (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1)))
[quoted text clipped - 8 lines]
>> tnsnames.ora:
>> (ADDRESS = (PROTOCOL = TCP)(HOST = oracle.koti)(PORT = 1521))

[snip]

>> and listener.ora:
>> (ADDRESS = (PROTOCOL = TCP)(HOST = oracle.koti)(PORT = 1521))

[snip]

>> is this just a text file that can be edited or have I made some errors?

>Its customary in this newsgroup to list the Oracle edition, version,
>OS info.

pardon me :-o

from my EM window:
Instance Name orcl
Version 10.2.0.1.0

>I would guess that you're running 10.2.0.1 on a 32 bit Linux OS.

well I'm not *entirely* certain, but I assume its 32 bit, for example

# uname -a
Linux oracle.koti 2.6.9-22.ELsmp #1 SMP Mon Sep 19 18:32:14 EDT 2005 i686
athlon i386 GNU/Linux

>Yes, the configuration files
>
[quoted text clipped - 3 lines]
>
>are indeed text files that can be edited directly.

ok ... well (from above) they contain references to HOST = oracle.koti and
I think that the host also thinks its oracle.koti too as using 'hostname'
gives:

# hostname
oracle.koti

but interestingly I see in my enterprise manager www window (displaying on
another machine on the same subnet)

Host localhost.localdomain
Listener LISTENER_localhost.localdomain

I use the URL:

http://10.0.0.56:1158/em/

to get to it (I'm behind a router, and this side is 10.0.0.0).

>One can also launch the Net Manager utility to made changes that will
>be relatively certain to be in proper form so as to not through
>errors.

>$ netmgr
>
>If you are not using an external procedure listener, that entry can be
>removed.

ok ... I'll look into that one too Thanks :-)

>localhost.localdomain should resolve to the ip address of the host
>using TCP (check it with a ping).

ah, well that's where it gets interesting here:

# ping localhost.localdomain
PING localhost.localdomain (127.0.0.1) 56(84) bytes of data.
64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=0 ttl=64 time=0.019
ms

--- localhost.localdomain ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 0.017/0.018/0.020/0.005 ms, pipe 2

which is some sort of loopback

so I made a change to the /etc/hosts file which now looks like this:

# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
10.0.0.56 oracle.koti oracle

and then restarted my box ... now here's where it gets more strange as now I
can't get the emctl to start (although the listener still fires up)

------------------------------------
$ lsnrctl start

LSNRCTL for Linux: Version 10.2.0.1.0 - Production on 30-JUL-2008 15:11:02

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

Starting /u01/app/oracle/product/10.2.0/db_1/bin/tnslsnr: please wait...

TNSLSNR for Linux: Version 10.2.0.1.0 - Production
System parameter file is
/u01/app/oracle/product/10.2.0/db_1/network/admin/listener.ora
Log messages written to
/u01/app/oracle/product/10.2.0/db_1/network/log/listener.log
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1)))
Listening on:
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oracle.koti)(PORT=1521))
)

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))
STATUS of the LISTENER
------------------------
Alias LISTENER
Version TNSLSNR for Linux: Version 10.2.0.1.0 - Production
Start Date 30-JUL-2008 15:11:03
Uptime 0 days 0 hr. 0 min. 0 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File
/u01/app/oracle/product/10.2.0/db_1/network/admin/listener.ora
Listener Log File
/u01/app/oracle/product/10.2.0/db_1/network/log/listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oracle.koti)(PORT=1521)))
Services Summary...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully

------------------------------------

$ emctl start dbconsole
TZ set to US/Eastern
OC4J Configuration issue.
/u01/app/oracle/product/10.2.0/db_1/oc4j/j2ee/OC4J_DBConsole_oracle.koti_orcl
not found.

however there is a directory OC4J_DBConsole_localhost.localdomain_orcl

$ ls -l /u01/app/oracle/product/10.2.0/db_1/oc4j/j2ee/
total 24
-rw-r--r-- 1 cje oinstall 256 Jul 24 10:59 deploy_db.ini
drwxr-x--- 15 cje oinstall 4096 Jul 24 10:58 home
drwxr-x--- 9 cje oinstall 4096 Jul 24 10:57 isqlplus
drwxr-x--- 3 cje oinstall 4096 Jul 24 10:57 oc4j_applications
drwxr-x--- 5 cje oinstall 4096 Jul 24 10:57 OC4J_DBConsole
drwxr-x--- 7 cje oinstall 4096 Jul 24 11:02
OC4J_DBConsole_localhost.localdomain_orcl

ok ... so I'll take a punt on things being created with hard coded depenencies
and move things to where its looking for them:

$ mv OC4J_DBConsole_localhost.localdomain_orcl/
OC4J_DBConsole_oracle.koti_orcl/

bewdy ... then I get

EM Configuration issue. /u01/app/oracle/product/10.2.0/db_1/oracle.koti_orcl
not found.

ok ...
$cd /u01/app/oracle/product/10.2.0/db_1

$mv localhost.localdomain_orcl/ oracle.koti_orcl/

then have another belt at it ...

$ emctl start dbconsole
TZ set to US/Eastern
Oracle Enterprise Manager 10g Database Control Release 10.2.0.1.0
Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
http://localhost.localdomain:1158/em/console/aboutApplication
Starting Oracle Enterprise Manager 10g Database Control
.......................... started.
------------------------------------------------------------------
Logs are generated in directory
/u01/app/oracle/product/10.2.0/db_1/oracle.koti_orcl/sysman/log

I can now connect my browser to http://132.234.0.56:1158/em and log in
but *something* still thinks that its localhost.localdomain
it appears that there are some problems with hard coding dependencies.
because I still see in EM the following:

Instance Name orcl
Version 10.2.0.1.0
Host localhost.localdomain
Listener LISTENER_localhost.localdomain

>do you see the service registered with the listener?
>
>$ lsnrctl status

yes, but as before the data being reported in
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oracle.koti)(PORT=1521)))

is perhaps not from the .ora files (because it's remained the same no matter
what was in them)

$ lsnrctl status

LSNRCTL for Linux: Version 10.2.0.1.0 - Production on 30-JUL-2008 15:47:57

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

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))
STATUS of the LISTENER
------------------------
Alias LISTENER
Version TNSLSNR for Linux: Version 10.2.0.1.0 - Production
Start Date 30-JUL-2008 15:11:03
Uptime 0 days 0 hr. 36 min. 54 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File
/u01/app/oracle/product/10.2.0/db_1/network/admin/listener.ora
Listener Log File
/u01/app/oracle/product/10.2.0/db_1/network/log/listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oracle.koti)(PORT=1521)))
Services Summary...

>You'll need to wait for the database instance to re-register itself
>with the listener, usually less than 3 minutes.
>you can also manually register the service with the listener via
>sqlplus:

bewdy ... thanks for that hint!

>hth.

heaps :-)

I still have 'unresolved or unknown issues' but I'm moving along here

thanks

See Ya
(when bandwidth gets better ;-)

Chris Eastwood
Photographer, Programmer Motorcyclist and dingbat
blog: http://cjeastwd.blogspot.com/

please remove undies for reply

Reply to this Message