My Oracle Support Banner

OAM 11g: Could not initialize class (Doc ID 1465797.1)

Last updated on MARCH 18, 2019

Applies to:

Oracle Access Manager - Version and later
Information in this document applies to any platform.
A race condition can cause OAM not able to instantiate bean as it may not find the policies as it rebuilds policycache. By the time policies are synced up the webgate has queried access server for policy evaluation.


Webgates cannot connect to the Access Server
Access server logs contain the following message

[APP: oam_server] Exception encountered while processing the request message. Exception EJB Exception: : java.lang.NoClassDefFoundError: oracle/security/am/proxy/oam/pbl/plugin/OAMProxyEngine

OAMSSA-05005: Journal entry for version {x} doesnt exist in instance



A runtime clean script was deletes the folder 
/Middleware/user_projects/domains/IDMDomain/servers/oam_server1/oam this 
folder contains the policycache which must be populated upon startup.
It is not necessary to delete this folder and doing so increases startup 
time as the cache is populated. While this cache is being built 
this error can occur.


To view full details, 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 a vibrant support community of peers and Oracle experts.