OAM upgrade, certain changes in Master not replicated to Clone

(Doc ID 2105390.1)

Last updated on MAY 02, 2017

Applies to:

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


After upgrade MDC environment from OAM to, certain changes are not replicated from Master to CLONE.
- New Application Domain created in Master gets replicated to Clone.
- Changes to existing policies DOES NOT replicated to Clone.
- New Host Identifier DOES NOT replicated over to Clone.


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

[oracle@oam1-Master bin]$ curl -u weblogic 'http://oam1-master.oracle.com:7001/oam/services/rest/_replication/hello' Enter host password for user 'weblogic': {"ok":"true"}
[oracle@oam1-Clone bin]$ curl -u weblogic 'http://oam1-clone.oracle.com:7001/oam/services/rest/_replication/hello' Enter host password for user 'weblogic': {"ok":"true"}
Replication agreement shows status as ACTIVE

[oracle@oam1-Master bin] curl -u weblogic:****** -H 'Content-Type: application/json' 'http://oam1-master.oracle.com:7001/oam/services/rest/_replication/201409040157218184'
JSON Response: {"enabled":"true","identifier":"201409040157218184","ok":"true","pollInterval":"60","startingSequenceNumber":"101","state":"ACTIVE"}



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