Enables spreadsheet update logging, clearing the logs at the end of the archiving process.
SSAUDITR 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.
If SSAUDITR (or SSAUDIT) is not specified, spreadsheet update logging is not enabled.
If SSAUDITR (or SSAUDIT) 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) SSAUDITR and/or SSAUDIT statements per application.
SSAUDITR 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.
SSAUDITR 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, the update transaction failes and an error message is issued.
SSAUDITR may slow Lock and Send operations.
The spreadsheet log file will not be cleared if the database is shut down during archive mode. The database is expected to remain running while in archive mode.
SSAuditR demo
Enables logging with refresh (clear) for all databases belonging to the Demo application. The log is stored in the default directory.
SSAUDIT, which does not clear the logs after archive.
alter database begin | end archive (MaxL)
BEGINARCHIVE (ESSCMD)
ENDARCHIVE (ESSCMD)