Enterprise Vault (EV) for Domino Fails to Archive Messages in Domino Database due to corruption

book

Article ID: 100043609

calendar_today

Updated On:

Description

Error Message

Start a dtrace of the proper archiving task.  For EV for Domino Journal archiving choose to dtrace EVLotusDominoJournalTask.  And for EV for Domino Mailbox Archiving choose to dtrace EVLotusDominoArchivingTask.  Now wait for the task to start processing or manually start the task to run against the database having the issue.  If dtrace contains the following line the database is corrupted:

51 07:51:25.278 [4808] (EvLotusDominoJournalTask) <4892> EV-H {LotusDominoJournalingTask.ProcessDatabase} Error(2071): Multi-Segment ID table length from server is not the length expected

The Domino administrator could also try to open the database in question.  If corrupted, a lot of times the database will not open or take a really long time to open showing that there are issues with the database.  This is the case most of the time but not always.

Cause

Corrupted IBM Notes/Domino database (Notes storage file .nsf)

Resolution

Have the customer's Domino Administrator run fixup on the corrupted database.  Sometimes fixup is not enough and therefore a copy style compaction will work which is loading the Compact task with -C option.  For example if database is the journal database called mailjrn.nsf under the Journaling folder you could go to that server console and type the following command:

Load Compact Journaling\mailjrn.nsf -C

Note: Compact or Fixup are standard Notes/Domino maintenance programs.  Whether a database is corrupted or not, the Domino administrator can choose to execute these commands against a database.  If the slightest suspicion of database corruption, run maintenance which could save a lot of time troubleshooting.


 

Need assistance in finding the email under archive mails.

Issue/Introduction

Enterprise Vault (EV) for Domino Fails to Archive Messages in Domino Database due to corruption