Post was stopped due to ORA-00942 and the debug revealed further that it was a horizontally partitioned table on which it stopped.
The Shareplex internal table shareplex_partition had a wrong entry for target schema
The config file entry for the partitioned replication was correct and was as follows:
sp_ctrl (sjracth11-vip:29010)> view config to_gw9i_gw10g.cfg
Datasource:o.RCTS1_SPLEX
#Source Table Destination Table Routing Map
TAHOE.CDR GW.CDR !CDR_SCHEMA1
! gdbsj4gwsplex@o.gwdb1
However, the entry for the columns TARGET_TABLE_OWNER and TARGET_TABLE_NAME for the Shareplex internal table SHAREPLEX_PARTITION was TAHOE and CDR respectively whereas it should have been GW and CDR. So as is seen here, instead of providing the value for target schema in SHAREPLEX_PARTITION table, the customer provided the value for the source schema. The customer later changed the value for TARGET_TABLE_OWNER to GW in this internal table by logging as a DBA user after shutting down Shareplex and committed the change. After restart of Shareplex and Post, the replication was fine.
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center