for DDL replication, Replicat Sets Session To different schema than original one in source
Last updated on JULY 17, 2017
Applies to:Oracle GoldenGate - Version 188.8.131.52.6 and later
Information in this document applies to any platform.
In source, customer logged in as USER1 and issued an DDL.
The DDL was applied by replicat, and 'alter session set current_schema=USER2' was performed before applying the DDL, which cause error. USER1 is not mapped to USER2 in replicat.
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