Re: OEM Node discovery OK, but not DB, or Listener.

"Holger Baer" <holger.baer_at_science-computing.de> wrote in message news:d7mcha$8ie$1_at_news.BelWue.DE...
> Steve wrote:
>> Hi,
>> Strange issue. When logging into a local EM session can see a server
>
> No wonder because with a local session you can't discover nodes but
> rather configure them manually and the configuration is stored *locally*.
>> and tables no problemo, however when logging into the management
>> server, sysman, xxxx after discovering the node in question we do not
>> see the database or listener. Any ideas ?
>> Many thanks, Steve.
>>
>
> Oh dear, no version, no OS....
>
> I'm just assuming that we're talking 9i here:
>
> For the database to be found by the intelligent agent it must be listed
> in the listener.ora ($ORACLE_HOME/network/admin).
>
> The listener must be listed in services.ora ($ORACLE_HOME/network/agent),
> at startup the intelligent agent will (should) detect if a database is
> missing in the services.ora and add it. If it's already there, try
> deleting
> the respective line - or maybe better: shutdown IA, rename services.ora
> and start IA again. Check services.ora if the database is listed now.
> If it isn't, you probably have a misconfiguration in your listener.ora.
>
> HTH
> Holger

I believe the agent first checks the /etc/oratab and /etc/lsnrtab files (or the Windows registry) during its discovery. So please check if your db and listener are properly listed there (and they should be if you created your db with the dbca).

Matthias Received on Thu Jun 02 2005 - 14:37:38 CDT