My Oracle Support Banner

OAM Upgrade, Certain Changes in Primary Server Are Not Replicated To The Clone Server (Doc ID 2105390.1)

Last updated on OCTOBER 06, 2020

Applies to:

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

Symptoms

After upgrade MDC environment from OAM 11.1.2.2.0 to 11.1.2.3.0, certain changes are not replicated from Primary Server to CLONE.

Example:

Changes

Curl command shows APS is enabled on both the data centers with JSON response {"ok":"true"}

[oracle@oam1-Primary Server bin]$ curl -u weblogic 'http://<Primary ServerHOSTNAME>.<DOMAIN>:<PORT>/oam/services/rest/_replication/hello' Enter host password for user 'weblogic': {"ok":"true"}
[oracle@oam1-Clone bin]$ curl -u weblogic 'http://<CLONEHOSTNAME>.<DOMAIN>:<PORT>/oam/services/rest/_replication/hello' Enter host password for user 'weblogic': {"ok":"true"}
Replication agreement shows status as ACTIVE

[oracle@oam1-Primary Server bin] curl -u weblogic:****** -H 'Content-Type: application/json' 'http://<Primary ServerHOSTNAME>.<DOMAIN>:<PORT>/oam/services/rest/_replication/'
JSON Response: {"enabled":"true","identifier":"","ok":"true","pollInterval":"60","startingSequenceNumber":"101","state":"ACTIVE"}

 

Cause

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
Symptoms
Changes
Cause
Solution
References


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