My Oracle Support Banner

For DDL Replication, Replicat Sets Session To Different Schema Than Original One In Source (Doc ID 1270161.1)

Last updated on FEBRUARY 27, 2019

Applies to:

Oracle GoldenGate - Version 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.


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.