You find that Lotus Domino® or Lotus Notes® crashes, sometimes repeatedly, and the Fatal Thread in the NSD identifies the "DBDLookup" function.
Sample Fatal Thread:
 --- called from signal handler with signal 10 (SIGBUS) ---
 fe4adcb0 LookupItem (e172f0, 0, 1, c8e79fa4, c8e79f80, 1) + 580
 fe4ad4a0 DBDLookup (e172f0, 154afc4, 1, 1, 2, 0) + 3f4
 fe4ac64c DBDPerformFunction (54290, e17370, 0, 5, c8e7a34c, c8e7a4dc) + c8
 fdf54678 DBDFunction (fe4aec14, b7b28f5c, 6, 0, c8e7a348, c8e7a4d8) + b28
Using the @DbLookup function with the [RETURNDOCUMENTUNIQUEID] keywords parameter causes this crash.
While the issue was initially linked to cases in which a returned UNID referenced a save/replication conflict, it was also found that garbage detail was being returned instead of the expected UNID list. For additional details about this problem, refer to Document #1244598, "@DbLookup with [ReturnDocumentUniqueID] returns only one UNID or numerous incorrect UNIDs."
NOTE: It is possible that a similar crash can occur in Notes, especially with local databases.
This issue was reported to Quality Engineering as SPR# DJOE69PDXC. The issue no longer occurs in Notes/Domino 6.5.5 and later releases. Starting in Notes/Domino 6.5.5, the usage only returns a single UNID even if it should return a list of UNIDs. While this change in behavior may avoid the crash, it can also cause applications to not function as expected.
To avoid the crash as well as the undesired behavior (specific to 6.5.5 and later), do not use @DBLookup with [RETURNDOCUMENTUNIQUEID]. Instead, create a View column with the formula, @Text(@DocumentUniqueID), and have @DBLookup return that column's data. Note: If you do not want the UNID to appear in the view, create a second hidden view that contains only the key column and the UNID column.
Refer to the Upgrade Central site for details on upgrading Notes/Domino.
Use of the @DBLookup function with the [RETURNDOCUMENTUNIQUEID] keywords parameter can also cause the Domino server to crash when the function is used in a web application. In a reported case, @DBLookup was used within a hotspot formula in a form design. When a document was created or opened, the Domino server crashed. This issue was reported to Quality Engineering as SPR# CYII633UWJ and was fixed in Notes/Domino 6.5.5. It has not been determined if the fix resulted in the undesired behavior where the function only returned one UNID instead of a list of UNIDs.
|Messaging Applications||Lotus End of Support Products||Not Applicable||Linux, Mac OS, Windows||6.5.4, 6.5.3, 6.5.2, 6.5.1, 6.5, 6.0||All Editions|