Re: Q: Using OEM to discover 2 databases on 1 server

In message <XVsAXjSlbXAEFw49_at_jimsmith.demon.co.uk>, Jim Smith <jim_at_jimsmith.demon.co.uk> writes
>In message <32uuv1le36vbs1288m1qdnn6ciln758bv6_at_4ax.com>, Sybrand Bakker
><gooiditweg_at_nospam.demon.nl> writes
>>On Fri, 24 Feb 2006 21:09:37 GMT, Vince Laurent
>><vincelaurent_at_REMOVETHISsbcglobal.net> wrote:
>>
>>>I just finished installing OEM on our HPUX11i system running Oracle
>>>9.2.0.4. I also installed the oracle intelligent agent on this
>>>server. When I went to discover nodes via OEM It found the server BUT
>>>only the database that is running/holding OEM - not the other database
>>>on the system.
>>>
>>>How do I get OEM to recongize more that one DB on a server?
>>>
>>>Thanks!
>>>Vince
>>>-----------------------------------------------------
>>>Come race with us!
>>>http://www.mgpmrc.org
>>
>>Verify services.ora, snmp_rw.ora and snmp_ro.ora on the database
>>server. Services.ora should list both database and snmp_rw.ora (IIRC)
>>too.
>>If it doesn't, stop the agent using agentctl, delete all files in
>>$ORACLE_HOME/network/agent
>>and restart the agent using agentctl
>
>I think there is also a problem in 9.2 where the agent can't find
>instances unless they are in listener.ora. That is, it doesn't
>recognise autoregistered instances. If Sybrand's suggestion doesn't
>work, do it again, but add the instance to tnsnames.ora and restart the
>listener before restarting the agent.

My last sentence should refer to LISTENER.ORA, not TNSNAMES.ORA

-- 
Jim Smith
I'm afraid you've mistaken me for someone who gives a damn.