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
I have hundreds of PMRs where HCL and IBM Support could not identify the root cause of the corruption. In my experience NSFs start getting corrupted the moment Domino is started. Database corruption happens so much that HCL added the rprcleanup feature to mitigate it.
That is fine in the case of clustered servers, but not all servers can be clustered.
Since the Domino server already includes code to trigger rprcleanup, why not leverage that code to provide a view or report showing administrators which databases are corrupted? Then we would be able to run maintenance proactively before experiencing an outage. And we wouldn't need another futile call to HCL Support. Do you understand?
Did you try to identiy the root cause of corruption?
Domino has some way to identify corruption, but if a server is not clustered, there will be no rprcleanup. In this case, we need to run maintenance to repair corrupted files. There should be a "Corruption Analysis" tool in the Tools pane of the Files tab in Domino Administrator. It would use the existing code in Domino to provide a list of the corrupted databases. Ideally, it would also specify the manner in which they are corrupted. For example if the view indexes are corrupted, our remedy is to run updall. Other types of corruption may require fixup or compact. The tool should provide this insight.