Post stopped due to error and the following errors showed up in event_log:
sp_ctrl>show log reverse
Info 2017-02-14 08:52:12.567126 16040 1 Poster exited with code=1, pid = 26573 (posting from sourceSID, queue queue_name, to targetSID)
Notice 2017-02-14 08:52:12.495536 26573 1 Poster: Shutting down by request (posting from sourceSID, queue queue_name, to targetSID) [module opo]
Error 2017-02-14 08:52:12.305177 26573 3 s:3 Poster: [SP-OPO01001] Post process stopped due to missing column "SHAREPLEX_OPERATION_SEQ" on target table "SHA86"."CDCTABLE". <CAUSE> Target table "SHA86"."CDCTABLE" is missing column "SHAREPLEX_OPERATION_SEQ". This is often caused by the target structure table not matching either the source table structure or the Post object cache structure. <ADVICE> Compare the source and target tables and add column if it is missing. Otherwise dump the Post object cache and then compare it with the table structure. Next, either correct the target table structure or copy the latest object cache from the source to the target. See 'http://advice.shareplex.com/SP-OPO01001' for additional advice and support. (posting from sourceSID, queue queue_name, to targetSID) [module opo]
Notice 2017-02-14 08:52:12.185105 26573 3 s:3 Poster: ORA-00904: "SHAREPLEX_OPERATION_SEQ": invalid identifier (posting from sourceSID, queue queue_name, to targetSID) [module osp]
The following steps were performed when configuring a replication in a Change History (CDC) environment:
The source and target tables were created where the target table had the same structure as the source table.
The config file had the following content:
sp_ctrl>view config cdcconfig
#source tables target tables routing map
sha86.cdctable !cdc:sha86.cdctable email@example.comSID
The config file was activated but it ran into the above errors on target. The script add_change_tracking_columns.sql located in /proddir/util subdirectory (where proddir refers to SharePlex’ Product Directory) was not run on target. This script is instrumental in creating default metadata columns on target table for CDC replication.
Run the script add_change_tracking_columns.sql on the target database and activate afresh.