Showing posts with label hyperion essbase. Show all posts
Showing posts with label hyperion essbase. Show all posts

Wednesday, January 15, 2014

Hyperion Essbase Audit Trail

Turning the Audit Trail on in Hyperion Essbase is useful if you would like to keep track of data modification by users. Turning on the Audit Trail makes Lock & Send slower, however, it is of great importance in tracking data changes.

We can use the SSAUDIT feature in order to keep track of changes.
In order to turn on the Audit Trail in Hyperion Essbase, do the following:

  • Open the essbase config file - essbase.cfg which is located under the  SERVER\d$\Hyperion\Essbase\bin folder.
  • Add the following line - 
    • SSAudit APPNAME DBNAME D:\Hyperion\Essbase\app\APPNAME
    • eg: SSAudit Nirmal Khoonks D:\Hyperion\Essbase\app\Nirmal 
  • Save the essbase.cfg file.
  • Restart Essbase Server.
The SSAUDIT creates two files ".ALG" and ".ATX" in the path that we have provided in the SSAUDIT script line.
In this case, those files would be available in "D:\Hyperion\Essbase\app\APPNAME" folder and they would be called "NIRMAL.ATX" and "NIRMAL.ALG."

ALG file logs the User and timestamp, like in the following example:


[Mon Jan 13 16:47:24 2014]
Create Spreadsheet Update Log
[Mon Jan 13 18:36:40 2014]
Log Updates From User [ essadmin@Native Directory ] Starting At Row [ 1 ] For A Total Of [ 8 ] Rows
[Mon Jan 13 18:38:27 2014]
Log Updates From User [ admin@Native Directory ] Starting At Row [ 9 ] For A Total Of [ 8 ] Rows

ATX file logs the dimension members being altered. 

"Operating" "AT" "PC" 
"FY14" 
"Budget" 
"Final" 
"Dec" 
"20D500" "115000" 1563. 
"25Z250" "125000" 0.569 

If the SSAUDIT is issued without any argument, the log would be produced at the default location:
ARBORPATH\APP\APPNAME\DBNAME

If you would like to turn on audit trial for multiple application/databases, you could add multiple SSAUDIT statements (up to 10) in the essbase.cfg file. You can choose the log path as per your need. 

  • SSAudit APPNAME1 DBNAME1 D:\Hyperion\Essbase\app\APPNAME1
  • SSAudit APPNAME2 DBNAME2 D:\Hyperion\Essbase\app\APPNAME2
If you would like to produce a single log for all the applications that you have, you could have the statement like:
SSAudit xxxxx xxxxx PATH of your choice

Make sure to restart Essbase server for it to take effect. 

SSAUDITR - This is the alternate for SSAUDIT, and it clears the logs at the end of archiving process. 

Friday, August 23, 2013

How to change Essbase INDEX and PAGING file location


When we create Essbase cube, the INDEX (.ind) and PAGING (.pag) files are by default created under the app-database directory. For example, if you have Essbase installed in “D” drive, and if I have an application.database named Khoonks.Nirmal, the INDEX and PAGING files would be located under \\servername\d$\HYPERION\ESSBASE\app\Khoonks\Nirmal.

The names of the files would be NIRMAL.IND and NIRMAL.PAG.

It is not a problem in the initial stages, however, as the database size keeps on increasing, it takes longer during database restructure, outline changes, calculations, etc. Therefore, it is a good idea to change the location of the INDEX and PAGING files.

This is how you can change the storage location. 
In this example, we are changing the location from “D” to “E” drive.
1             Export the database.
2             Clear ALL DATA.
3             Modify the database location.  
a.       Right-click the database -> Edit -> Properties. You will see DATABASE PROPERTIES dialog.
b.      Click on STORAGE tab.
c.       Under “DISK VOLUME” you will see text “Click here to add.” Click it.
d.      From the DROP-DOWN, choose E.
e.      Click “SET.” “APPLY” “CLOSE”
4            Restart the application.
5            Load data from the export you did in step 1.
6           Check the new STORAGE location by Right-clicking the database -> Edit -> Properties. You can see the     new file location – path like \\servername\e$\Hyperion\Essbase\APP\Khoonks\Nirmal
7            Agg the database.