LO43871: DOCUMENTS ARE NOT DELETED FROM THE MAIL DATABASE WHEN THE SERVER-BASED ARCHIVE FAILS DUE TO EXCEEDING THE QUOTA

APAR status

• Closed as Permanent restriction.

Error description

• 1) Create a desktop policy to enforce the server-to-server
  archive for those
  mails "not modified in more than 365 years".
  2) Run "compact -a" against the mail file (the purpose of this
  policy is to
  create a new empty archive db).
  3) Set the newly created archive db quota to 35 MB.
  4) Modify the desktop policy to enforce the server-to-server
  archive for those
  mails "older than 30 days".5) Run "compact -a" against the mail
  file again.
  
  --> Totally there are 157 mails in the mail file. If no quota,
  130 mails should
  be archived (not sure why 131 mails are placed in the archive
  db). However with
  35 MB quota set on the archive db, as the quota is being
  exceeded during the
  archive (failing at half of way), 97 mails are copied to the
  archive db (only
  shown in the All Documents view). But, these 97 mails are not
  deleted from the
  mail file and the mail file still has 157 mails (same as
  before).
  
  [0B24:0002-0C40] 07/12/2009 11:00:02 PM  Added Data Note -
  DestID 2698, SrcID
  4890
  [0B24:0002-0C40] 07/12/2009 11:00:02 PM  Added Data Note -
  DestID 2702, SrcID
  4746
  [0B24:0002-0C40] 07/12/2009 11:00:02 PM  Unable to write to
  database - database
  e:\Lotus\Domino\data\archive\a_admin.nsf would exceed its disk
  quota of 35840
  KB by 1 MB.
  [0B24:0002-0C40] 07/12/2009 11:00:02 PM  Unable to store
  document in
  archive\a_admin.nsf (NoteID = 0) from mail\admin.nsf (NoteID =
  4918): Unable to
  write to database because database would exceed its disk
  quota.
  [0B24:0002-0C40] 07/12/2009 11:00:02 PM  Unable to replicate
  archive\a_admin.nsf: Unable to write to database because
  database would exceed
  its disk quota.
  [0B24:0002-0C40] 07/12/2009 11:00:02 PM  Error archiving
  documents from
  mail\admin: Unable to write to database because database would
  exceed its disk
  quota.
  [0B24:0002-0C40] 07/12/2009 11:00:02 PM  Compacting mail\admin
  (admin)
  [0B24:0002-0C40] 07/12/2009 11:00:03 PM  Compacted  mail\admin,
  0K bytes
  recovered (0%)
  [0B24:0002-0C40] 07/12/2009 11:00:03 PM  Database compactor
  process shutdown
  
  
  6) Increase the quota for the archive db (aims to archive all
  mails).
  7) Run "compact -a" against the mail file again.
  
  --> The archive continues from the last break point. 32 mails
  are copied to the
  archive db but 130 mails are deleted from the mail file (still
  not sure why 131
  mails are placed in the archive db). At the moment, everything
  resumes as
  normal.
  
  [02D4:0002-0AF4] 07/12/2009 11:11:23 PM  Archiving documents
  from mail\admin
  (admin)
  [02D4:0002-0AF4] 07/12/2009 11:11:23 PM  Pushing mail\admin.nsf
  to
  archive\a_admin.nsf
  [02D4:0002-0AF4] 07/12/2009 11:11:23 PM  Added Data Note -
  DestID 2706, SrcID
  4918
  [02D4:0002-0AF4] 07/12/2009 11:11:23 PM  Added Data Note -
  DestID 2710, SrcID
  4650
  ......
  [02D4:0002-0AF4] 07/12/2009 11:11:24 PM  Archived mail\admin, 32
  documents were
  archived and 130 were deleted
  [02D4:0002-0AF4] 07/12/2009 11:11:24 PM  Compacting mail\admin
  (admin)
  [02D4:0002-0AF4] 07/12/2009 11:11:25 PM  Compacted  mail\admin,
  20224K bytes
  recovered (49%)
  [02D4:0002-0AF4] 07/12/2009 11:11:25 PM  Database compactor
  process shutdown
  
  
  The concern now is after the archive fails due to the quota, how
  does user know
  which mails have been copied to the archive db? During the clean
  up in the
  archive db, if user finds the mail both in the mail file and in
  the archive db,
  and incorrectly deletes the mail from the archive db, when the
  archive happens
  next time, this mail will also be deleted from the mail file.
  The mail is
  unexpectedly lost.
  
  If this spr is determined as working as designed, please close
  it as an
  Enhancement Request. The customer hopes either of behaviors:
  
  1. The archive can be rolled back. Seems nothing ever happens.
  2. Delete archived documents from the mail file.
  
  I attach the required data for setting up the environment. The
  password of
  admin.id is "password".
  

Local fix

Problem summary

• A programming error was found but will not be corrected. It
   will be a permanent restriction.
  

Problem conclusion

• A programming error was found but will not be corrected. It
   will be a permanent restriction.
  

Temporary fix

Comments

• This APAR is associated with SPR# YYLN7SW8GV.
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• NA
  

Fix information

Applicable component levels