11/15/09

Recovery from Spreadsheet Log

The Essbase Spreadsheet addin can update Essbase in data cell level. In case of Essbase disaster, the essbase can be restored from the last backup. Suppose the last backup is yesterday night, and the Essbase disaster happens in lunch time today. The data this morning is not restored by default. How to restore all of the detail data include the data one second before the Essbase disaster? Here is the method:
1. Set SSAUDIT or SSAUDITR in essbase.cfg file
Sample code:
SSAUDITR Sample Basic C:\logfoldername
The above statement will set the spreadsheet log on Sample application, and basic database. If logfoldername is not specified, the default log folder is used.
SSAUDIT Sample
The above statement will set the spreadsheet log on Sample application for all sub databases.
SSAudit xxxxx xxxxx c:\sslog
The above statement will set the spreadsheet log on all application for all sub databases.
2. After adding the above code to the essbase.cfg, restart Essbase Server. You will see the next words in the C:\Hyperion\logs\essbase\app\Sample\Sample.log
[Sun Nov 15 22:22:50 2009]Local/Sample///Info(1002088)
Starting Spreadsheet Log [C:\Hyperion\products\Essbase\EssbaseServer\APP\Sample\Basic\Basic.alg] For Database [Basic]
This means the setting is successful.
3. You can go on to make updating in Sample.Basic using Excel Spreadsheet addin, everything is logged now.
4. Now, suppose your Essbase is just restored from a backup, further more, you can recover transactions from the update log. To do so, use the Essbase command-line facility, ESSCMD, from the server console. The following ESSCMD command sequence loads the update log:
LOGIN hostnode username password
SELECT appname dbname //Example: Select Sample Basic
LOADDATA 3 filepath:appname.ATX
//LOADDATA 3 C:\Hyperion\products\Essbase\EssbaseServer\APP\Sample\Basic\Basic.atx
EXIT
5. The difference between SSAUDIT and SSAUDITR is:
SSAUDIT append logdata to existing logs after archiving. SSAUDITR clear the logs at the end of the archiving process.
6. Please note, you should mannully backup and clear the Basic.atx and Basic.alg log files, so that they will not become too huge.