What it means
During a DAOS resync, Domino could not read the named database to collect its attachment references, so the resync could not complete.
Common causes
- The named database is damaged
- The database was in use, locked or offline during the resync
- The database could not be opened because of disk or file system problems
Quick fixes
- Check that the named database opens normally
- Take a backup, then run
fixup [database] on it
- Run
tell daosmgr resync again once the database is healthy
- Until the resync succeeds DAOS postpones deletions, so watch repository disk space
Disclaimer
The errors, causes and fixes on this site are carefully researched, drawing on HCL documentation and 28 years of hands-on Domino and Notes experience. Every environment is different, though, and a solution that works in one may not be right for yours. Exact wording can also vary between Domino and Notes versions.
This information is general guidance only and is provided without warranty of any kind. Always back up your data and test changes on a non-production system first. To the extent permitted by law, Bruinsma Services Pty Ltd accepts no responsibility or liability for any loss, damage, downtime or other consequence arising from use of this information. For advice specific to your environment, please contact me.