When a config with wildcards is activated, any table that that conforms to the wildcard entry and has a column of the type UROWID fail to activate with the following entries showing up in event_log:
Warning 2016-10-06 13:55:05.856000 15316 13456 Activation: Column COLUMN_NAME type UROWID - cannot replicate this type. Skipping wildcard match ("OWNER"."TABLE_NAME") (activating sid source_SID) [module ocf]
Since we do not support replication of tables with type UROWID, 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 tables with UROWID columns, 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.
Note:
Starting with SharePlex 9.2, support has been added for the Oracle UROWID data type. This support applies to Oracle-to-Oracle configurations only.
