Technote Number: 1094127
Problem:
This issue was reported to Quality Engineering, and was addressed in
Notes/Domino 6.5.3. The issue will not be addressed in Notes/Domino 5.x.
Excerpt from the Lotus Notes and Domino Release 6.5.3 MR fix list (available at
http://www.ibm.com/developerworks/lotus/):
Calendaring & Scheduling
SPR# BKAN5YEQ92 - Old room/resource reservations are not purged long after they
should be. This problem has been fixed in 6.0.5 and 6.5.3.
If you disable the agent and start it again, all documents in the database will
be considered new, and those older than two days will be deleted.
OR
If you change the agent to run on "All Documents in Database", the example
would be:
1. Create a reservation for a certain date. In this example, September 18.
2. At 01:00 on September 19 the agent runs and selects this new reservation.
However, the reservation is not two days old, so it is not deleted.
3. At 01:00 on September 20 the agent runs and selects the reservation. The
reservation is then deleted since it is now two days old.
Supporting Information:
Steps To Reproduce Problem:
1. Create a reservation for a certain date. In this example, September 18.
2. At 01:00 on September 19 the agent runs and selects this new reservation.
However the reservation is not two days old, so it is not deleted.
3. At 01:00 on September 20 the agent runs and doesn't select the reservation,
since it is neither new nor modified.
4. At 01:00 on September 21 the agent runs and doesn't select the reservation,
since it is neither new nor modified.
5. At 01:00 on September 22 the agent runs and doesn't select the reservation,
since it is neither new nor modified.
6. If you now stop the agent and start it again, all documents will be
considered new and the agent will delete the reservation.
Related Documents:
More >
|  |
|
|
|
|
|