OAM_ADMIN status is in failed status

classic Classic list List threaded Threaded
28 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Re: OAM_ADMIN status is in failed status

raja
Reply | Threaded
Open this post in threaded view
|

Re: OAM_ADMIN status is in failed status

raja
Hi Erman

I will perform the action plan as per metalink note. Also i have attached the admin server logs for your review.

Thanks
Reply | Threaded
Open this post in threaded view
|

Re: OAM_ADMIN status is in failed status

ErmanArslansOracleBlog
Administrator
Okay Raja. take those actions and update me.
Reply | Threaded
Open this post in threaded view
|

Re: OAM_ADMIN status is in failed status

raja
Hi Erman

Can i use two different version of JDK. One for OID and another one for OAM?

Thanks
Reply | Threaded
Open this post in threaded view
|

Re: OAM_ADMIN status is in failed status

ErmanArslansOracleBlog
Administrator
These are two seperate products.
So if you isolated them in terms of weblogic server , then you can use different(supported) jdk versions for each of them.
However, I didn't do it before.
Reply | Threaded
Open this post in threaded view
|

Re: OAM_ADMIN status is in failed status

Raja
Hi Erman

I used JDK-6u45 for OAM and i was able to configure OAM without any issues. And also i was able to successfully enabled Single Sign on for EBS 12.2.6

Not sure what is the issue with  JDK-1.7.0_141

Thanks again for your assistance.


Thanks
Raja
Reply | Threaded
Open this post in threaded view
|

Re: OAM_ADMIN status is in failed status

ErmanArslansOracleBlog
Administrator
java 1.7.41 has lots of security enhancements.
These enhancements sometimes create problems (if you don't play the game by its rules)
Probably, a security thing was blocking you.
anways, thanks for the update.
Reply | Threaded
Open this post in threaded view
|

Re: OAM_ADMIN status is in failed status

Amir Elgohary
In reply to this post by ErmanArslansOracleBlog
I have been in same error after fresh installation.
I tried the referenced  (Doc ID 2008417.1) and found that the configuration was correct.
After full day of searching I went beck to re-installation of OIAM and creating new domain and the error gone.
I'm using the java version included with OIAM downloads 1.7U80.
one issue I should mention, it might be the cause. in installation I pointed jrelog to jdk directory not the jre
12