There are occasions when some DDL may get replicated to target and can cause Post to stop due to error. Unless the underlying cause is addressed or the DDL removed from the queue, Post will not move forward. This can cause undue delay in posting of the remaining data changes that occurred on source.
This solution delves on the question of whether it is possible to have SharePlex configured to selectively ignore certain DDL errors and not ignore the rest of the DDL errors.
It is possible to have SharePlex ignore some of the DDL errors while not ignore the rest. This can be done by configuring the oramsglist file located in $SP_SYS_VARDIR/data directory. For details on configuring this file, see Shareplex Reference Manual Chapter titled “Shareplex Parameters” section titled “Post Parameters” and look for details on the parameter SP_OPO_CONT_ON_ERR. The parameter can be configured to ignore both DDL and DML errors. Please be aware that once a certain Oracle DDL is set to be ignored, from that point on this type of DDL will be ignored for all tables that encounter this DDL error. It cannot be set for some tables and not set for others.
Another thing to keep in mind is that the parameter should be unset once the problem point is passed. Since one may want to have Post stop on such errors so as to have more control over it and also be able to investigate the cause of such problems in a proactive manner.
If one wants to ignore all DDL, then one may want to configure the parameter SP_OPO_STOP_ON_DDL_ERR to 1. This parameter is also described in the same Chapter in Reference Manual.
The cause for such erroneous DDL may be enabling of 9i supported DDL feature on source (by turning on the parameter SP_OCT_REPLICATE_ALL_DDL to 1), applying DDL independently on source and target replicating tables, etc.