Did you ever discover the rogue instance? I would be interested in learning
why it wasn't being discovered.
Phil Wilson ([EMAIL PROTECTED])
DBA, Operations Group
SkillSoft, Learning Solutions for the Human Enterprise
506.462.1124(w)
506.447.0334(c)
-Original Message-
Sent: Friday,
Not yet. I have found some interesting tidbits in metalink and
will get back to this. However, they have me in training this
week so I am not doing much research, just hitting the few
immediate fires I can during breaks. :(
I'll let you know if I find something though.
John P Weatherman
Message-
From: Deshpande, Kirti
Sent: Friday, October 18, 2002 12:09 PM
To: '[EMAIL PROTECTED]'
Subject: RE: OEM can't seem to discover 1 instance
Gaja is not active on the list due to his new workload...
.. but he receives 'oracle-l updates' whenever we talk ;)
- Kirti
The instance should be listed in the oratab file, the listener.ora file and
the snmp_rw.ora file. It is automatically added to the snmp_ro.ora file at
agent start up.
Ensure that the Intelligent Agent is running. If any changes need to be
made to any of the previously mentioned files, stop and
this is why I gave up on OEM.
it sometimes discovers things and sometimes not. I just use Dba Studio now.
-Original Message-
[mailto:Reginald.W.Bailey;jpmorgan.com]
Sent: Friday, October 18, 2002 5:14 AM
To: Multiple recipients of list ORACLE-L
The instance should be listed in the
Hmm, thanks to all who are replying. It looks like the instance is not
making
it into either snmp_rw.ora, snmp_ro.ora or the services.ora. I have
manually
edited them, but when I restart the agent, it wipes out the manual entries
in
the snmp_ro.ora and the services.ora.
The oratab and listener
John,
Try this
On the client node:
1. Make sure all instances are in oratab listener.ora.
2. Stop the agent.
3. rm $ORACLE_HOME/network/agent/*.q
4. rm $ORACLE_HOME/network/agent/services.ora
5. rm $ORACLE_HOME/network/admin/snmp_r*.ora
6. start the agent
7. Check the pertinent log files in
LOL, don't I hear THAT all the time!
-Original Message-
Thomas F
Sent: 18 October 2002 14:24
To: Multiple recipients of list ORACLE-L
this is why I gave up on OEM.
it sometimes discovers things and sometimes not. I just use Dba Studio now.
-Original Message-
Is this UNIX or Windows?
Where is your oratab file located and what is your ORACLE_HOME directory?
The discovery process looks in your oratab (which can be located anywhere as
long as the ORATAB environment variable is defined) or the Windows registry
to locate all of the ORACLE_HOMEs that are in
seem to discover 1 instance
Date: Fri, 18 Oct 2002 05:38:37 -0800
Hmm, thanks to all who are replying. It looks like the instance is not
making
it into either snmp_rw.ora, snmp_ro.ora or the services.ora. I have
manually
edited them, but when I restart the agent, it wipes out the manual entries
When you do a lsnrctl status is there anything different for the instance that isn't
discovered and the ones that are?
-Original Message-
Sent: Friday, October 18, 2002 9:39 AM
To: Multiple recipients of list ORACLE-L
Hmm, thanks to all who are replying. It looks like the instance
Er, what I meant to say in my last email is to delete the node from OEM and
then rediscover all of the databases on it fresh.
Mike
From: John Weatherman [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Subject: RE: OEM can't seem
Scrap OEM. Seriously, we ran into way too many of these little annoying problems. We
decided that we had better things to do with our time. Have you had to re-register all
of your jobs, yet? That one was a real pain.
Jay
[EMAIL PROTECTED] 10/18/02 09:38AM
Hmm, thanks to all who are
I agree with Jay. Everytime I use OEM there are 10 or 20 annoying
little things that make it incredibly frustrating to use.
Jared mentioned a while back that the new product manager for OEM is on
this list. Maybe he could set up something (like a *big* mailbox) to
take suggestions for
Check the log files in the log directory. If the agent fails to log into
the instance, it will be in the log files. They are found at
$TNS_ADMIN/network/log.
The agent will always wipe out the snmp_ro.ora and services.ora files upon
restarting. It should include entries from oratab and the
Beth,
I heard that the new project manager is Gaja. We can expect a better
product from him and his team.
Ruth
- Original Message -
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Sent: Friday, October 18, 2002 11:54 AM
I agree with Jay. Everytime I use OEM there are 10
Gaja is the new project manager. some of the people also working on the
product are John Beresniewicz and (I believe) James Morle.
Should be a really good product when they are done with it
--- Ruth Gramolini [EMAIL PROTECTED] wrote:
Beth,
I heard that the new project manager is Gaja. We
Gaja is not active on the list due to his new workload...
... but he receives 'oracle-l updates' whenever we talk ;)
- Kirti
-Original Message-
Sent: Friday, October 18, 2002 10:54 AM
To: Multiple recipients of list ORACLE-L
I agree with Jay. Everytime I use OEM there are 10 or
Anybody seen anything like this? I am running 9.2.0.1 OEM auto discovery.
The Intelligent Agent is running on the target node. For some reason, it
seems unable to discover 1 instance, the other 3 on that node are found.
TNS seems ok, I can connect to the instance from other boxes without any
Are there entries in your oratab for this instance? After adding this
entry, if not there, recycle the IA and try again.
Phil Wilson ([EMAIL PROTECTED])
DBA, Operations Group
SkillSoft, Learning Solutions for the Human Enterprise
506.462.1124(w)
506.447.0334(c)
-Original Message-
It is in the oratab. I have cycled several times
John P Weatherman
Database Administrator
Replacements Ltd.
-Original Message-
Sent: Thursday, October 17, 2002 4:50 PM
To: Multiple recipients of list ORACLE-L
Are there entries in your oratab for this instance? After adding this
Title: RE: OEM can't seem to discover 1 instance
John I had the same issue recently where before the same instance
had been discovered. I had deleted the node after having removed
one instance from the server. Before it discovered all three and
now it discovers only one of two. Go figure. I
John;
At my last job (2 years ago, sorry for the lack of retention of memory)
there were files that were created in the (I believe) network/agent
directory. I think these were the .q files. We had an issue with OEM not
discovering an instance as well. Oracle told us to remove the files and
I believe that the instance needs to be in both the oratab and the
listener.ora files.
Mike
From: Kevin Lange [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Subject: RE: OEM can't seem to discover 1 instance
Date: Thu, 17 Oct 2002 13
Also, make sure your services.ora in the network/agent directory is correct.
-Original Message-
Sent: Thursday, October 17, 2002 4:44 PM
To: Multiple recipients of list ORACLE-L
John;
At my last job (2 years ago, sorry for the lack of retention of memory)
there were files that were
I believe that it needs to be in oratab, listener.ora, and services.ora
The services.ora is the one that gave me problems last week.
Tim Boles
- Original Message -
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Sent: Thursday, October 17, 2002 1:10 PM
Anybody seen
26 matches
Mail list logo
