Discovering EBS in OEM 12c fails

[waldi]

Hi, we're discovering EBS environment (2 database and 2 application server) in OEM 12c.

All prereqs should be fulfilled. E-Business Plugin deployed on Server and agents, correct agent version checked (12.1.0.4) and Prevalidate finishes with success.

Starting Discover fails on step "Register EBS" with following errors:

oracle.apps.ebs.amp.oms.discovery.discoverer.AppsDiscoveryException: oracle.apps.ebs.amp.oms.discovery.discoverer.AppsDiscoveryException: oracle.apps.ebs.amp.oms.discovery.discoverer.AppsDiscoveryException: Failed to discover Web Logic Doamin. Job Name=WLS Discover:UAT_fs1[Thu Dec 17 16:25:50 CET 2015], Job Id=271A9BA1AF1E1116E0534E1F16ACA8C9
Caused By: oracle.apps.ebs.amp.oms.discovery.discoverer.AppsDiscoveryException: oracle.apps.ebs.amp.oms.discovery.discoverer.AppsDiscoveryException: Failed to discover Web Logic Doamin. Job Name=WLS Discover:UAT_fs1[Thu Dec 17 16:25:50 CET 2015], Job Id=271A9BA1AF1E1116E0534E1F16ACA8C9
Caused By: oracle.apps.ebs.amp.oms.discovery.discoverer.AppsDiscoveryException: Failed to discover Web Logic Doamin. Job Name=WLS Discover:UAT_fs1[Thu Dec 17 16:25:50 CET 2015], Job Id=271A9BA1AF1E1116E0534E1F16ACA8C9
oracle.apps.fnd.oam.em.util.job.CommandException
Caused By: oracle.apps.fnd.oam.em.sdk.targetData.discovery.AppsDiscoveryException: Error while attempting to discover EBS on : UAT_UAT2( oracle_database )
Caused By: oracle.apps.ebs.amp.oms.discovery.discoverer.AppsDiscoveryException: oracle.apps.ebs.amp.oms.discovery.discoverer.AppsDiscoveryException: oracle.apps.ebs.amp.oms.discovery.discoverer.AppsDiscoveryException: Failed to discover Web Logic Doamin. Job Name=WLS Discover:UAT_fs1[Thu Dec 17 16:25:50 CET 2015], Job Id=271A9BA1AF1E1116E0534E1F16ACA8C9
Caused By: oracle.apps.ebs.amp.oms.discovery.discoverer.AppsDiscoveryException: oracle.apps.ebs.amp.oms.discovery.discoverer.AppsDiscoveryException: Failed to discover Web Logic Doamin. Job Name=WLS Discover:UAT_fs1[Thu Dec 17 16:25:50 CET 2015], Job Id=271A9BA1AF1E1116E0534E1F16ACA8C9
Caused By: oracle.apps.ebs.amp.oms.discovery.discoverer.AppsDiscoveryException: Failed to discover Web Logic Doamin. Job Name=WLS Discover:UAT_fs1[Thu Dec 17 16:25:50 CET 2015], Job Id=271A9BA1AF1E1116E0534E1F16ACA8C9

Any glue where to look? As it says "Failed to discover Web Logic Domain" i checked credentials but the are working.

Many thanks for any idea.
Regards
Stefan

[ErmanArslansOracleBlog]

Please send me the emoms.trc file

[waldi]

Thanks for quick response. Attached the part of emoms.trc when discovering was running and failed.

Thx
Stefan

emoms.zip

[ErmanArslansOracleBlog]

This is the FATAL error.

FATAL oam.job_command log.36 -  Exception:  Error while attempting to discover EBS on : UAT_UAT1( oracle_database )   Discovery Error:

This is the only fatal error , altough there are other errors, but the code could continue with that.

So we should concantrate on the fatal error.

The error is a little strange , as it should write "using schema: apps" at the end of the error line.

Do you supply the credentials for EBS connection?

Check these docs:

How to Set Credentials in Grid Control 12c for E-Business Suite Plug-in (Doc ID 1490884.1)
https://docs.oracle.com/cd/E24628_01/doc.121/e39873/T508706T601738.htm#amp_prefcred

[ErmanArslansOracleBlog]

I think that it is related with credentials, as the error you are getting is truncated.
It should be something like  "Error while attempting to discover EBS on : UAT_UAT1( oracle_database ) using schema : apps "

