Tags: database, file, following, friends, log, mysql, ora10g, oracle, parameter, sidora10, sql, status, unknown
LISTENER status unknown
I have the following listener status log for our ora10g db with SID=ora10 :
Listener Parameter File /u01/app/oracle/product/10.1.0.2/network/admin/listene
Listener Log File /u01/app/oracle/product/10.1.0.2/network/log/listener.
Listening Endpoints Summary...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "ora10" has 1 instance(s).
Instance "ora10", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
What does >>Instance "ora10", status UNKNOWN<< mean? why it is unknown?
Thanks a lot
Leave a comment...
- 3 Comments
- The status will show as "UNKNOWN" if there is a SID_DESC under the SID_LIST section in LISTENER.ORA file.
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 preferrable not to have it.
Verify that the INSTANCE_NAME, SERVICE_NAMES parameters in your INITSID.ORA file is what is expected.
When removing the SID_LIST section from your LISTENER.ORA file, the information for the sid is obtained from your INITSID.ORA file. Perform a status on the listener after a duration of time to allow the database to register with the listener.#1; Sat, 23 Feb 2008 12:45:00 GMT
- An UNKNOWN status means that the instance is registered statically in the listener.ora file : Configuring and Administering the Listener
Nicolas.#2; Sat, 23 Feb 2008 12:46:00 GMT
- What does "UNKNOWN" status mean in lsnrctl status output?
Submitted by admin on Sat, 2004-07-03 13:24.
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.
You can either ignore it, or remove the SID_LIST from your listener.ora so that your instance registers with default the listener running 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=1522))";
When you restart the instance,it should register with this listener.
Oracle, in fact, doesn't recommend having SID_LIST in listener.ora (since 9i) becose it seems to causes additional overhead on the listener process.
Thanks to Orafaq.com#3; Sat, 23 Feb 2008 12:47:00 GMT