Re: can discover nodes but not databases

Barry,

I had this same problem yesterday on a new Oracle 9i install. The error message in the log for the agent indicated that the database wasn't being seen by the agent. It turned out that there was a DNS problem at the client site such that pinging servername.domain didn't work, but pinging servername without the domain name worked Ok. So I made this change in my listener.ora and tnsnames.ora files and it started working. Generally it is a good idea to delete the *.q files in the agent directory along with the services.ora file too. These get rebuilt when the agent starts up.

I found Metalink document id# 166935.1 to be helpful when I was doing my troubleshooting.

David Simpson
www.dotcomsolutionsinc.net

"bgt0990" <btighe_at_neometrics.com> wrote in message news:3d172eab$1_4_at_corp-news.newsgroups.com...
> I'm running OEM 2.2 with 8.1.7.0 Oracle on a win 2000 box.
>
> When I try to use OEM I can create a repository, and connect using
> sysman/oem_temp. When I "Discover Nodes" all I get is the node
information.
> I can ping it and check the properties on it, it's fine. However, I do not
> discover any databases no matter what I've tried so the whole thing is
> useless.
>
> Any clue why the agent would report the node without reporting the
database?
>
> The only clue I can give is that this used to work on this machine and at
> one point we lost a drive which necessitated restoring from a cold backup,
> When I reloaded Oracle on this machine I don't believe I asked it to put
on
> the sample database (scott/tiger) but just loaded what I thought we
needed.
> That was some time ago so I can't tell you what may have been different.
I
> certainly loaded Enterprise Manager and I assume that would give you all
the
> supporting modules.
>
> Thanks
> Barry
>
>
Received on Tue Jun 25 2002 - 16:08:54 CEST