Re: Understanding "lsnrctl status"

c-eriks_at_algonet.se (Christian Eriksson) wrote in message news:<d0d6f67c.0408160550.51f075ab_at_posting.google.com>...
> Hi!
>
> I want to clarify, for myself, some basic facts about Oracle Client
> Server configuration. I start with the listener configuration on the
> server side.
>
> What block(s) in what configuration file(s) defines the services
> (shown below)?
>
> What causes there to be more than one instance of a service (shown
> below)?
>
> Output from "lsnrctl status" (Oracle 9.2.0.1.0 on Sun Solaris 8):
>
> ........................
>
> Services Summary...
> Service "PLSExtProc" has 1 instance(s).
> Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this
> service...
> Service "ftgdb" has 2 instance(s).
> Instance "ftgdb", status UNKNOWN, has 1 handler(s) for this
> service...
> Instance "ftgdb", status READY, has 1 handler(s) for this service...
> Service "ftgdbXDB" has 1 instance(s).
> Instance "ftgdb", status READY, has 1 handler(s) for this service...
> The command completed successfully
>
> Regards Christian Eriksson

Starting with version 8.1 the Oracle instance and the listener have the ability to automatically find each other without listener.ora entries being predefinded for the database. Most listener.ora files however would have had SID_DESC entries for the existing databases in them since these were requried up to then. Habit, would result in entries being made for new databases.

I believe this is the cause of the double listing for a database instance via status. Unfortunately I am not allowed to change the listener.ora and test if removing the now redundant entries and bouncing the listener and databases 1- works correctly and 2- cleans up the status enties.

As noted this is conjecture, but perhaps you can test it and post back the results.

HTH -- Mark D Powell -- Received on Mon Aug 16 2004 - 22:22:40 CEST