When shareplex replicates tables' DDL, post will stop and exit for various ORA messages when there is a mismatch between source table's DDL structure and target table's DDL structure.
Target table does not have the same partition setup, and Shareplex replicates tables' ddl with SP_OCT_REPLICATE_DDL sets to 1 or 3 or SP_OCT_REPLICATE_ALL_DDL sets to 1. Since Shareplex is instructed to replicate tables' ddl, any changes on tables' ddl will be replicated to target, and poster will stop or report error and move forward when there is a mismatch between source table's ddl structure and target ddl's structure.
Depend on the mismatch between source and target, poster may throw different Oracle errors. For example: ORA-02149, ORA-04043, ORA-00904, ORA-00959
1. Make sure source and target tables' have the same table structure.
2. set param sp_opo_stop_on_ddl 0
This parameter instructs poster to continue when it encounters an ddl error. This will apply for all ddl error.
Although shareplex has been replicating tables' DDL, start from version 6.0 and higher shareplex starts replicating more features for tables' DDLs such as partition, drop and create indexes, etc. See suported and non-supported session in Shareplex Release for detail.
