Oracle Access Manager Upgrade 11.1.2.x to 126.96.36.199: .oamkeystore Remains Empty (0 Byte) when Starting Servers After Extending OAM Domain
Last updated on MAY 19, 2017
Applies to:Oracle Access Manager - Version 188.8.131.52.0 to 184.108.40.206.0 [Release 11g]
Information in this document applies to any platform.
Oracle Access Manager (OAM) Domain needs to be extended to upgrade OAM from 11.1.2.x to 220.127.116.11. A keystore file $DOMAIN_HOME/config/fmwconfig/.oamkeystore remains empty (0 byte) when starting servers after extending the OAM domain.
The keystore file is empty (0 byte) just after extending the domain. This is the expected behavior. The keystore file is recreated automatically during starting AdminServer after extending domain. However, the keystore file may remain empty during starting servers after extending the OAM domain in some environment.
If the keystore file is empty, OAM applications, which are "oam_admin" on AdminServer and "oam_server" on OAM managed servers, fail to start with the following keystore errors:
The OAM 18.104.22.168 or 22.214.171.124 has been upgraded to 126.96.36.199.
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