Return
-
Title
How to handle DDL changes with SharePlex. -
Description
If DDL changes are made to an object that SharePlex is replicating, steps need to be taken to ensure that replication is still possible.Before making any changes, check the SharePlex Release Notes for your version to see if the change will be handled by SharePlex.If the change is outside the scope of DDL replication, use the following procedure. -
Cause
SharePlex needs to know the exact structure of the objects it is replicating.DDL replication handles many changes but there are changes that SharePlex does not handle or support.Refer to the SharePlex Release Notes for a list of unsupported DDL changes. -
Resolution
Steps to ensure DDL changes to an object that SharePlex is unable to replicate:1. Make a copy of the current config file and edit the copied config file so that the DDL object is excluded from replication.2. Quiet the Source system for the relevant object.3. Activate the copy config file, this will exlcude the object from replication.4. If the Target object is changing, check the Target Post queue is empty so the Target object is not being updated.5. Make DDL changes to the object on Source and Target as required.6. Activate the original config file, this will bring the object back into replication with the new DDL changes.NOTE: If supplemental logging is off at the Oracle level on Source the object will need to be analyzed but this will not apply to the other objects in replication.7. Resume user activity on Source.NOTE: Between points 3 and 6, the object is not being replicated.Any updates on Source will not be replicated.