Activation fails with "Bad config file:..All routing maps in a partition scheme must also be list (4298433)

When activating a config involving horizontal partitioning, it fails with the following type of error messages:

02/08/08 15:04 Notice: New activation id 55 [sp_tconf/11327]
02/08/08 15:04 System call error: No such host (h_errno = 1) host: 10.11.143.74\q_uhs_mig_part1 [sp_tconf(rim)/11327]
02/08/08 15:04 Config compilation completed: datasrc - o.ULOOKUP; file - ULOOKUP_30.cfg
02/08/08 15:04 Bad config file: file - ULOOKUP_30.cfg; All routing maps in a partition scheme must also be listed on a line in the configuration file.  (Scheme: user_id_partition0)(Route: 10.11.143.74:q_uhs_mig_part1*sjcrulookup01.vip.sjc.ebay.com@o.ULOOKUP+10.11.143.74\q_uhs_mig_part1*sjcrulookup02.vip.sjc.xyz.com@o.ULOOKUP+10.11.143.74:q_uhs_mig_part1*sjcrulookup03.vip.sjc.xyz.com@o.ULOOKUP+10.11.143.74:q_uhs_mig_part1*
sjcrulookup04.vip.sjc.xyz.com@o.ULOOKUP+10.11.143.74:q_uhs_mig_part1*writeulookupsmf.vip.xyz.com@o.ULOOKUP+10.11.143.74:q_uhs_mig_part1*sjcrulookup05.vip.sjc.xyz.com@o.ULOOKUP)
02/08/08 15:04 Process exited sp_tconf  (for o.ULOOKUP) [pid = 11327] - exit(1)

The config file is not consistent with the contents of the internal table SHAREPLEX_PARTITION

For every table involved in horizontal partitioning, there is at least one entry in the Shareplex internal table SHAREPLEX_PARTITION and the # of such entries depend on the # of column conditions that are specified for that replicating table. The key column is named PARTITION_SCHEME and the row also has another column named ROUTE. So it can be said that every column condition on a replicating table is represented by a corresponding entry in SHAREPLEX_PARTITION table and that entry also has a field called ROUTE that represents the routing info about the target to which the table is being replicated vide that column condition.

Any routes that are specified in the field ROUTE should also be listed somewhere in the config file, either due to the same table being replicated via full-table replication or using a placeholder option if no full-table replication exists for that table. Not doing so would result in the above error. One needs to correct the problem by editing the config file to include an entry for the route somewhere in it (most likely in the placeholder entry), and then activate the config once again. 

For more information on how to set up horizontally partitioned replication, please refer to the Admin Guide Chapter titled "Preparing for Shareplex Replication" subsection "Configuration for horizontally partitioned replication".