Error updating view in mail.box: Database is corrupt -- Cannot allocate space

HCL Domino Domino Forum
1

Hi. During the standard mail.box maintenance, 1 database was damaged.

The following was output to the console:
[3500254:000008-000071593C275700] Clearing DBIID 7C38C854 for DB /local/notesdata/mail3.box
[3500254:000008-000071593C275700] 25.06.2025 01:00:09 Router: Received maintenance request for mail3.box, processing all pending message updates
[3500254:000008-000071593C275700] 25.06.2025 01:00:09 Router: Beginning in-place compaction of mailbox file mail3.box
[3500254:000008-000071593C275700] **** DbMarkCorrupt(PackBuckets: Bucket packing failure), DB=/local/notesdata/mail3.box TID=[3500254:000008-000071593C275700] File=inplace.c Line=1492 ***
[3500254:000008-000071593C275700] Assigning different DBIID(old - 00000000, new - 875C13D4) for DB /local/notesdata/mail3.box
[3499073:000135-00007D0A074E9700] Clearing DBIID 875C13D4 for DB /local/notesdata/mail3.box
[3500254:000008-000071593C275700] 25.06.2025 01:00:27 Recovery Manager: Assigning new DBIID for /local/notesdata/mail3.box (need new backup for media recovery).
[3500254:000008-000071593C275700] 25.06.2025 01:00:27 Router: Unable to compact mailbox file Mailbox 3: 03:F5
[3500254:000008-000071593C275700] 25.06.2025 01:00:27 Router: Completed compaction of mailbox file mail3.box
[3500239:000002-00007392B69B6740] 25.06.2025 01:00:27 Error updating view in mail3.box: *Database is corrupt -- Cannot allocate space*

After that, the database became unavailable, and the following entry was constantly in the console:
[3500217:000002-000073A2A0A91740] 25.06.2025 01:00:49 Error updating view in mail3.box: Database is corrupt – Cannot allocate space

A commit was launched on the database, but it did not help.:
[3499073:000013-00007D0BAD470700] lo fixup mail3.box -F -J -O –Y
[3591612:000002-0000723AFD529740] Clearing DBIID 4B3DA628 for DB /local/notesdata/mail3.box
[3591612:000002-0000723AFD529740] 25.06.2025 05:03:03 Database Fixup: Started: mail3.box -F -J -O –Y
[3591612:000002-0000723AFD529740] 25.06.2025 05:03:03 Performing consistency check on mail3.box…
[3591612:000002-0000723AFD529740] Assigning different DBIID(old - 00000000, new - F57A8BCA) for DB /local/notesdata/mail3.box
[3591612:000002-0000723AFD529740] 25.06.2025 05:03:07 Recovery Manager: Assigning new DBIID for /local/notesdata/mail3.box (need new backup for media recovery).
[3591612:000002-0000723AFD529740] 25.06.2025 05:03:07 Completed consistency check on mail3.box
[3591612:000002-0000723AFD529740] 25.06.2025 05:03:07 Performing consistency check on views in database mail3.box
[3591612:000002-0000723AFD529740] 25.06.2025 05:03:07 Completed consistency check on views in database mail3.box
[3591612:000002-0000723AFD529740] 25.06.2025 05:03:07 Database Fixup: Shutdown
As a result, the database had to be deleted with a server restart.

Question: What caused this error?
How to fix it is clear. But why is the base damaged?

2

Hi Aleksandr,

In response to your question:

What caused this error?

Common reasons for the “Database is corrupt – Cannot allocate space” error include hardware issues and improper operational procedures, such as sudden server shutdowns.

How to fix this?

The “Database is corrupt – Cannot allocate space” cannot be fixed by fixup. What we suggest is to recreate the mail3.box
Please see the knowledge article below for database corruption error that cannot be corrected by fixup:
Database corruption error that cannot be corrected by fixup - Customer Support

In addition, please see the documentation below regarding the Possible causes of Notes/Domino database corruption.

Thank you!

Regards,
John Vincent Dela Cruz