When creating multiple ID Servers for multiple replication system domains, observe these guidelines:
Make sure all Replication Server and data server names are globally unique across domains.
By using unique names, you simplify your administration and prevent confusion, especially in the interfaces files, which contain network access information for servers.
Maintain unique names and distinct ID numbers to accommodate the future possibility of data transfer between domains (that is, merging of domains).
Provide a different range of database and Replication Server ID numbers for each domain.
Make sure the ID numbers of any additional domains are large enough so that they do not overlap with the ranges of the first domain. See “Example of assigning ID numbers”.
Make sure that replication definition names are globally unique within and between ID Server domains.
The ID number is increased each time a Replication Server or database is added to the replication system. By default, your first ID number for a data server is 101. For a Replication Server it is 16,777,317. The last possible ID number for a data server is 16,777,316. For a Replication Server it is 33,554,431.
If you are creating two domains, you could assign ID numbers according to Table 4-1.
Component |
First ID number |
Last ID number |
|---|---|---|
1st domain data server |
101 |
99,999 |
2nd domain data server |
100,000 |
16,777,316 |
1st domain Replication Server |
16,777,317 |
17,777,316 |
2nd domain Replication Server |
17,777,317 |
33,554,431 |
When you are installing an ID Server using the rs_init program, you can specify the Starting Replication Server ID and the Starting Database ID.
Make
sure your ranges do not overlap from one domain to another. Make your
ranges large enough so that ID numbers can never increase to the
next range. For example, a range of 99,999 accommodates nearly all
possible cases.
