SSAUDIT

Enables spreadsheet update logging, appending to existing logs after archiving.

This setting does not apply to aggregate storage databases.

Syntax

SSAUDIT appname [ dbname [ log_path] ]

appname—Application name.
dbname—Optional. Database name.
log_path—Optional. Full directory path where you want the information stored. Do not provide a log_path value unless you have also provided a value for dbname.

Default behavior:

If SSAUDIT (or SSAUDITR) is not specified, spreadsheet update logging is not enabled.
If SSAUDIT (or SSAUDITR) is issued with no arguments, Essbase activates spreadsheet logging for all databases in all applications on the Essbase Server, and puts the log in the default directory: ARBORPATH\app\appname dbname.

Use the value xxxxx to indicate "all" for any argument.

You can issue up to ten (total) SSAUDIT and/or SSAUDITR statements per application.

Description

SSAUDIT enables Essbase to log successfully completed spreadsheet update transactions. The resulting logs can be used as a source of input data upon recovery after archive operations or other server interruptions.

Notes

SSAUDIT is not available when using Free-Form reporting in Spreadsheet Add-in.
If you have duplicate database names in different applications, do not store their error logs in the same directory. If you do, the log for one database will be replaced by the log for any subsequent database with the same name.
SSAUDIT creates two logs for each database:
- dbname.atx, which stores the update transaction records that can be used as the input source for data load
- dbname.alg, which stores history records from every update transaction, including user name, time stamp, and number of updated rows
Essbase ensures that if you enable spreadsheet logging, updates do not take place without getting logged. If Essbase cannot write to the update logs for any reason, Essbase fails the update transaction and issues an error message.
SSAUDIT may slow Lock and Send operations.

Example

SSAudit xxxxx xxxxx c:\sslog

enables logging for all applications and databases, storing the log in the path c:\sslog. This example assumes that you do not have duplicate database names (see Notes).