HP-UX Directory Server B.08.10.03 Release Notes (5900-2214, February 2012)

Table 1 Data not migrated when using the cross option
ImpactData
The replicated topology must be in synch before starting
the migration; otherwise, consumer replicas must be
reinitialized after migration.
Replica nsState attribute
Changelogs
No effectnsslapd-idl-switch attribute
Creates the possibility that a non-unique nsUniqueId
value could be generated. This is unlikely because of the
algorithm used for generating unique IDs.
The unique ID generator entry, cn=uniqueid
generator,cn=config
For more information on these attributes, see the HP-UX Directory Server configuration, command,
and file reference.
NOTE: If a supplier or hub is not fully synchronized with its consumers at the time of migration,
you must reinitialize all its consumers after migration.
4 Known problems that have been fixed
4.1 Known problems fixed in B.08.10.03
Table 2 Fixes in HP-UX Directory Server B.08.10.03
Description of corrected problemDefect
With audit logging enabled, under certain circumstances an information leak might occur.QXCR1001065568
If a supplier changelog is trimmed of changes and a stale LDIF is loaded into a consumer
replica, an inconsistent replication state might occur.
QXCR1001063264
Running the setup script setup-ds-admin.pl with the -k option (which saves a temporary
configuration setup cache file that can be reused for a silent setup) results with an invalid
QXCR1001047835
admin value in the cache file. Attempts to use this file to provide configuration settings for
a new directory server instance will fail.
4.2 Known problems fixed in B.08.10.02
Table 3 Fixes in the latest release of HP-UX Directory Server B.08.10.02
Description of corrected problemDefect
The log rotationinfo file is corrupted at startup. As a result, log files that were created
before the restart are not removed after they expire.
QXCR1000977427
4.3 Known problems fixed in B.08.10.01
Table 4 Fixes in HP-UX Directory Server B.08.10.01
Description of corrected problemDefect
The values of any createTimestamp, creatorsName, modifyTimestamp, and
modifiersName attributes specified in an LDIF file that is being imported are replaced
QXCR1000968533
instead of retained as expected. The creatorsName and modifiersName values are
replaced with empty strings, and the createTimestamp and modifyTimestamp values
are replaced with the current time. This issue also affects migration when performed using
LDIF exports (for example, when migrating from Netscape Directory Server 6.x).
The account policy plug-in uses the createTimestamp value to determine the account
inactivity limit if a loginTimestamp is not found. Thus, users imported using LDIF and
8