Data Is Always Stored on the Same Partition in Membership Database (262047)
The information in this article applies to:
- Microsoft Site Server 3.0
This article was previously published under Q262047 SYMPTOMS
When the Membership database is partitioned across multiple databases, data may always get stored on the same partition. For example, the following unique CN values are placed on the same partition because the first 16 characters are the same:
cn=aasd000a0a180005
cn=aasd000a0a180006
CAUSE
The hash algorithm used to determine the partition value only uses the first 16 characters. In the previous example, the same partition value is generated because the first 16 bytes are the same for each.
WORKAROUND
To work around this issue, do one of the following:
- Add a "must have" attribute of GUID to the custom class and change the naming attribute to GUID rather than CN?.
- Use a namespace-partition scheme rather than value partitions (separate containers and/or partitions for a specific series set of Macintosh addresses).
- Reverse the entries so that the unique characters are at the beginning of the RDN.
- Truncate or abbreviate the first set of characters for a known series of Macintosh addresses so that the objects are correctly partitioned when you use value partitions.
STATUSMicrosoft has confirmed that this is a problem in Microsoft Site Server 3.0.
| Modification Type: | Major | Last Reviewed: | 5/10/2000 |
|---|
| Keywords: | kbprb KB262047 |
|---|
|