Directory Server 6.2 - Possible Database Integrity Issues
By klemay on Apr 15, 2008
6642430: DB corruption (zero’d pages) when performing db2ldif against large 20GB ldif file.
The sunsolve record for this bug can be found at http://sunsolve.sun.com/search/document.do?assetkey=1-1-6642430-1.
This issue does not affect Directory Server 6.0 or 6.1 release so you
only need this fix if you are running Directory Server 6.2.
Directory Server Enterprise
Edition 6.2 is no longer available for download and Directory Server
Enterprise Edition 6.3, which includes a fix for this issue, will be
available for download early April. When upgrading to Directory Server
6.3 from 6.2 (not needed if you are on 6.0 or 6.1), make sure you
export the database (db2ldif) prior to the upgrade and then re-import
the database after the upgrade to fully re-initialize the database and
to ensure that no corruption issues remain.
Recommended patch or upgrade procedures:
Shut down each directory server instance, as described in Starting, Stopping, and Restarting a Directory Server Instance.
Perform an LDIF export of the database, as described in Backing Up to LDIF.
Install the hotfix for bug 6642430 on Directory Server 6.2, or upgrade your Directory Server 6.2 instance to Directory Server 6.3 once Directory Server 6.3 is available for download (early April). You will need to login to Sunsolve in order to see this bug description.
Re-initialize the database from the LDIF exported in step 2, as described in Importing Data From an LDIF File.
If you are running replicated instances of Directory Server, make sure you read Restoring Replicated Suffixes as well.