Is it possible to issue a single copy command to sync multiple tables by running the copy command against a dummy config file? Say, equivalent of "compare config" where a single compare command run against a dummy config file syncs multiple tables that are contained within that config file.
Starting with Shareplex 7.0 and up, it is possible. The following is the syntax:
copy using <routing_file>
Where <routing_file> refers to a file similar in format to a config file without datasource on the first line like the configuration file and containing source and target table entries for tables to be sync'd, or put another way, it is a dummy config file. Another term used for routing_file is synchronization routing file.
If there are more than one datasource in that instance of Shareplex (a configuration that is very uncommon), then the following option needs to be used:
copy using <routing_file> for o.SID (where SID refers to the datasource or Oracle SID to which the tables belong, in case there are multiple datasources in that instance of Shareplex).
If there are replication going to multiple targets in the dummy config file, then the following option needs to be used:
copy using <routing_file> at <targat_hostname>@<target_sid>
The command can be used for a routing file that contains tables that are all in replication or none of them are in replication. There can be no mix and match. In case none of them are in replication, then the following option is used:
copy using <routing_file> force
Here are some limitations when using copy on a routing file:
The tables in routing file should not have referential integrity relationship between them as the copy syncs tables randomly. So either disable such constraints on the target for the duration of copy or do not sync such tables with copy using routing file.
If there are large # of tables in the routing file and if such tables themselves are large, then the Post will be disrupted (stopped) for a longer time. Moreover, since copy uses Oracle Export with consistent=y option, this may require adequate sizing of undo segments. Otherwise ORA-01555 (snapshot too old) will occur. For this reason, the routing file should be configured appropriately.