OAM Admin Console and OAM Server are Not Accessible After Upgrading Oracle Access Manager to 11.1.2.3.0 with Errors "ORA-00001", "Invalid OAM Keystore configuration"
(Doc ID 2228018.1)
Last updated on SEPTEMBER 07, 2023
Applies to:
Oracle Access Manager - Version 11.1.2.0.0 to 11.1.2.3.0 [Release 11g]Information in this document applies to any platform.
Symptoms
Oracle Access Manager (OAM) has been upgraded from 11.1.2.0 to 11.1.2.3 as per the Upgrade Guide. The WebLogic Administration Server and the Access Manager Managed Server(s) start as RUNNING mode. But the OAM Administration console (application name: oam_admin) and OAM Server application (application name: oam_server) fail to start and are not accessible.
The Administration server log and its diagnostic log show the following during startup.
AdminServer-diagnostic.log:
The similar error has been already reported as Windows platform specific issue, but the above issue happened on Linux platform.
Similar issues:
<Document 2034769.1> OAM 11.1.2.3 (11gR2PS3) Admin Server Fails To Start after installation on Windows platform
<Document 2078116.1> OAM 11.1.2.3 Console Not Accessible After First AdminServer Startup, Log Shows "Invalid OAM Keystore configuration"
Changes
Upgrading OAM to 11.1.2.3.0
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 |