Technote Number: 1094741
Problem:
This issue can occur for two different reasons:
(1) Notes 5.0.13, 6.0.4, 6.5.1, and 6.5.2 clients accessing a mail file on a
Notes Domino 5.x server:
A regression issue has been discovered in relation to a fix made in SPR#
KHAN5QMMMC. Specifically, documents are not being removed as expected when you
manually archive documents, using one of the Notes Client releases noted above
and when the mail file is on a Domino 5.x server. This regression was reported
to Quality Engineering via SPR #BTLW5XYBD9 and has been addressed in Domino
6.5.3.
Excerpt from the Lotus Notes and Domino Release 6.5.3 MR fix list (available at
http://www.ibm.com/developerworks/lotus):
Mail Client
SPR# BTLW5XYBD9 - Corrected an issue with enforcement of $NoPurge item when
doing R5-style archiving, which could prevent the removal of documents from the
source database. This regression was introduced in 5.0.13.
Workaround:
If an earlier 6.0.x or 6.5 Notes Client release is not available, then the only
workaround is to create a local replica, archive the documents from it, and
then replicate back to the server.
For information on how to create a replica, refer to the Lotus Notes Help topic
"Creating Replicas".
(2) Using 5.x or 6.x:
The option "Do not delete documents that have responses" has been enabled on
the Advanced pane of the Archive Settings dialog box.
If the option "Do not delete documents that have responses" is enabled,
documents that have responses (also known as parent documents) can be copied to
the archive, but they will not be removed from the original database if their
response documents are not being archived. This is to keep orphan documents
from occurring. If a parent document and all its child documents are archived
at the same time, then the parent document will be copied into the archive and
removed from the original database.
Disabling the option "Do not delete documents that have responses" allows
documents to be removed from the original database after they are archived,
regardless of their status as a parent document. This is not advised, however,
because this may create orphan documents. Orphan documents are not visible in
a hierarchical view because the associated parent documents have been deleted.
Supporting Information:
The information in the Archive Settings dialog box applies whether the
archiving is manual or scheduled. The topic "Archiving databases and
documents" in the Notes Help database provides more information on this.
For more information on SPR #KHAN5QMMMC, refer to the document titled
"Archiving: Parent Docs Removed from Source if Children Are Candidates for
Archive" (#1136814)? More >
|  |
|
|
|
|
|