Oracle Access Manager Upgrade 11.1.2.x to 11.1.2.3: .oamkeystore Remains Empty (0 Byte) when Starting Servers After Extending OAM Domain (Doc ID 2266508.1)

Last updated on SEPTEMBER 14, 2023

Applies to:

Symptoms

Oracle Access Manager (OAM) Domain needs to be extended to upgrade OAM from 11.1.2.x to 11.1.2.3. 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:

AdminServer.log:

Changes

The OAM 11.1.2.0 or 11.1.2.1 has been upgraded to 11.1.2.3.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.