What it means
DAOS found that a database was changed outside Domino, so its DAOS references may not match the catalog. DAOS holds off deleting .NLO files until it resynchronises.
Common causes
- The NSF was restored from a file-level backup
- The file was moved or overwritten at operating system level, or copied from another server
- A compact that failed and left catalog information out of date
Quick fixes
- Let Domino recreate or update the DAOS catalog
- Run a copy-style compact on the database (
load compact [database] -c) to correct its DAOS information
- If it was copied from another server, run
tell daosmgr resync in a quiet period, as it can take a long time
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.