Fun with OHS

Recently I encountered an issue with OHS Node Manager failing to start-up properly after patching to Oracle EPM 11.2.11.  This issue, has only happened in one environment, and I personally haven’t encountered it anywhere else.  With that said, I thought I’d share what I ran into.

When starting node manager, the nodemanager.properties file (located at X:\Oracle\Middleware\user_projects\epmsystem1\httpConfig\ohs\nodemanager) is called.  This file has an entry that determines which libraries are loaded for the node manager, based on the operation system the Node Manager is running on.

That entry is NativeVersionEnabled=True.

If that value is set to ‘True’ and for some reason the NodeManager cannot find those libraries, you will get an error like the one below in the NodeManager.log file (located in the same folder noted above):

• “weblogic.nodemanager.common.ConfigException: Native version is enabled but node manager native library could not be loaded.  Caused by java.lang.UnsatisfiedLinkError no node manager in java.library.path”

The simple fix, is to set this value to ‘false’ and restart the NodeManager.  The NodeManager documentation says setting this value to ‘false’ can have performance implications, as the NodeManager specific libraries are supposed to be tuned to the OS.  However, in the case of OHS, all NodeManager is doing is handing-off the startup process to Apache, and not performing any performance or load bearing activities, so I suspect there isn’t much issue here.

The larger fix would be to reapply all OHS and NodeManager related patches, and watch for ‘locked’ or ‘Read Only’ files in the log that might not be getting upgraded, and thus impacting the underlying libraries.

As always, thank you for reading, and if iArch Solutions can assist you with your EPM or Cloud environments, let us know…we’re always here to help.