The OpenEdge DBA Files

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.

If you follow the guidelines suggested here, you can expect more hours of uninterrupted sleep at the very least, and at best? You will experience minimal disruption to your system should your OpenEdge databases be damaged for reasons beyond your control.