Thanks for the suggestion, Vikas - and thanks to everyone else.
Alas, I tried Vikas's suggestion, but OEM still can't discover the node.
I'm a bit reluctant to upgrade the Agent on the 8.0.6 server to the 8.1.6
Agent, since I understood Oracle recommends you use the version of Agent
which matches the version of your core installation, which on the server
concerned is Oracle 8.0.6 Server.
I think for the time being I'll resign myself to configuring the node
manually in OEM - it's no great hardship, really!
Thanks again to everyone who offered suggestions and advice.
Paul
------------------------------------------------------------
Paul Vincent
Database Administrator, University of Central England
------------------------------------------------------------
> -----Original Message-----
> From: Vikas Kawatra [mailto:[EMAIL PROTECTED]]
> Sent: 07 June 2001 19:11
> To: Multiple recipients of list ORACLE-L
> Subject: RE: OEM 2.1 cannot contact agent on a node
>
>
> * Stop the agent on the remote node
> * delete all the q files
> * on the OEM side , remove all the databases from the node in
> question.
> * start agent on the remote node
> * rediscover the node on OEM
>
> The steps above should solve the problem
>
> vikas
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Paul Vincent
INET: [EMAIL PROTECTED]
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