So there is no "using schema" there.. So maybe discover phase is running without credential, or it can not get the credentials..

[ErmanArslansOracleBlog]

Also take a look at these notes,

R11i / R12.0 / R12.1: Getting Started with Oracle Application Management Pack (AMP) for Oracle E-Business Suite, Release 12.1.0.1.0 (Doc ID 1434392.1)

[ErmanArslansOracleBlog]

Also install agents using vip addresses if you didnt do so.

[waldi]

Worked thru document Doc ID 1434392.1 and created all Credentials and set them as preferred credentials if possible.In case of EBS it's not because this has to be discovered first. At the current point it's not available in OEM and therefore no credentials can be set and tested.

Error is still the same,looks like i have to open a SR.

There is one thing i would like to add. We are running OEM 12.1.0.5 which is listed as supported. Nevertheless starting with EBS Plugin system reclaims that agent 12.1.0.5 is not supported. Therefore i "downgraded" agent to former version 12.1.0.4.

How is agent involved in discovery process and can this be an issue?

On another test system i loaded VM templates available from oracle for testing and there i installed agent 12.1.0.4 from the scratch without up-/downgrading and on this environment discovery was successful.

Thx
Stefan

[ErmanArslansOracleBlog]

The issue can be your downgrade move.

Read this one:
If the reason that have made you downgrade is the same as the explained scenario in this doc, then you could ignore it and continue.

Prevalidate Oracle E-Business Suites: Discovery Wizard Failing In OEM 12c (Doc ID 2079578.1)
Error : EMGC supports 12.1.0.4.0 and 12.1.0.3.0 agents only. Seems one or more agents are below 12.1.0.3.0. Please check above table and upgrade non compatible agents before performing EBS discovery.

=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Bug 21975249 : EBS PLUG-IN 12.1.0.4 PRE-VALIDATE FAILS ON AGENT VERSION 12.1.0.5
AMP 12.1.0.4 code was released and later also certified with EM 12.1.0.5.

SOLUTION

Ignore this validation failure. Please continue and do the discovery.  Cloud Control 12.1.0.5 is certified with AMP 12.1.0.4
This has been reported as a known issue in:
Bug 21975249 EBS PLUG-IN 12.1.0.4 PRE-VALIDATE FAILS ON AGENT VERSION 12.1.0.5

[Stefan]

Many thanks, this was exact the reason for our problem. I figured it out today as i dropped my EBS target out of the environment where it works, up-/ and downgraded the agent and startet the discover again. Got the same error, deleted all the agents and installed new 12.1.0.4 agents from the scratch and all worked fine again.
But it's nice to know that we can ignore the error on revalidation as we don't need to uninstall (and loose information) the current agents. We will upgrade them again to 12.1.0.5 and will see what happens.

Thx and regards
Stefan

[manjari]

Hi Erman,

I am trying to install AMP 12.1.0.4 on OEM 12c reles 4. But my discovery  and prevalidation also fails, I tried to reinstall the agents, but still  fails with err

.

Detailed discovery report:

[ErmanArslansOracleBlog]

You are doing something wrong. It can not see the standard class.
Which document are you following?

[ErmanArslansOracleBlog]

Check this.

It is not the same error, but look similar, as it is still related with java.lang.NoClassDefFoundErrorand EM 12C
EM 12c: Enterprise Manager 12c Cloud Control Deployment Procedure Fails Checking Prerequisites: java.lang.NoClassDefFoundError (Doc ID 1929766.1)

[ErmanArslansOracleBlog]

Also, check the directory permission as well as the group name of the OS user that you are trying to install the AMP.

[ErmanArslansOracleBlog]

REview following guide and make sure you don't skip any required steps.

Oracle® Application Management Pack for Oracle
E-Business Suite
Guide
Release 12.1.0.4.0
Part No. E57981-02

https://docs.oracle.com/cd/E24628_01/doc.121/e57981.pdf

[Shaik Mujeeb]

Hi Emran,

I have deployed agent on 4 servers (2 node rac 2 node ebs)

Added Cluster and Databases in cloud control.

when i am trying to prevalidate to discover the targer ebs it is getting failed. log showing below error.

Can you suggest for action.

[ErmanArslansOracleBlog]

Hi Shaik Mujeeb ,

What below error? I don't see any any errors below your question

Also , Please create a sepeate/"new" issue in this forum for your question ! Your issue-your case may be different..