Is There A Method To Remove Auto Repair Entries For A Mailbox That No Longer Exists On the Store? (Doc ID 2168054.1)

Last updated on AUGUST 05, 2016

Applies to:

Oracle Communications Messaging Server - Version 7.0.5 and later
Information in this document applies to any platform.

Goal

We keep the user's message files on one file system and the store.idx, store.cxxx, etc. files for the same on a different file system.  After we rehost the user with rehostuser command from the source mail store to a new destination mail store, we continue to keep the user's message files on one file system, but delete the store.idx, store.cxxx files from the other file system on the source mail store.  There was a change in behavior in MS 7u5 p38 with mboxutil command that resulted in triggering auto repair requests for this broken mailbox on the source mail store.  User's mailbox works fine on the destination store.  However, there are now millions of auto repair requests queued up in the maintenance queue.

Is there a method to removing auto repair entries for a mailbox that no longer even exists on the store?

Ex.

(19:34:58) root@mailhost [~] grep -c user1 !$
grep -c user1 /var/tmp/imcheck.q.output
1527182

From imcheck -q:

RecNo Mailbox Timestamp Action
---------- ----------------------------------- -------------- ------

p1056193 user/user1 20160724124424 repair
p1056194 user/user1 20160724124424 repair
p1056195 user/user1 20160724124424 repair
....
p2715957 user/user1 20160725175449 repair
p2715958 user/user1 20160725175449 repair
p2715959 user/user1 20160725175449 repair


 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms