SPR

Technote

Problem:
Notes 6.x and 7.x:
In the case where the issue is observed even though Soft Deletions are not
enabled the issue has been attributed to the inclusion of ghost notes in the
unread table causing the count to be inflated. This issue was reported to
Quality Engineering as SPR# RMAS6KALCR, and is fixed in Notes 7.0.2.

Excerpt from the Lotus Noes and Lotus Domino Release 7.0.2 MR fix list
(available at http://www.ibm.com/developerworks/lotus):

Unread Marks
SPR# RMAS6KALCR - Deleting parent docs can cause a situation where if the
unread table contains a deleted note, it causes the unread count to be wrong.

Refer to the Upgrade Central site for details on upgrading Notes/Domino.

Marking all of the documents in the database as Read will resolve the issue,
but may work only as a temporary measure:

1. Open to a view containing all documents.
2. From the menu select View > Show > Unread only.
3. From the menu select Edit > Select All.
4. On the action bar select the Folder > Move to Folder.
5. Select the Create New Folder button. Call the new folder "Unread". Select
OK to close the name dialog.
6. Select the Add button to add the selected documents to the newly created
Unread folder.
7. From the men select Edit > Unread Marks > Mark All Read.
8. Close and then re-open the database.
9. Switch to the Unread folder.
10. From the menu select Edit > Select All, and then Edit > Unread Marks >
Mark Selected Unread. Note: DO NOT use the Mark All Unread option for this
step.
11. Once the documents appear as expected then you can remove the folder by
highlighting the folder and selecting from the menu: Actions > Folder Options >
Remove Folder.

Ghost notes, or ghost documents, are created as document place holders, as
necessary, during various operations or tasks such as replication. A typical
usage would be to act as a shell parent document in cases where the parent
document of a response document has been deleted. In this case the response
document is considered an orphan and the ghost note is created as a placeholder
(to help keep track of the children).


Notes 6.0.3-6.0.4 & Notes 6.5-6.5.2 directly related to the use of Soft
Deletions:
This issue was reported to Quality Engineering in SPR # MARO5VSMGS and has been
addressed in Notes 6.5.3/6.0.5 Client and Domino 6.5.3/6.0.5 Server.

Regarding the first scenario described above, where the unread count is faulty
after more than 350 documents were deleted:

- If the database resides on a server then both the server and client release
must be updated.
- In order to reliably repair databases exhibiting the issue it is suggested
that a new replica be created.

In addition, if the database is replicated then it is recommended that the
unread replication functionality be enabled. This setting is on found on the
beanie tab (last tab on right) of the Database Properties. For the "Replicate
Unread Marks" option select "All Servers" if local replicas or non-clustered
server replicas will be in use.

Excerpt from the Lotus Notes and Domino Release 6.0.5 and 6.5.3 MR fix lists
(available at http://www.ibm.com/developerworks/lotus/):

Client UI
SPR# MARO5VSMGS - Fixed a problem where a large amount of deleted messages
(>400) were not removed from the unread table.

Workarounds for the Above (or other) Scenarios where the Unread Count is not
Updated as Expected:

First, open the Trash folder and mark any documents in it as Read, then empty
the Trash.
Then, purge the deletion stubs as follows:
1. Select File > Replication > Settings > Space Savers.
2. Set the "Remove documents not modified in the last XX" days to 0. Do not
enable/select the property's checkbox.
3. Close and re-open the database.

If purging the deletion stubs does not result in a corrected unread count or
trigger the unread counts to be updated as expected when deleting additional
documents, then create a new replica of the database.

Note:
- Simply marking the documents in the Trash folder as Read will not actually
resolve this issue - it is only a temporary workaround.

- Workarounds involving marking all documents as read, and then optionally
marking selected documents as unread, are not applicable to the folder unread
count issue described in this technote.


Alternatives:
The following workarounds, though likely less desirable, may warrant
consideration in some cases:

Disable soft deletions for the database
Disable the unread mark count feature for folders in the outline. For more
information refer to the document, "How to enable or disable the unread count
for folders" (#1087629).
More >