Simpler Navigation for Servers and Operating Systems
Completed: a much simpler Servers and Operating Systems section of the Community. We combined many of the older boards, so you won't have to click through so many levels to get at the information you need. Check the consolidated boards here as many sub-forums are now single boards.
cancel
Showing results for 
Search instead for 
Did you mean: 

OEM:discovery failed

Giada Bonfà
Frequent Advisor

OEM:discovery failed

Hi,
I was configuring OEM console.
I got this error:

discovery failed:VNI-4026:discovery failed:error while transferring services.ora from agent:4009
7 REPLIES
T G Manikandan
Honored Contributor

Re: OEM:discovery failed

Is the agent running?

check that the agent service is started


Revert
T G Manikandan
Honored Contributor

Re: OEM:discovery failed

Just check the attachment

T G Manikandan
Honored Contributor

Re: OEM:discovery failed

1 more
T G Manikandan
Honored Contributor

Re: OEM:discovery failed

Also check whether two agents are running

ps -ef |grep dbsnmp
T G Manikandan
Honored Contributor

Re: OEM:discovery failed

Not more than 2 attachments

I should get down to the forums etiquette
Giada Bonfà
Frequent Advisor

Re: OEM:discovery failed

Hi,
I have OMS on windows XP and the target database and the repository are un HP-UX server.
I can set up the OMS console but I still cannot discover any node because of the error.

I checked the agents and they are running.
What can I do?
What does /par mean?
lsnrctl dbsnmp_status \par

thank you
Osa Jousou
Occasional Advisor

Re: OEM:discovery failed

Relink the agent executables.