Technote Number: 1174405
Problem:
This issue was reported to Quality Engineering as SPR #ETHU65SFYG and has been
addressed in Domino releases 6.0.5 and 6.5.4.
Excerpt from the Lotus Notes and Domino Release 6.0.5 / 6.5.4 MR fix list
(available at http://www.ibm.com/developerworks/lotus):
SPR# ETHU65SFYG - This fix eliminates the possibility of data corruption due to
opening a note with mime content from Admin4.
This fix makes it possible to work around the issue by adding the following
parameter to the Notes.ini:
ADMINP_ENABLE_CASCADE_DESIGN_ELEMENTS=1
Supporting Information:
The delete/rename request is a batch process that opens every database on the
server that manages its ACL. All the Delegate Mail File and Delete from ACL
requests use the same semaphore, so only one of these requests can be processed
at a time. The delay is caused by the same AdminP request processing. Other
requests could continue to process, but the other threads eventually pick up
one of these types, and then waits for its turn with the semaphore.
In addition, the amount of time to process each database is longer in recent
releases later than 6.0, in that design elements are also reviewed as part of
the ACL modifications.
ACL requests are started on an "interval" time as specified in the server
document and are not immediate. The default interval setting is 60 minutes,
and increasing this time may improve performance as ACL requests are batched.
If multiple names are affected by a delete/rename, then the batching attempts
to make as many of these changes to the database as possible during one
search. (Please note that any interval request will be affected by this
change.)
For example, if three people are deleted from the Address Book and they all
exist in the ACL for a database, then when the Administration Process reviews
the ACL for this database, it will make the changes for all three
modifications. If the interval time is short, then the possibility exists that
the request will need to be processed for each user, which defeats the purpose
of "batching" the requests. The more work done when the database is open, the
better.
Another possibility is to suspend the administration request processing for a
period of time (via the Server document, Server Tasks tab, Administration
Process tab, Miscellaneous section), though you may want to manually force a
request to occur immediately, if the administration request is critical. More >
|  |
|
|
|
|
|