The following entries are observed in the event log when Post stops due to error:
Error 2016-03-08 12:53:24.767109 16283 1712027392 s:9 Poster: [SP-OPO01002] Post process stopped due to DDL error ORA-02431: cannot disable constraint (SYS_C00256361) - no such constraint on SQL ALTER TABLE "OWNER"."TABLE_NAME" disable constrain.... <CAUSE> Post received a DDL error from the target database. Message:[subque/seq 9/182324348 seqno/offset 2416/292962040]. <ADVICE> While Post is stopped, fix the problem so that this error does not occur again. Then, manually execute the correct DDL on the target and restart Post. (Note: On restart, Post will skip the original DDL that caused the error.) To configure Post to continue processing after it receives
RESOLUTION 1:
Restart Post to let Post moves on and at a later time decide on enabling the constraint on the target table depending on the replication strategy followed.
RESOLUTION 2:
· Direct the Post to ignore the DDL error and move on and at a later time decide on enabling the constraint on the target table depending on the replication strategy followed. To do so set the parameter as below:
sp_ctrl>set param SP_OPO_STOP_ON_DDL_ERR 0
· Start post.
· This will direct Post to ignore the Oracle error ORA-02431 which is a DDL error. Once the problem message(s) have been ignored, undo the change and set the parameter to its default value of 1 by:
sp_ctrl>reset param SP_OPO_STOP_ON_DDL_ERR
· Then bounce (stop and start) the Post for the parameter change to take effect. It is not a good practice to have the Post ignore DDL errors indefinitely hence the parameter is changed to the default value of 1 as soon as possible.
