The OpenEdge DBA Files
Read on for more soul crushing, database corrupting, career killing ways to CRASH your OpenEdge database!
Linux "Out of Memory Killer"
A Linux self-preservation mechanism, the OoMK terminates a process when memory is over-committed. Unsurprisingly, the OoMK kills the process consuming the most memory, which, most likely, is the database broker process.
A quick Google search will turn up numerous interesting articles on how to avoid this situation, including ways to tune "oom_adj". In practice, though, it is unlikely that your database will be spared and you are better off making sure that you have ample memory to handle the expected workload on your server.
ProTop is a living breathing entity. It is growing and changing all the time. Be sure to regularly update your installation to ensure you have access to all of the great new features, enhancements and fixes. Here's how...
A catalog of wince-inducing practices to be avoided for the OpenEdge or, indeed any, database.
Why is storage so important in a world of 99.9% buffer hits? I’m glad you asked!
Welcome to our monthly ProTop newsletter, where you’ll find out what’s new, tips and tricks and other cool ways to use both the free and commercial versions of ProTop.
Visibility is one of the key themes when it comes to ProTop, and having the ability to see how the various objects in your database are growing is the focus of the storage statistics trends dashboard.
You may have heard that there is a critical security vulnerability in the “log4j” library that is used by many applications in the Java ecosystem and you might be wondering if this impacts your OpenEdge environment.
In today’s missive, we are going to talk about poor, misunderstood memory. How much is used? How much is free? How exactly do you define “used” and “free” memory? And the million dollar question: why should you care?