OAM Admin Console and OAM Server are Not Accessible After Upgrading Oracle Access Manager to 184.108.40.206.0 with Errors "ORA-00001", "Invalid OAM Keystore configuration"
Last updated on FEBRUARY 27, 2018
Applies to:Oracle Access Manager - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 11g]
Information in this document applies to any platform.
Oracle Access Manager (OAM) has been upgraded from 22.214.171.124 to 126.96.36.199 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 188.8.131.52 (11gR2PS3) Admin Server Fails To Start after installation on Windows platform
<Document 2078116.1> OAM 184.108.40.206 Console Not Accessible After First AdminServer Startup, Log Shows "Invalid OAM Keystore configuration"
Upgrading OAM to 220.127.116.11.0
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms