The OAM Managed Server Cannot Be Started From A Script

(Doc ID 1590926.1)

Last updated on SEPTEMBER 09, 2017

Applies to:

Oracle Access Manager - Version 11.1.1.6.0 and later
Information in this document applies to any platform.

Symptoms

The OAM managed server cannot be started from a script with other IDM stack components, but can be started moments later using the same command.

The customer in this cases uses an SH script to start their entire IDM environment.  This main script then runs individual startup scripts for each component. Each component starts successfully until the oam managed server fails with the no error. the last line seen in the logs is;

weblogic.kernel.Default (self-tuning)'> <> <> <0000K3BRpgMFw000jzwkno1I7t_h000002> <1377802620073> <BEA-149060> <Module oam-wlsagent-logout.war of application oamsso_logout [Version=11.1.1.3.0] successfully transitioned from STATE_NEW to STATE_PREPARED on server oam_server1.>

If the script to start the OAM managed server is then immediately run itself, the oam managed server is started.

Cause

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