OAM Admin Console and OAM Server are Not Accessible After Upgrading Oracle Access Manager to 188.8.131.52.0 with Errors "ORA-00001", "Invalid OAM Keystore configuration"
(Doc ID 2228018.1)
Last updated on APRIL 05, 2020
Applies to:Oracle Access Manager - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 11g]
Information in this document applies to any platform.
Oracle Access Manager (OAM) has been upgraded from 18.104.22.168 to 22.214.171.124 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.
The similar error has been already reported as Windows platform specific issue, but the above issue happened on Linux platform.
<Document 2034769.1> OAM 126.96.36.199 (11gR2PS3) Admin Server Fails To Start after installation on Windows platform
<Document 2078116.1> OAM 188.8.131.52 Console Not Accessible After First AdminServer Startup, Log Shows "Invalid OAM Keystore configuration"
Upgrading OAM to 184.108.40.206.0
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