Mechanism needed to limit shared memory dumping per instance, similar to the per session limit available now

Shared memory dumping is disruptive in a production environment, particularly if the shared memory size is large. In our environment, many sessions can simultaneously encounter the same issue and so we are open to many shared memory dumps occurring at the same time for the same problem. Not only does this take a long time but even though we have a large-sized dedicated disk partition for dumps, this can fill and we can end up with many incomplete dumps when one complete one would be far more useful.

There are some mechanisms already for controlling share memory dumping: you can choose not to dump the buffer pool; and you can limit the number of dumps per session.

We propose that there is some sort of mechanism to limit the number of shared memory dumps per instance or at least the number of shared memory dumps that can be in progress at the same time.

Post comment

Admin

Karen Qualley

Reply
| Sep 12, 2019

Thanks for your input! This is now in 14.10.xc2

0 reply Hide replies

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.

Please enter your email address

RELATED IDEAS

Mechanism needed to limit shared memory dumping per instance, similar to the per session limit available now