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

Steve

unread,

Jun 1, 2005, 4:27:13 PM6/1/05

to

Hi,
Strange issue. When logging into a local EM session can see a server
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.

Matthias Hoys

unread,

Jun 1, 2005, 4:46:24 PM6/1/05

to

"Steve" <sau...@hsius.com> wrote in message
news:1117657633.4...@g43g2000cwa.googlegroups.com...

There must be something wrong with the discovery of the services done by the
"Intelligent" Agent on the server. Try restarting the agent (agentctl
stop/start) and check the services.ora file under ORACLE_HOME/network/agent
(or /admin, can't remember).

HTH
Matthias

Steve

unread,

Jun 1, 2005, 5:10:06 PM6/1/05

to

Thanks for your Reply Matthias ! Am checking this now. Steve.
Unfortunately can delete, the discover nodes with the result that it
finds the node, finds the http server but does NOT find the listener or
database. Am looking at the services.ora file but nowhere is there an
entry for the new node.

Steve.

Matthias Hoys

unread,

Jun 1, 2005, 5:48:33 PM6/1/05

to

"Steve" <sau...@hsius.com> wrote in message

news:1117660206....@g14g2000cwa.googlegroups.com...

Did you try to restart the agent on the server ? Any errors ? There are also
errors under $ORACLE_HOME/network/log which might help you finding the cause
of the problems. Are the databases listed in the /etc/oratab file ?

Matthias

nitin...@rediffmail.com

unread,

Jun 2, 2005, 12:58:06 AM6/2/05

to

hi ...Do you work on windows..what u need to check is whether the
preffered credentials are set properly...ur network settings(if you are
trying to dicover node of other machine).Try and restart the
service.Also if you manually configure the node,then you would not see
that database in jobs list...OMA has to discover it automatically.

regards

Holger Baer

unread,

Jun 2, 2005, 3:29:45 AM6/2/05

to

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

Pete's

unread,

Jun 2, 2005, 9:29:05 AM6/2/05

to

Version of EM & Databases involved would be nice, however, I ran into a
similar situation with 9.2 version of EM and oracle apps 11.5.7(uses
9.2.0.? db) instance. I too could see the sever & listener but not the
database. The oracle apps install wizard junk names the listener for
the db the same name as the db. The emagent had problems with it.
After hours conversing with support, the fix was to rename the listener
to something other than that of the db name.

HTH,
Pete's

Steve

unread,

Jun 2, 2005, 11:56:53 AM6/2/05

to

Many thanks for all your help on the psychic oracle hot-line who indeed
knew that with 9.2 OEM on a W2k box connecting to 9.2 on a Red Hat
server the listener had to be renamed and voila .... the db, listenter,
and node now show up !
Running a backup job produces the VNI-2015 error which we are presently
trying to resolve.
Best Regards, Steve.

Steve

unread,

Jun 2, 2005, 2:21:20 PM6/2/05

to

The VNI-2015 error is gone. Just a matter of setting node credentials
(we used sysman) vs database credentials and also making sure the node
credentials match a user on the Red Hat server who has root access.
Thanks again.

Matthias Hoys

unread,

Jun 2, 2005, 3:37:38 PM6/2/05

to

"Holger Baer" <holge...@science-computing.de> wrote in message
news:d7mcha$8ie$1...@news.BelWue.DE...

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

Holger Baer

unread,

Jun 3, 2005, 2:41:25 AM6/3/05

to

Matthias Hoys wrote:
>
>
> 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
>

Funny thing: The documentation tells exactly this to be the case, however, I did
just shutdown the intelligent agent, remove one entry from listener.ora, remove
the services.ora, start intelligent agent. The removed service does not appear
in the services.ora.

So to believe is fine. My experience however, differs.

And yes, this db was created with dbca, only two days ago. But to be fair, in the
listener.ora is one service listed, that no longer exists. So maybe the entries
in listener.ora *and* registry have to match to be listed. (Not starting a myth
here, I hope).

This was tested on windows 2000 with Oracle 9.2.0.6

Cheers,
Holger