My Oracle Support Banner

Oracle Access Manager Upgrade 11.1.2.x to OAM Server Application Fails to Start After Upgrade Due to Incorrect Target Configuration for Library 'oracle.sdp.client' (Doc ID 2326038.1)

Last updated on APRIL 19, 2022

Applies to:

Oracle Access Manager - Version to [Release 11g]
Information in this document applies to any platform.


Oracle Access Manager (OAM) Cluster is removed from target for library 'oracle.sdp.client' during upgrading OAM from 11.1.2.x.x to As a result, the 'oam_server' application fails to start because it can not find the library 'oracle.sdp.client' as below;

{OAM Managed Server Name}.log:

In this case, "oam_server1" is not actual OAM server name. So, the OAM server (e.g. WLS_OAM1/WLS_OAM2) can not find the library 'oracle.sdp.client' and fails to start.


The issue may happen in the following conditions:

- A number of OAM servers are configured as cluster.
- OAM managed servers name are other than default 'oam_serverX'
- OAM is upgraded from 11.1.2.x to


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

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