Essbase application stopped

Question

Hi Gurus,
One of my essbase app has stopped. I tried to start it from the EAS console and it does not start. It give a message, the following application did not start.
It gives ERROR 1002097 Unable to load database
Any suggestions?
Thanks

Answer 1

Please check below steps!
Symptoms
Error 1002097 Unable to load database (dbname) when:
Trying to start an Application or
Trying to Launch a Business Rule from Essbase
The application log also may show the following two errors:
Unable to lock file dbname.esm
Unable to open dbname.esm file
Cause
A lock was kept on the database or file (either by third party process (e.g. virus scan) or Essbase (orphaned ESSSVR process)
Solution
Ensure in Essbase Administration Services that no locks exist (right-click on Essbase Servername, EDIT->LOCK and EDIT->LOCKED OBJECTS, and if your database/outline appears in there, unlock it.)
Ensure no third party process keeps a lock on Essbase files. Pay special attention to antivirus- and backup software that may be scanning / running on your Essbase folders as that can lock the files.
Check if any ESSSVR process stays when the Essbase Agent is stopped
If the Essbase Agent is stopped using the Services Panel on Windows while a process is currently running, or if there has been an abnormal termination of the Essbase Agent, orphaned ESSSVR processes can be left. The steps to recover are then:
On Windows:
1. Shutdown the Essbase server using ESSCMD or MaxL.
2. Check Task Manager, confirm the ESSBASE.exe process is gone.
3. Check for any orphaned ESSSVR.exe processes still running.
4. Do an "End Process" on any ESSSVR.exe process that is still running.
5. Start the Essbase service and start the application.
UNIX:
1. Log in to the UNIX server as the user that starts Essbase.
2. Shutdown the Essbase server using ESSCMD or MaxL.
3. Run a "ps -ef | grep ESSBASE" to confirm Essbase is shutdown.
4. Run a "ps -ef | grep ESSSVR" to check for orphaned ESSSVR processes.
5. Note the process id (PID) and do a "kill -15 (pid)" for each of the orphaned ESSSVR processes. It may take a few minutes for the process to terminate. If it does not terminate, you will need to run a "kill -9 (pid)" which is a hard kill.
6. Start Essbase as you normally do and start the application.
To shutdown Essbase using ESSCMD or MaxL, use the following commands:
ESSCMD:
Shutdownserver "servername" "username" "password";
MaxL:
Alter system shutdown;
Windows Services:
sc \\MACHINENAME stop "HyS9ESBAgent11.1.1_hypservice_1"
choice /n /t 5 /d y > nul