Unable to Connect to Database (after server has been re-started)

Question

Hi,<BR><BR>I use Essbase Admin Services 7.1.3 and the server was not responding, therefore our IT guys re-started it. Since then I am unable to connect to one of the applications. I have tried to start/Stop the application but it just says "Application did not start". <BR><BR>There are 6 databases in this application altogether (3 data and 2 Currency). The application has been there for about 3 years (it holds historic sales data) and there has never been any problems with it.<BR><BR>When I tried to Start the application, in the message panel at the bottom it says "Error: 1013015 Unable to Connect to Database (2003)". It's as if there is a problem with this 2003 database but the 2002 and 2004 database are OK.<BR><BR>Has anyone ever had this problem and knows how to rectify it??<BR><BR>Thanks in advance.<BR><BR>Sarah

Answer 1

It may be that the server restart corrupted the database. Go into database properties and uncheck the box start database with application and then try to restart the application.<BR><BR>You can try database validation, or simply reload the database from backup. But you can get the application up and the rest of the databases up by decoupling the database restart from the application start.<BR><BR>There will be a .xcp log file in your application directory (and possibly your database directory.) These might help Hyperion Support in identifying the cause of the problem. But the quickest solution would be to reload the database from backup. The serer and application logs can also provide help in identifying the problem.<BR><BR>One of the keys is to determine why the server is not responding before restarting the server. It may be that a single application is the source of problem. Typical causes are unscheduled free space restructures, application loads of large databases, and an occasional rogue process. Rather than rebooting the entire box, or even restarting the Essbase server, the safest approach is to only kill the job that is soaking up the cpu cycles, causing the server to be unresponsive. This requires identifying the offending process (esssvr.exe) and killingit. Often that restores the rest of the system to operations, giving you time to focus onthe offending application.<BR><BR>You learn thses things when you are pushing the server to its limits (or beyond). If it happens often, you need to do a serious performance audit of teh server and determine whether you need more power and/or memory. <BR><BR>And in any case, you are less likely to encounter this sort of problem in the future if you try to limit applications to a single database. This will allow a better utilization of system resources. And also, it's a good idea to shut down applications that you are not going to be using for a while. Every loaded app takes system resources whether or not it is doing anything. So review your list of apps that start on startup and consider unloading apps after completing batch processing. <BR><BR>Sorry about the long lecture, but I speak from somewhat painful experience. I hope that this will help you.