Changing allocation of ID blocks to a replica

MultiSite controls how many record ID numbers are allocated to each replica. This allocation is done by using ID blocks (groups of IDs). Depending on the activity level of a replica family, you may want to increase the size of the ID blocks that are allocated to a replica to ensure that synchronization flows smoothly.

About this task

For example, with the default settings, if a synchronization packet contains enough new records that the receiving replica exceeds the number of IDs remaining in its current ID block, synchronization import fails. By default, each replica is given an ID block of 4096 IDs when it is created. When a replica reaches a threshold of 1024 IDs remaining, it is allocated another ID block of 4096 IDs. This ensures that all IDs are unique. ID block allocation is handled internally by the working schema repository during synchronization.

To control the number of IDs allocated to a replica, you can perform one of these tasks:
  • Use the –size and –threshold options when you create a replica with the mkreplica –export command. For example, to create a new replica with an actual ID block size of 25000 and a threshold of 50%, you would use the following command:
    multiutil mkreplica -export -clan telecomm -site boston_hub -family DEV 
    -u susan -p passwd –size 250 –threshold 50 –out c:\cqms\boston_hub.xml
    goldengate:sanfran_hub
    Multiutil: Packet file ‘c:\cqms\boston_hub.xml’ generated
    
  • Modify the size and threshold settings with the chreplica command. For example, to change all replicas in a site to have an actual ID block size of 50000 and a threshold of 30%, you would use the following command:
    multiutil
     chreplica -clan testclan -site boston_hub -user susan -p passwd 
    -host minuteman –size 500 -threshold 30 boston_hub