Till today, you have seen my all articles that show DML replication Golden Gate. I, U, D [Insert update and delete] three main operations which are replicated in Golden Gate.

But, Golden Gate supports DDL replication too. It supports DDL synchronization from one database to another.

Let us first see requirement and restrictions of DDL replication in Golden Gate :

ASSUMETARGETDEFS must be specified at the target, means source and target object definition must be identical.

When Extract data pump is being used, tables for which DDL is being replicated must be configured in passthru mode. DDL filtering, manipulation and error handling is not supported by a data pump.

User exit functionality is not supported with DDL synchronization.

Limitations we have allowed in Table and Map statements for characters are inherited for DDL.

Objects created with Oracle reserved words are ignored while replicating DDL.

While running ddl_setup.sql if that tablespace is shared by other users than Golden Gate owner user, that script will fail.

Golden Gate supports synchronization of TRUNCATES as a stand-alone function or as part of full DDL  synchronization. If you are using DDL synchronization, disable stand-alone TRUNCATE synchronization to avoid error caused by duplicate operations.

Oracle allows only 18 characters for a rename because of the ANSI limit for identifiers so, if you rename a table with ALTER TABLE RENAME and table name is longer than  18 characters that statement fails.

DDL capture and replications are allowed up to 2 MB in length, longer DDL that 2 MB in length are not allowed

If you want to be updated with all our articles send us an Invitation or Follow us:

Telegram Channel: https://t.me/helporacle

Skant Gupta’s LinkedIn: www.linkedin.com/in/skantali/

Joel Perez’s LinkedIn: Joel Perez’s Profile

LinkedIn Group: Oracle Cloud DBAAS

Facebook Page: OracleHelp


About The Author

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.