HCL Domino Ideas Portal
Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
Of course, Thomas, of course. Fixing a bug is better than trying to get around it.
But the proposed idea is in the same spirit as the 'fixup' command or the 'database auto-repair' feature. No product is bug free, we all know this. If there is a risk that data can become corrupted because Domino clustering is still not bug free then a feature detecting the presence of corrupted data is probably welcome.
Instead of repairing it automatically, wouldnt it be better to fix the problem that caused the database or content to get corrupt?
cldbdir.nsf contained wrong information indeed. Both members of the cluster "took control" of the mailfiles. It explains the duplicates in clubusy.nsf.
So, Domino should detect if something is wrong in clubusy.nsf or cldbdir.nsf.
Additional information :
https://www-01.ibm.com/support/docview.wss?uid=swg21152976