Path: news.easynews.com!newsfeed1.easynews.com!easynews.com!easynews!c03.atl99!news.webusenet.com!news02.tsnz.net!newsfeed01.tsnz.net!ken-transit.news.telstra.net!news.telstra.net!newsfeeds.bigpond.com!not-for-mail From: "Howard J. Rogers" Subject: Re: OEM finds node but not all instances. User-Agent: Pan/0.13.0 (The whole remains beautiful) Message-ID: Newsgroups: comp.databases.oracle.server References: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Lines: 35 Date: Tue, 04 Mar 2003 06:19:29 +1100 NNTP-Posting-Host: 144.138.45.34 X-Trace: newsfeeds.bigpond.com 1046718624 144.138.45.34 (Tue, 04 Mar 2003 06:10:24 EST) NNTP-Posting-Date: Tue, 04 Mar 2003 06:10:24 EST Organization: Telstra BigPond Internet Services (http://www.bigpond.com) Xref: newsfeed1.easynews.com comp.databases.oracle.server:178292 X-Received-Date: Mon, 03 Mar 2003 12:21:03 MST (news.easynews.com) On Sun, 02 Mar 2003 14:19:41 +0000, Preston Kemp wrote: > Hi all, > > I'm running 8.1.7 on Win2k. I've just installed OEM, but it's only > finding 1 of my 4 instances (they're all on the same server). I > installed the repository on 1 of the instances that isn't being found. > All 4 are in tnsnames.ora. I can still connect to all of them through > SQLPlus etc. Any ideas on how to make the other 3 appear? Yup: forget about the tnsnames.ora. Your problem is likely the listener.ora. For quirky reasons best known to itself, the Intelligent Agent that informs OEM about which databases are available to be managed isn't that intelligent, and simply runs off to the Listener and checks the SID_LIST in the listener.ora. If your databases aren't mentioned there (ie, declared statically) then the agent won't know about them. So: fix up your listener.ora by using the Network Configuration Manager to add the 3 other SIDs to the Listener's known database, and then re-start the Intelligent Agent. You should then be able to discover them all in OEM. By the way: just a tip. Instead of waiting to fire up OEM and run the discovery wizard, have a look in ORACLE_HOME/network/admin/agent for a file called services.ora. Open that up in a text editor, and see which SIDs are listed there. If they are in services.ora, OEM will be able to find them. Regards HJR