Every now and then I need to educate a customer on how OPMN works. Well, here's some knowledge I'm giving away for free. (3 CEOs ago hated when I did this)
Here's the symptom of what's causing your on-premises Hyperion / Oracle EPM Essbase.log to keep growing 24x7, even when no end-users are logged in and no MaxL automation is running:
Make a backup copy of opmn.xml if you've never performed this exercise before! OPMN is very particular about the XML file, and Essbase will fail to boot up if you commit a typo error in this file.
Now click Search->Find in your favorite text editor (cough cough Notepad++ cough cough) for the word "death". It is present in the opmn.xml file exactly once:
I have comments to offer on the restart-on-death setting. We'll get to that in a moment. But for now, you want to insert a new line immediately after <restart retry="2" timeout="600"/>
Paste exactly this:
<ping timeout="20" interval="0"/>
Bounce the Essbase service (Windows) or use your stopEssbase.sh / startEssbase.sh scripts in Linux. Done. Your modified file should look like this: