When a config with wildcards is activated, any external tables is subsequently created and that conforms to the wildcard entry fail to activate with the following entries showing up in event_log:
Notice 2016-10-07 22:58:51.569000 6068 3392 Capture: Creation of table <external_table_name> (oid=249058) is not replicated: Cannot replicate external table (capturing from source_SID) [module oct]
Since we do not support replication of external tables, we can ignore the above messages. If the wildcard entries do not apply to any other valid tables (which SharePlex supports for replication) but only to external tables, then such entries can be removed from the config file as follows:
1. Make a copy of the currently active config file and remove the entries for external tables.
2. Activate the copy.
However, if a wildcard entry applies to a supported table which exists in the database or may be created in future, then the config file can be left unchanged so as to allow such supported tables to be brought into replication and the above messages can simply be ignored.
