The following DDL errors are observed when Post stopped due to error. However, no form of DDL replication is configured, meaning both SP_OCT_REPLICATE_ALL_DDL and SP_OCT_REPLICATE_DDL are set to 0.
Notice 2011-02-16 15:51:54.213000 4928 4920 s:2 Poster: ORA-02429: cannot drop index used for enforcement of unique/primary key. (posting from NAME1, queue queue_name, to NAME2) [module osp]
Error 2011-02-16 15:51:54.213000 4928 4920 s:2 Poster: Poster exit on 9i ddl error due to ORA-02429: cannot drop index used for enforcement of unique/primary key. on drop index OWNER.INDEX_NAME (posting from NAME1, queue queue_name, to NAME2) [module opo]
OR
Error 2011-02-12 06:24:34.587127 13392 3 s:2 Poster: Poster exit on 9i ddl error due to ORA-00955: name is already used by an existing object. on CREATE INDEX "OWNER.INDEX_NAME: ON "OWNER.TABLE_NAME" (posting from NAME1, queue queue_name, to NAME2) [module opo]
Notice 2011-02-12 06:24:34.586406 13392 3 s:2 Poster: ORA-00955: name is already used by an existing object. (posting from NAME1, queue queue_name, to NAME2) [module osp]
Create and drop index are replicated even when DDL replication is disabled. This happens when the auto-add feature of Shareplex is enabled (SP_OCT_AUTOADD_ENABLE is set to 1)
RESOLUTION:
To address the root cause so that the issue does not recur in future, disable the auto-add feature by configuring the following Capture parameter on source:
sp_ctrl>set param SP_OCT_AUTOADD_ENABLE 0
WORKAROUND:
To get post up and running, 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
sp_ctrl>start post
sp_ctrl>reset param SP_OPO_STOP_ON_DDL_ERR
