The OpenEdge DBA Files
Mark has been working with Progress since 1989 when he was presented with his first “Progress Test Drive” while working for the US Coast Guard in Washington DC. He knew a good thing when he saw it and joined Progress Technical Support in 1990 where he worked with Adam Backman and other long term proponents of Progress. Since then Mark has swapped back and forth between 4GL development and DBA roles. He has a “penchant for making things work the way they should” and, before joining White Star, enjoyed database and application tuning using ProTop as the Progress DBA Lead at JPMorgan Chase.
"Will ProTop tell me when it is time to add a new fixed and or variable extent to my OpenEdge database?" It most certainly can.
The schema area should not be used to store application data. And, if you are getting ready to dump & load, certain schema attributes require special attention.
Blocked sessions are the silent killers of enterprise applications. No one in IT notices there's a problem until the business is seriously affected.
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...
It all started on Monday evening when the Out Of Memory (OOM) killer decided to kill the database broker process, _mprosrv. Given the circumstances, it was suggested that we “just” reboot. “Just” is a four-letter word. Whenever you hear “just,” you should prepare yourself…
So we rebooted…
… and, of course, it took longer than expected. Forty-five minutes to shut down (mostly to “deactivate” swap), and then, since the server hadn’t been rebooted for 2 years, the filesystems needed another 45 minutes for an fsck. Ok, that was painful, but at least we have a nice clean system to restart the db.