METHOD 1:
1. Make sure the application is stopped. (Stop app in Essbase Administration Services Console). Go into the OS system (for example: Explorer for Windows) and find the Essbase Application.
2. Within the database directory, please delete the following files:
Db_name.ind
Ess00001.pag
Ess00001.ind
Db_name.esm
Db_name.tct
3. After deleting these files, please reload data (via text file, spreadsheet or relational source) and calculate database.
METHOD 2:
Below is a step-by-step walk-through of an alternative method of recovering the database. The typical way of backing up the database is to delete the five files we recommend (ess00001.pag, ess00001.ind, db_name.ind, db_name.esm, db_name.tct) and reload the data back into the database to restore these files as stated above.
1. Copy the essbase.sec file to another location within the system while the application is closed/stopped. This file holds all the security information. However the reason to make a copy of it is because in later steps, it is recommended to delete the application. The security file will update itself once this is done. A copy of this file ensures the security information of the application is not lost.
2. Make sure you know all the Database settings for your application because you will be blowing away db_name.db. There are several ways to do this:
(a) Going through Database | Information and write down information
(b) In Esscmd, run commands: GETDBSTATS, GETDBSTATE. This will output the Database settings.
3. Delete the problematic application and database. This is done via the Essbase Administration Services Console. This will delete the db_name.db. To double-check this, look into Windows Explore to make sure the application is deleted. Note: Do NOT attempt to delete the application/database through Windows Explorer (if on Windows). This is unsupported and will not delete it properly.
4. Create a NEW application and database, name it the same name as the old application. This is because the security file points to the application with that particular name.
5. Copy the essbase.sec back into the bin directory over the previous essbase.sec. The reason is because the one existing in essbase\bin has been altered upon deletion of the database. It wiped out the database’s security settings.
6. Reload data into the database and calculate.
This recovery method will give a *fresh* new start of the database. This will provide a clean application and will hopefully decrease the crashes/corruption encountered. If it doesn't decrease the crashes, the next step would be to analyze disk space, memory and cache settings to find the root of the corruption problem.
1. Make sure the application is stopped. (Stop app in Essbase Administration Services Console). Go into the OS system (for example: Explorer for Windows) and find the Essbase Application.
2. Within the database directory, please delete the following files:
Db_name.ind
Ess00001.pag
Ess00001.ind
Db_name.esm
Db_name.tct
3. After deleting these files, please reload data (via text file, spreadsheet or relational source) and calculate database.
METHOD 2:
Below is a step-by-step walk-through of an alternative method of recovering the database. The typical way of backing up the database is to delete the five files we recommend (ess00001.pag, ess00001.ind, db_name.ind, db_name.esm, db_name.tct) and reload the data back into the database to restore these files as stated above.
1. Copy the essbase.sec file to another location within the system while the application is closed/stopped. This file holds all the security information. However the reason to make a copy of it is because in later steps, it is recommended to delete the application. The security file will update itself once this is done. A copy of this file ensures the security information of the application is not lost.
2. Make sure you know all the Database settings for your application because you will be blowing away db_name.db. There are several ways to do this:
(a) Going through Database | Information and write down information
(b) In Esscmd, run commands: GETDBSTATS, GETDBSTATE. This will output the Database settings.
3. Delete the problematic application and database. This is done via the Essbase Administration Services Console. This will delete the db_name.db. To double-check this, look into Windows Explore to make sure the application is deleted. Note: Do NOT attempt to delete the application/database through Windows Explorer (if on Windows). This is unsupported and will not delete it properly.
4. Create a NEW application and database, name it the same name as the old application. This is because the security file points to the application with that particular name.
5. Copy the essbase.sec back into the bin directory over the previous essbase.sec. The reason is because the one existing in essbase\bin has been altered upon deletion of the database. It wiped out the database’s security settings.
6. Reload data into the database and calculate.
This recovery method will give a *fresh* new start of the database. This will provide a clean application and will hopefully decrease the crashes/corruption encountered. If it doesn't decrease the crashes, the next step would be to analyze disk space, memory and cache settings to find the root of the corruption problem.
