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
We suffer from this issue across many of our large applications that involve many DB's. It's a bad look for Domino as the only fix is to re-create the replica which for a 20GB DB can take a whole morning. We are hoping the move to v11 will help alleviate the issue with the ID Table being 10 times larger.
This though would be a great asset to proactively managing ID tables.
Yes, it would be very nice to be able to follow/monitor this. I've had an issue where a number of ODS 53 databases, due to poor programming, had their IDTable completely filled. It took us some time to find out what was the issue that broke the application suite, and from there on mitigating it. Which took a few days to sort out, during which a vital part of the application suite wasn't working.
An ability to monitor the IDtable growth and set a limit (percent) that would trigger an alarm or a DDM warning, would allow us to be pro-active instead of re-active.
What do you do when you know the size of the IDtable is close to a limit?