Notes/Domino Fix List
 |  |
| SPR # CCAY5UBN2B | Fixed in 6.5.6; 7.0.2; 6.5.5 FP3 release |  |
Product Area: Server Technical Area: Database Platform: Cross Platform
Lotus Customer Support APAR: LO16291
SPR# CCAY5UBN2B - Fixed a Server panic with the following error, "Panic: Assert(IsNullBBLOCK(dbdir->UpdateLinks.prev))". This was a problem with dbdirman not protecting the update queue. This is a subtle timing condition where 2 dbdirman queue entries collided and one overwrote the other, and has been fixed.
Technote Number: 1157534
Problem:
This issue was reported to Quality Engineering, and has been addressed in the
following releases:
Domino 6.5.2 Fix Pack 1
Domino 6.5.3 Fix Pack 1
Domino 6.5.4
Domino 6.5.5 Fix Pack 3 (FP3)
Domino 6.5.6
Domino 6.0.5
Domino 7.0.2
Refer to the Upgrade Central site for details on upgrading Notes/Domino.
Excerpt from the Lotus Domino Release 6.5.2 FP1 and 6.5.3 FP1 fix lists
(available at http://www.ibm.com/developerworks/lotus):
SPR# MCOO5MZSMG - Fixed a Domino server panic with OSBBlockAddr: Bad block
Handle. This problem has been fixed in 6.0.5, 6.5.4, 6.5.2 FP1, and 6.5.3 FP1.
Excerpt from the Lotus Domino Release 6.5.6, 7.0.2, and 6.5.5 FP3 fix lists
(available at http://www.ibm.com/developerworks/lotus):
SPR# CCAY5UBN2B - Fixed a Server panic with the following error, "Panic:
Assert(IsNullBBLOCK(dbdir->UpdateLinks.prev))". This was a problem with
dbdirman not protecting the update queue. This is a subtle timing condition
where 2 dbdirman queue entries collided and one overwrote the other, and has
been fixed. More >
Last Modified on 07/23/2016
Go back
|