-
Title
Activation for horizontal partitioning fails with "All routing maps in a partition scheme must al -
Description
When activating a config involving horizontal partitioning, it fails with:
sp_ctrl>activate config CONFIGFILE
All routing maps in a partition scheme must also be listed on a line
in the configuration file. (Scheme: VENKY_TEST)(Route:
servername1@o.SID1+servername2@o.SID2+servername3@o.SID3)
The config file named CONFIGFILE contains the following:
Datasource:o.MAILMGR
MAILMANAGER.VENKY_TEST MAILMANAGER.VENKY_TEST !VENKY_TEST
! servername1@o.SID1+servername2@o.SID2 -
Cause
The route specified in the config file is inconsistent with the content of the Shareplex internal table SHAREPLEX_PARTITION.
-
Resolution
When implementing Horizontal Partitioning, one needs to pay special attention when specifying the route. If the route is specified somewhere in a config file, then it need not be specified by a placeholder using the exclamation (!) sign. Otherwise it needs to be specified vide this placeholder option. The error we are seeing is due to the fact that the content of the ROUTE field in the Shareplex internal table SHAREPLEX_PARTITION corresponding to the field SCHEME VENKY_TEST does not match with what is specified in the placeholder. Here are the details.
The route specified by us for the scheme VENKY_TEST in the config file (using placeholder option) is:
! servername1@o.SID1+servername2@o.SID2
Whereas the content of the ROUTE field in the internal table SHAREPLEX_PARTITION corresponding to the value of VENKY_TEST contained in the field named PARTITION_SCHEME is:
SQL> select route from shareplex_partition;
ROUTE
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
servername1@o.SID1+servername2@o.SID2+servername3@o.SID3
The placeholder entry (the line starting with "!" ) in config file was corrected so that it matched the value of the ROUTE field as below:
Datasource:o.MAILMGR
MAILMANAGER.VENKY_TEST MAILMANAGER.VENKY_TEST !VENKY_TEST
! servername1@o.SID1+servername2@o.SID2+servername3@o.SID3
After this anomaly was corrected, the config activated fine. -
Additional Information
The following excerpt from the Shareplex Admin Guide elaborates on what is meant by placeholder routing map:
To enter placeholder routing maps
All routing maps in a partition scheme must also be listed on a line somewhere in the
configuration file itself, in order for SharePlex to build its routing list. The requirement
usually is satisfied because partitioned replication generally is combined with full-table
replication. When using a route in a partition scheme but not in a regular (non-partitioned)
configuration entry, you must provide a placeholder routing map for that route
on a configuration line so that it is incorporated into the routing list.
If all routes used in your partition schemes exist on a line somewhere in the configuration
file, placeholders are not required, and you can close and save the configuration
file. Otherwise, do the following:
1 Press Enter to start a new configuration line.
2 Type an exception marker (!).
3 Type at least a few spaces or, if you are using tabs to maintain columns, tab to the
second or third column.
4 Type the routing map* using one of the following methods.
FIGURE 12: Routing formats
Basic routing map targetsys@o.targetSID
Compound routing map
targetsys1@o.target_SID1 + targetsys2@o.target_SID2
Routing map with named export queue
source_sys:queue_name*targetsys@o.targetSID
Routing map with named post queue
targetsys:queue_name@o.targetSID
If you are using default (not named) queues, use a basic routing map or a compound
routing map, depending on how many target systems you are listing.
Or...
If you are using named queues, use the appropriate syntax as shown in Figure 12.