The following warning messages are observed when a table fails to activate:
Warning 2017-01-03 14:12:28.659445 8584 1 Activation: Target table name portion of wildcard specification must be same as source or '%'. Skipping ("SHA86"."TABLE%") (activating sid ORA11GR2) [module ocf]
Here are the entries from the config file for problem table(s):
sp_ctrl (alvsupu15:5438)> view config wildcardconfig
#source tables target tables routing map
expand sha86.table% sha86.test% firstname.lastname@example.org
The following restriction applies when using wildcards:
The name of the objects on the source must be the same as the name of the objects on the target, but the objects may belong to different owners (or reside in different schemas).
In our case this requirement is not met hence the object fails to be brought into replication. It is not possible to activate objects in this manner. The only way to activate objects this way is to not use wildcards and specify individual entries for source and target objects in the config file.