Sun Java System Directory Server 6.2 Database May Become Corrupted

---

Sun Java System Directory Server 6.2 Database May Become Corrupted

1. Impact

A race condition may cause database pages for Sun Java System Directory Server to not sync to disk, resulting in possible Directory Server database corruption. Depending on which pages are affected, the impact may vary.

2. Contributing Factors

This issue can occur in the following releases for all platforms (Solaris 8, 9, and 10 SPARC and x86 Platforms, Linux, Windows, HP-UX):

• Sun Java System Directory Server Enterprise Edition 6.2

Note: Directory Server 6.1, 6.0, 5.2 and 5.1 are not affected by this issue.

To determine if the Directory Server running on a system is affected, the following command can be used:

    $ dsadm -V

If the output contains the version string 6.2, the system is affected.

3. Symptoms

Depending on which database page is affected and which operation tries to access it, the resulting error messages can be different, but in the most frequent cases a message similar to the following is logged:

    DEBUG - conn=-1 op=-1 msgId=-1 -  libdb: PANIC: fatal region error detected; run recovery

4. Workaround

There is no workaround for this issue. Please see the Resolution section below.

5. Resolution

This issue is addressed in the following releases:

Native Package Versions:

• Solaris 9 and 10 with SPARC patch 125276-07 or later
  
• Solaris 9 x86 with patch 125277-07 or later
• Solaris 10 x86 and x64 with patch 125278-07 or later
• Linux with patch 125309-07 or later
• Windows with patch 125311-07 or later

PatchZIP (Compressed Archive) versions:

• Solaris 9 and 10 with SPARC patch 126748-04 or later
  
• Solaris 9 x86 with patch 126749-04 or later
  
• Solaris 10 x86 and x64 with patch 126750-04 or later
  
• Linux with patch 126751-04 or later
  
• Windows with patch 126753-04 or later
  
• HP-UX with patch 126752-04 or later

Note: After patches have been applied: Since the database corruption can be present but undetected, it is recommended to rebuild the database by exporting to an ldif file and reimporting the ldif file. In a replicated environment, all servers need to be rebuilt or reinitialized. Export/Import and initializing servers in a replicated environment is documented in the DSEE reference guide at:


This Sun Alert notification is being provided to you on an "AS IS" basis. This Sun Alert notification may contain information provided by third parties. The issues described in this Sun Alert notification may or may not impact your system(s). Sun makes no representations, warranties, or guarantees as to the information contained herein. ANY AND ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT, ARE HEREBY DISCLAIMED. BY ACCESSING THIS DOCUMENT YOU ACKNOWLEDGE THAT SUN SHALL IN NO EVENT BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES THAT ARISE OUT OF YOUR USE OR FAILURE TO USE THE INFORMATION CONTAINED HEREIN. This Sun Alert notification contains Sun proprietary and confidential information. It is being provided to you pursuant to the provisions of your agreement to purchase services from Sun, or, if you do not have such an agreement, the Sun.com Terms of Use. This Sun Alert notification may only be used for the purposes contemplated by these agreements.

Copyright 2000-2008 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, CA 95054 U.S.A. All rights reserved.




Attachments

This solution has no attachment