Fatal Error: Essbase is already loaded
While starting Essbase we used to get “Essbase is already loaded” error and it used just stops. After searching here and there we came to know that this issue happens when Essbase server gets crashed and goes into UNKNOWN state. Once that happens it fails to start next time and the logs does not show any significant lead about the problem.
If you are facing the same issue like below, then please follow below possible solutions to fix it.
-bash-3.2$ ./opmnctl status Processes in Instance: BIInstance ---------------------------------+--------------------+---------+--------- ias-component | process-type | pid | status ---------------------------------+--------------------+---------+--------- coreapplication_obips1 | OracleBIPresentat~ | 6876 | Alive essbaseserver1 | Essbase | N/A | Down coreapplication_obiccs1 | OracleBIClusterCo~ | 6874 | Alive coreapplication_obisch1 | OracleBIScheduler~ | 6872 | Alive coreapplication_obijh1 | OracleBIJavaHostC~ | 6871 | Alive coreapplication_obis1 | OracleBIServerCom~ | 6873 | Alive -bash-3.2$ ./opmnctl stopall opmnctl stopall: stopping opmn and all managed processes... -bash-3.2$ ./opmnctl startall opmnctl startall: starting opmn and all managed processes... ================================================================================ opmn id=localhost:10215 Response: 5 of 6 processes started.
Error Seen In LogFile:
-------- 13/09/28 05:48:47 Ping process -------- -------- 13/09/29 23:23:50 Start process -------- -------- 13/10/25 01:39:30 Start process -------- Info: Essbase is reducing the number of soft file descriptors because the 32K limit has been exceeded. Exceeding the limit may significantly increase application load time. Fatal Error: Essbase is already loaded
If above logs comes and the status for Essbase shows down then follow below mentioned debugging methods:
Solution:
– execute opmnctl stopall to stop all the running processes.
-bash-3.2$ ./opmnctl stopall opmnctl stopall: stopping opmn and all managed processes...
– Usually this issue happens when the server crashes and it fails to clear the essbase.lck file. so cd to BIShared/Essbase/essbaseserver1/bin folder and make sure essbase.lck is not available there, if its available delete it.
rm essbase.lck
– Grep for any stray ess process for making sure its not running. If you find essbase server running please investigate and shut it down first.
ps -eaf | grep -i ess
– Grep for the essbase running port number using below command and make sure its already not in use. (Here the essbase port taken as 10215)
-bash-3.2$ netstat -antlup | grep 10215 (Not all processes could be identified, non-owned process info will not be shown, you would have to be root to see it all.) tcp 0 0 :::10215 :::* LISTEN 22501/ESSBASE
You can see the stray process id 22501 is still running, so use kill -9 22501 to kill it and rerun the same command the port shall be free now.
– cd to the essbase.cfg file location and make sure its not misconfigured or corrupt.
Make sure the AGENTPORT is correctly mentioned like below.
AGENTPORT 10215
– Once all above stuff is correctly checked and fixed run below command to start and check status. It shall show output like below
-bash-3.2$ ./opmnctl startall opmnctl startall: starting opmn and all managed processes... -bash-3.2$ ./opmnctl status Processes in Instance: BIInstance ---------------------------------+--------------------+---------+--------- ias-component | process-type | pid | status ---------------------------------+--------------------+---------+--------- coreapplication_obips1 | OracleBIPresentat~ | 22500 | Alive essbaseserver1 | Essbase | 22501 | Alive coreapplication_obiccs1 | OracleBIClusterCo~ | 22499 | Alive coreapplication_obisch1 | OracleBIScheduler~ | 22497 | Alive coreapplication_obijh1 | OracleBIJavaHostC~ | 22496 | Alive coreapplication_obis1 | OracleBIServerCom~ | 22498 | Alive
In case of any ©Copyright or missing credits issue please check CopyRights page for faster resolutions.