The target table is not getting data changes from source. The source and target tables have an entry in the currently active config file.
Most likely the source table has been dropped and recreated while still in replication.
Carry out the following steps to determine if this is the cause and take corrective action thereof:
1. Dump the object cache on source by the object id value of the problem table to see if the table forms its part. See SOL1771 for details. If this is the case, then the issue should be referred to support for futher investigation. If the source table is not a part of the object cache, then it is most likely dropped and recreated in the past (after the table was first included in replication). Use the following DBA view to see if it was created after the config file was first created (get the latter info from the output of Ã¢â‚list configggÃ¢â‚ from sp_ctrl):
select created,LAST_DDL_TIME from dba_objects where OBJECT_NAME="<TABLE>" and OWNER="<OWNER>";
2. Once it is confirmed that the table is not a part of the object cache, then the following should be done to bring the table back in replication:
a. Make a copy of the currently active config file, remove the table from it by commenting it out and activate the copy.
b. Activate the original config file that has the table in it.
c. Synchronize the table using compare repair, copy or any other means.
Another reason for seeing data not replicating to target table is when the parameter SP_OCT_GEN_STOP is enabled on source. This parameter controls whether the replication is enabled or disabled. If the parameter is disabled (having a value of 0x0 or 0x00000000), then replication is enabled and if the parameter has any other value, then the replication is diabled. But this enabling this parameter will impact all tables and not just our problem table. To see the current setting of the parameter, issue the command Ã¢â‚list param all captureeeÃ¢â‚ from source sp_ctrl.