topic Re: lsnrctl - why status unknown ? in Operating System - HP-UX

lsnrctl - why status unknown ?

Ratzie — Mon, 13 Mar 2006 11:41:13 GMT

Why when we give the command lsnrctl we get the status unknown?

It does give the time up ect. but it does not what to say they status.

LSNRCTL for Linux: Version 10.1.0.3.0 - Production on 13-MAR-2006 10:39:55

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

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC)))
STATUS of the LISTENER
------------------------
Alias listener
Version TNSLSNR for Linux: Version 10.1.0.3.0 - Production
Start Date 13-MAR-2006 09:11:41
Uptime 0 days 1 hr. 28 min. 13 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /opt/app/oracle/network/admin/listener.ora
Listener Log File /opt/app/oracle/network/log/listener.log
Listener Trace File /opt/app/oracle/network/trace/listener.trc
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.2.101)(PORT=1521)))
Services Summary...
Service "DATADB" has 1 instance(s).
Instance "DATADB", status UNKNOWN, has 1 handler(s) for this service...

The command completed successfully

Re: lsnrctl - why status unknown ?

Geoff Wild — Mon, 13 Mar 2006 12:13:03 GMT

Are you running it as root or as the oracle user?

Rgds...Geoff

Re: lsnrctl - why status unknown ?

Ratzie — Mon, 13 Mar 2006 12:47:19 GMT

as oracle user

Re: lsnrctl - why status unknown ?

Steven E. Protter — Mon, 13 Mar 2006 12:53:31 GMT

Shalom,

There is probably some obtuse technical requirements to get that status.

I've seen it for years and only cared if the listener actually was not working.

If it is, the cause is probably a lack of customer service oriented programming on their part, nothing to worry about.

Not an asnwer, but an opinion. It surprises me Oracle hasn't complained about my postings over the years.

SEP

Re: lsnrctl - why status unknown ?

Geoff Wild — Mon, 13 Mar 2006 13:20:48 GMT

http://www.orafaq.com/faq/what_does_unknown_status_mean_in_lsnrctl_status_output

"An 'UNKNOWN' status means that the instance is registered statically (with a SID_LIST) in the listener.ora file, rather than dynamically with service registration."

Rgds...Geoff

Re: lsnrctl - why status unknown ?

James A. Donovan — Mon, 13 Mar 2006 13:23:33 GMT

An UNKNOWN status means that the instance is registered statically
(with a SID_LIST) in the listener.ora file rather than dynamically with
service registration. Therefore, the status is not known.

The SID_LIST in the listener.ora file is not required.
One of the reasons why Oracle recommends not using one, is because it
may cause unnecessary overheads on the listener process.
The SID_LIST section only needs to be used for instances such as PLSExtProc.
It is not normally a problem having the instance duplicated in the SID_LIST,
but it is preferable not to have it.

Re: lsnrctl - why status unknown ?

Sandman! — Mon, 13 Mar 2006 13:49:43 GMT

Hi,

'UNKNOWN' status means that the instance is registered statically (with a SID_LIST) NOT dynamically in the listener.ora file. You can either ignore it or remove SID_LIST from your listener.ora so that your instance registers with the default listener on port 1521 or specify a local listener in your pfile (or spfile) with the host, port, protocol information as follows:

alter system set LOCAL_LISTENER="(address=(protocol=tcp)(host=yourhost)(port=your_listener_port))";

When you restart the instance, it should register with this listener. Having SID_LIST in listener.ora (since Oracle 9i) is not recommended since it causes additional overhead on the listener process.

cheers!

Re: lsnrctl - why status unknown ?

Indira Aramandla — Mon, 13 Mar 2006 19:44:50 GMT

Hi LHradowy,

An UNKNOWN status means that the instance is registered statically (with a SID_LIST) in the listener.ora file rather than dynamically with service registration. Therefore, the status is not known.

If the SID is not registered with the listener (lsnrctl status; Instance , status UNKNOWN)
but the service name is registered (status READY), then the connection to the info store db will fail (using SID), even though it is possible to make a sqlplus connection using the tnsnames.ora connect info, which specifies service_name for connections.

The SID_LIST in the listener.ora file is not required. One of the reasons why Oracle recommends not using one, is because it may cause un-necessary overheads on the listener process. The SID_LIST section only needs to be used for instances such as PLSExtProc. It is not normally a problem having the instance duplicated in the SID_LIST, but it is preferable not to have it.

The handlers are like this. One is for the Dedicated service in the SID_LIST. One is for the Dedicated service that has automatically registered itself with the listener process (instance_name in the init.ora file). One is for each Dispatcher that has started (Giop and SGiop use).

Indira A

Re: lsnrctl - why status unknown ?

Yogeeraj_1 — Mon, 13 Mar 2006 23:18:29 GMT

hi,

see also metalink note: 151223.1 "Oracle Net 9i Listener - Lsnrctl services / "status UNKNOWN" displayed"

kind regards
yogeeraj

Re: lsnrctl - why status unknown ?

Ratzie — Tue, 14 Mar 2006 10:09:34 GMT

excellent