Post stopped with "Internal error: Poster exit on 9i ddl error due to ORA-00942" (4255620)

While replicating 9i Supported DDL, the following errors are observed on target Shareplex due to Oracle error ORA-00942:

:
02/12/09 21:59 Notice: ORA-00942: table or view does not exist. [sp_opst(osp)/942136]
02/12/09 21:59 Internal error: Poster exit on 9i ddl error due to ORA-00942: table or view does not exist. on COMMENT ON TABLE owner.table_name IS Data Pump Mast... [sp_opst (for o.SID1-o.R012 queue queue_name)/942136]
02/12/09 21:59 Process exited sp_opst (for o.SID1-o.SID2 queue queue_name) [pid = 942136] - exit(1)

The DDL is failing on target because the object does not exist on target.

The error is typical when replicating 9i Supported DDL (by configuring the parameter SP_OCT_REPLICATE_ALL_DDL to 1 on source). The error can happen if the 9i Supported DDL feature was enabled after the table was first created. The subsequent DDL to add comment on table replicated to the target and failed since the target table did not exist. Another possibility can be that the object was subsequently dropped from target. The problem can be resolved in one of the following ways:

A.On target ignore the DDL by configuring the parameter SP_OPO_STOP_ON_DDL_ERR to 0 for the time being and restart Post. From this point on all DDL errors will be ignored by Post. Once the Post is past the problematic DDL, the parameter can be reset to the default of 0 by the sp_ctrl command reset param <parameter name>. Keeping it enabled indefinitely is not a good idea. See SOL21396 for details. In brief:
sp_ctrl>set param SP_OPO_STOP_ON_DDL_ERR 0
To enable it back
sp_ctrl>reset param SP_OPO_STOP_ON_DDL_ERR

B.One can also configure the parameter SP_OPO_CONT_ON_ERR to ignore the Oracle error ORA-00942. See SOL277 for details.

C.If it was not an intent to replicate 9i Supported DDL (typically the DDL on non-replicating tables), then it may be worth disabling the feature by setting the parameter SP_OCT_REPLICATE_ALL_DDL to 0 on source. To do this:
sp_ctrl>reset param SP_OCT_REPLICATE_ALL_DDL (the parameter is live and will take place immediately).

D.Create the target table and restart Post.

There could be other reasons but the main point is that the target table does not exist so the DDL fails.