Oracle Access Manager Server Fails to Deploy From Weblogic
(Doc ID 1485451.1)
Last updated on FEBRUARY 01, 2019
Applies to:
Oracle Access Manager - Version 11.1.1.5.0 and laterInformation in this document applies to any platform.
Symptoms
Oracle Access Manager(OAM) Server Fails to Deploy From Weblogic
- OAM server fails to deploy from weblogic console, but can startup from command line
- Oracle 11g database j2db is available...
- Oracle 11g database asdb is available...
- Oracle 11g LISTENER is running...
- Oracle 11g LSNR_EXTPROC is running...
- OAM Node Manager is running...
- OAM WebLogic Administration Server is running...
- OAM WebLogic Managed Servers are running...
- OID WebLogic Administration Server is running...
- OID WebLogic Managed Servers are running...
- All OID OPMN Process are running...
- F/R WebLogic Administration Server is running...
- All F/R WebLogic Managed Servers are running...
- All F/R OPMN Process are running...
The Summary of Servers on the OAM WebLogic Server Administration Console shows that both the AdminServer and the oam_server1 servers are running.
However, the Summary of Deployments on the OAM WebLogic Server Administration Console shows that the oam_server is in a “Failed” state.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |